It's been quite some time since this bug was reported and last commented on, so I'd like to solicit feedback to whether this bug still exists in the Amarok 2.x series. It has been observed as far back as Amarok 1.2.3 in Apr 2005 [1], but that bug was closed due to being against the 1.4 series. If we can confirm the issue still in Amarok 2, we can reopen that bug. I searched currently open bugs in Amarok's bugtracker for this one, but couldn't find it in bugs.kde.org [2].
For those picking up midway, the bug described here is _not_ that sound doesn't play out of Amarok -- that's often a Pulseaudio or other sound system error. This bug deals with the way Amarok handles a sound system that can't play anything -- typically because a sound device is unavailable. In those instances, Amarok will fail on the current track and advance to the next one, which then fails, so it advances again, etc. When this happens on dynamic playlists in particular (essentially of infinite length), it hogs CPU and makes Amarok unresponsive. How does this bug now stand in relation to Amarok 2? [1] https://bugs.kde.org/show_bug.cgi?id=103289 [2] https://bugs.kde.org/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=amarok&content=loop+through+sound+device ** Bug watch added: KDE Bug Tracking System #103289 http://bugs.kde.org/show_bug.cgi?id=103289 -- Amarok loops through all songs when the sound device isn't available https://bugs.launchpad.net/bugs/85791 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to amarok in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
