https://bugs.kde.org/show_bug.cgi?id=356828
--- Comment #8 from Robert Munteanu <robert.munte...@gmail.com> --- For the record, when this problem happens I can work around it by manually killing another kscreenlocker-related process. I forgot its name, something related to 'backend' I think. So this might be a clue - that process might be holding on to a stale reference ( of something, I have no idea about X internals ) and killing it ( and probably it being restarted ) make the problem go away. -- You are receiving this mail because: You are watching all bug changes.
