Version: (using KDE 3.5.9) Installed from: Debian testing/unstable Packages I have my screensaver set til "Blank screen". When choosing "Lock session" on the KDE menu, or using CTRL-ALT-L, the screen is almost always blanked as the session is locked. However, a few times the screen is not blanked. E.g., just now it happened again. When I locked the session using CTRL-ALT-L, the "unlock session" password prompt came up instead of the screen going black. The session was locked, but the image on the screen was the desktop with the password prompt in the middle, instead of a black screen as usually happens.
Confirmed: sometimes it has happened to me too.
Is kscrensaver responsable of this type of issues?
Happens to me too on KDE 4.2 Beta2 and KDE 4.2 RC1.
Created attachment 30429 [details] Screenshot :)
Created attachment 30430 [details] One more screenshot :)
For me (on KDE 4.2 Beta2 and RC1 on Ubuntu Interpid): - The issue happens very often -- at least on automatic session locks. (Not sure about how often it happens on manual lock and whether it happens on manual lock at all, as I almost never lock screen manually.) - Only a part of the screen remains uncleared. Always a rectangle. And it always resides in right-bottom quarter of the screen. However the rectangle size may differ from time to time.
Created attachment 38756 [details] Desktop shown under unlock window Hello, I'm moving from bug #183496, which has probably the same or similiar origin. Today I have locked a screen with alt+control+l and returned 5 minutes later. I have moved my mouse and whole desktop appeared under unlock window as seen on this "screenshot". Desktop was static - conky window and clock didn't update and I was unable to perform any action on the desktop. As long as I have been moving my mouse/writing something on keybord, the desktop was visible. After pressing "cancel" the screen went blank and desktop didn't appear under unlock window anymore. This bug does not happen too often. I can easily reproduce effect similiar to this bug by putting system under heavy load (start one instance of glxgears for every CPU core) but it is present only for about 10 seconds after locking a screen and disappears even when I'm moving my mouse, so it might even not be related to bug described above. System: Arch Linux 64 bit, NVIDIA binary drivers, KDE 4.3.3 Settings: - Screenserver: Blank Screen - Start automatically after 4 min - Require password to stop after 10 seconds - Composing enabled Please vote on this bug if You are affected. @sasha1024 Your screenshot indicate that You are affected by bug #179924 - take a look at comment #32 there. :)
Happens to me sometimes too. Qt: 4.5.3 KDE: 4.3.3 (KDE 4.3.3)
*** Bug 232863 has been marked as a duplicate of this bug. ***
possibly related to bug 183496, though the timing is different.
the original issue has been fixed looong ago by introducing a one-second dead time after a forced lock, so the unlock dialog would not try to come up immediately if the user moved the mouse or so after issuing the lock action. the other issues in the comments are unrelated.