https://bugs.kde.org/show_bug.cgi?id=346741
--- Comment #10 from Holger <h.kl...@gmx.de> --- (In reply to Mircea Kitsune from comment #8) > The screen locker you activate on demand isn't encrypted either. I don't see > why this is relevant to auto-lock on startup: Your computer is as secure > with auto-lock as it is when you leave it running after you've manually > locked it. Bad enough, you can leave the drivers seat while the engine is still running. But this request is like starting the engine on remote control. I brought up the hdd encryptionm, as I see it as an integral part of the suggested suspend2disk work-around. Why sacrifice security, if you could have both, 1. security and 2. the requested comfort of booting your system to a ready state, waking it up from hibernate? Well, not my decision anyway, so let's wait what the kscreenlocker maintainer thinks on the topic. -- You are receiving this mail because: You are watching all bug changes.
