this issue was reported at [1] and claimed to be "RESOLVED as FIXED" with amarok-2.1.1. hopefully it will be reopened and really fixed soon.
[1] https://bugs.kde.org/show_bug.cgi?id=172953
this issue was reported at [1] and claimed to be "RESOLVED as FIXED" with amarok-2.1.1. hopefully it will be reopened and really fixed soon.
[1] https:/ /bugs.kde. org/show_ bug.cgi? id=172953