https://bugs.kde.org/show_bug.cgi?id=353838
--- Comment #13 from bjoe...@arcor.de --- (In reply to Myriam Schweingruber from comment #12) > I presume the problem is solved, closing Yes. Unfortunately it's still unclear, which change in the post 2.8 development of Amarok fixed the problem. I see two possible strategies to come to a stable version: 1) Do a "git bisect" between Amarok 2.8 and 2.8.90 and find a patch, which fixes the problem 2) Wait for a release -- You are receiving this mail because: You are watching all bug changes.
