(In reply to Oliver Kurz from comment #4) > Maybe you could find the error easier in the .xsession-errors file when > deleting the content and immediately afterwards locking the screen. That was also my first idea, but deleting the content and trying to lock/unlock session doesn't create any log-entries... Only after rebooting, the file gets "filled" :-(