Comment 19 for bug 389681

Well, it could also be that the apps were run with sudo instead of kdesudo, as Jonathan points out. It could be either a packaging issue or running with sudo, and it's hard to decide exactly which. I have the sneaking

Reporters with the issue (Dragoneyes, Daniel, James, Peter, Ioritz, and fasoi): Do you remember ever running Amarok as "sudo amarok" before the issue?