Summary: | Playlist not restored after crash or kill | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Tristan Miller <psychonaut> |
Component: | Playlist | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED DUPLICATE | ||
Severity: | wishlist | CC: | alexander.whittley, florian_staudacher, frederic.coiffier, k.dummann, oliver.henshaw |
Priority: | NOR | ||
Version: | 2.3-GIT | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Unspecified | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Tristan Miller
2008-10-30 16:09:12 UTC
If Amarok is not responding, it might be a bad idea to save whatever is going on within the application and load that next time the application starts. Autosaving the playlist periodically seems like a waste of time, since the playlist will most likely have been changed before the crash unless the refresh rate of the backup is quick, in which case you're just wasting cpu cycles. Might be another solution though, not sure. This is not a bug, but more a wish. It currently works like this by design, for performance reasons. *** This bug has been confirmed by popular vote. *** *** Bug 193764 has been marked as a duplicate of this bug. *** why is this a wish? If I logout from my desktop the application schoul normaly close, like click on on "quit" or? Is there any reason why amarok handles this in a different way then other applications? For me, Amarok closes correctly when logging out of KDE, so it saves the playlist. If it doesn't for you, then it's probably crashing on exit, for which you should file another bug. Is it possible that KDE kills applications which take too much time to shutdown ? I believed it was the problem with Amarok 1.x and KDE 3 : Amarok took lots of time to save its playlist and KDE killed it before it has finished. *** This bug has been marked as a duplicate of bug 226829 *** *** This bug has been marked as a duplicate of bug 170506 *** |