Version: (using Devel) Installed from: Compiled sources KDE 4.3.95, Ubuntu 10.4 Alpha 2+. I find that KDE will not lock the screen when I suspend to RAM or hibernate to disk, if I initiate the action from within KDE. However, if I press my laptop's Fn-key suspend-to-RAM combination, the screen saver is activated and the screen is locked upon resume, just as it should be. In the latter case, just before the machine is suspended, I get a reassuring notification about the screen saver being activated. In the former case, that notification is missing. My desktop machine running KDE 4.3.4 on openSUSE always locks the screen on suspend, so this may be a regression, or possibly a Ubuntu thing.
After installing KDE 4.3.95 on a desktop machine running openSUSE 11.2, I see that it behaves as expected, with the screen saver properly activated just before suspend. I'm beginning to think this is an Ubuntu issue.
Kubuntu 10.4 appears to have fixed this.
Sorry, not fixed, just no longer happens all the time- only most of the time. Probably an artefact of the underlying timing issue.
Bug has also been reported as http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580370
Broken in 4.5 RC2 too
security issue, marking as major
Just to clear up what happens currently. Suspend to disk (power button or via task bar button), and then the machine hibernates. Upon resume, what was on the screen (i.e. could be the users bank !) reappears. This happens almost every time. About half the time, it's possible to move the mouse cursor too. Once the disk calms down from the resume, the screen saver does activate.
See also #174117
*** Bug 253730 has been marked as a duplicate of this bug. ***
*** Bug 234925 has been marked as a duplicate of this bug. ***
*** Bug 174117 has been marked as a duplicate of this bug. ***
SVN commit 1194836 by dafre: BUG: 224517 Explicitely wait for the screensaver Lock to be finished before carrying out any other action. M +2 -1 suspendsession.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1194836