summaryrefslogtreecommitdiffstats
path: root/BUGS
diff options
context:
space:
mode:
authorSlávek Banko <[email protected]>2016-03-26 17:01:39 +0100
committerSlávek Banko <[email protected]>2016-03-26 17:01:39 +0100
commit81fedf1b8e2e3fe9e3d5a8fb5ef69b8ca2aab19d (patch)
tree1ba18eeb5470232b06215b81278e7d5fe24d5932 /BUGS
downloadkplayer-81fedf1b8e2e3fe9e3d5a8fb5ef69b8ca2aab19d.tar.gz
kplayer-81fedf1b8e2e3fe9e3d5a8fb5ef69b8ca2aab19d.zip
Initial import of kplayer 0.6.3
Diffstat (limited to 'BUGS')
-rw-r--r--BUGS36
1 files changed, 36 insertions, 0 deletions
diff --git a/BUGS b/BUGS
new file mode 100644
index 0000000..32198e3
--- /dev/null
+++ b/BUGS
@@ -0,0 +1,36 @@
+Known problems
+--------------
+
+Problems when coming back from full screen mode have been fixed.
+
+Seeking still does not work well on some media types. In those cases you
+can try using the Forward/Backward commands instead of clicking on the
+progress slider or dragging the slider thumb. Also the detected length may
+not be correct in some cases, especially on variable bitrate files. Some
+files are not seekable at all. This is an MPlayer problem.
+
+After playing from slow media like optical disks, some MPlayer processes
+may be left behind. Run killall mplayer to kill them.
+
+Resizing is not very smooth and causes flickering of the video area and
+other parts of the program. Aspect ratio is not maintained while resizing
+the window continuously.
+
+Some actions in the Configure Shortcuts and Configure Toolbars dialogs
+have the same name when in fact they are different actions. This is
+presently a kdelibs limitation.
+
+Reporting bugs
+--------------
+
+It is importand that you follow the steps described in Reporting KPlayer
+Bugs Micro-HOWTO
+http://docs.kde.org/development/en/extragear-multimedia/kplayer/howto-bug-reporting.html
+
+All bugs should be reported through the SourceForge bug tracking system
+http://sourceforge.net/tracker/?group_id=71710&atid=532182
+Please go through existing bugs first to make sure your issue is not yet
+being tracked.
+
+Similarly, feature requests, patches and support requests should be sent
+through SourceForge. That will make sure they are not forgotten.