Summary: | Playback will not resume after pause | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Patrick Jensen <patrick.jensen> |
Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | freeoffers0, lahtela |
Priority: | NOR | ||
Version: | 2.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Example protected .wma file |
Description
Patrick Jensen
2008-12-19 00:52:14 UTC
Disclaimer: it would be very very unprofessional of us to release a product where you can't resume playback from a paused state :). So, given this, that we haven't heard this from any other users, and that the developers can't reproduce I think it is safe to assume that it is a system configuration problem on your end. Make sure that you are using the xine phonon backend and not gstreamer. Gstreamer is known to be quite buggy. Feel free to reopen only if you have concrete evidence supporting that the problem might be on our side. Failing this, please try ask on our forum, the irc channel or ask your distribution for support. Thanks After doing some testing, I verified that this problem arises only after Amarok attempts (and invariably fails) to play a track affected by bug 176134 After additional investigation it appears that this is exclusively related to tag bug 176154, because Amarok handles an empty dummy file with 0:00 length just fine. Created attachment 29555 [details]
Example protected .wma file
Sorry unrelated-unintentional attachment intended for a different bug. Feel free to delete. This bug appears some times after a collection rescan. Once scan is complete and I start to use Amarok, the pause will not resume as descibed in the original description. Restarting Amarok resolves the issue. This is with Amarok 2.0.1 in Ubuntu Intrepid. Closing as dupe of another report. Patrick's and Tatu's comments indicate that this is a collection problem. *** This bug has been marked as a duplicate of bug 176154 *** |