Bug 198086 - "Multiple background tasks running" message appears and never goes away
Summary: "Multiple background tasks running" message appears and never goes away
Status: RESOLVED FIXED
Alias: None
Product: amarok
Classification: Applications
Component: Playlist (show other bugs)
Version: 2.1.1
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-27 22:37 UTC by doc.evans
Modified: 2009-08-02 12:47 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 doc.evans 2009-06-27 22:37:45 UTC
Version:           2.1.1 (using 4.2.2 (KDE 4.2.2), Kubuntu packages)
Compiler:          cc
OS:                Linux (x86_64) release 2.6.28-13-generic

These seems to happen every day or two:

I look at the amarok window and see that "Multiple background tasks are running", and the progress bar is sitting at 13%. If I expand the view to see what the tasks are, I see six (6) instances of "generating playlist".

According to "top" amarok doesn't seem actually to be doing anything, and even if I wait for hours, the progress meter doesn't change and the "Multiple background tasks running" message never goes away.

The only thing I seem to be able to do is simply hit the "Abort all background operations" button. That works... until the next time the message appears.
Comment 1 A. Spehr 2009-06-28 01:05:25 UTC
*** Bug 198099 has been marked as a duplicate of this bug. ***
Comment 2 doc.evans 2009-06-29 20:45:31 UTC
Additional info:

Once amarok enters this state, it seems that dynamic playlists stop working properly: as one song finishes, instead of a new song being appended on to the playlist, nothing happens. So after a while all the songs on the playlist have been played and the music stops :-(
Comment 3 Myriam Schweingruber 2009-07-16 10:05:35 UTC
I can't reproduce this, but running 2.2-SVN here. Anybody else?
Comment 4 Myriam Schweingruber 2009-08-02 12:47:25 UTC
Still can't reproduce this with today's git build. Closing as solved.