Bug 276088 - Kaffeine keeps loosing file
Summary: Kaffeine keeps loosing file
Status: RESOLVED INTENTIONAL
Alias: None
Product: kaffeine
Classification: Applications
Component: general (other bugs)
Version First Reported In: 1.x
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Mauro Carvalho Chehab
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-19 23:01 UTC by Lukas
Modified: 2017-10-04 09:04 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lukas 2011-06-19 23:01:35 UTC
Version:           1.1 (using KDE 4.6.4) 
OS:                Linux

Kaffeine frequently "looses" playing file. By loosing I mean starts to act like the file was deleted - playback stops (however audio keeps playing, probably from the buffer/cache), stop and press play doesn't works, seeking also doesn't. 

Only fixable by closing Kaffeine waiting for a while and opening the same file again. 

Running  kaffeine --nofork prints nothing during the failure prints nothing.


Reproducible: Sometimes




OS: Linux (x86_64) release 2.6.39.1-32-desktop
Compiler: gcc
Comment 1 Lukas 2011-06-19 23:11:18 UTC
Forgot to mention this happens when seeking video file or HDD is busy by other apps (like copying file, indexing or just starting any an application). So looks like Kaffeine expects data even before it is ready. Then the bad things happen ;/
Comment 2 Mauro Carvalho Chehab 2016-06-06 00:22:46 UTC
This bug is too old, for a version < 1.3. Closing it, as the latest version is 2.0.1, and lots of things changed since version 1.2.x, including the usage of VLC as video display backend, support for DVB-T2 and ISDB-T via libVLC, etc.

You may check on the upstream version and see if the bug was solved. The README file contains instructions about how to compile it. You can find it at our git repository: 

https://quickgit.kde.org/?p=kaffeine.git 

If you find similar issues with version 2.0.1, please re-open.