https://bugs.kde.org/show_bug.cgi?id=389441
--- Comment #2 from Aleix Pol <aleix...@kde.org> --- That solved the problem for me, yes. I'd say the bug is more how kactivitymanagerd goes mental if the db goes corrupt for any reason. -- You are receiving this mail because: You are watching all bug changes.
