Version: unspecified OS: Linux When I go to the screensaver settings and choose a screensaver and test it, it works there, but it does not work elsewhere, such as when it engages when it has been idle, or when I try to lock the screen. When I hit the shortcut key to lock the screen, nothing happens on screen except that the mouse cursor disappears, then when I mouse the mouse, the background then turns black and I get the prompt for the password. When I move the mouse after the computer has been idle, the screen momentarily flashes black. Reproducible: Always
sounds like one of the numerous compositing-related problems, but your report is too vague to tell. please look for "screensaver" bugs in the "kwin" product. also, simply browse the screensaver bugs. name some possible candidates and differences to what you are observing.
None of the screensaver bugs in kwin are similar to what is happening here.
have you tried turning off compositing/desktop effects?
OpenGL screensver and either a global color table on the root window (xprop -root | grep COLOR) or MSAA -> the screensaver need to _explicitly_ blank the screen (what probably doesn't happen) or it will remain translucent in that area. Pleas try a) suspend* compositing before running the screensaver (can we please call it screenlocker, it doesn't save anything anymore but actually _wastes_ battery...) b) w/ resumed compositing, try a screenlocker that does for sure not use OpenGL (xmatrix or so) also important: which KDE version do you use and do you auto-suspend compositing for fullscreen windows ("kcmshell4 kwincompositing", 3rd tab) * shortcut: SHIFT+Alt+F12
a) The bug still occurs after turning 3d effects off with shift alt f12 b) I don't have 'xmatrix', although it does seem to work with some (slide show) and not other non-opengl ones (swarm).
- Do you happen to use the plasma-netbook shell? - Please open a text shell ("konsole") and run "sleep 10; xprop > locker_window.txt" You've then 10 seconds to trigger the (non working) screenlocker. Wait until the cursor turns into a cross and click "the background" (whatever you see) Attach that file. (Either the window is not mapped or there's perhaps some hanging server grab)
"You've then 10 seconds to trigger the (non working) screenlocker." ? It always works if I trigger it when I use "test" in system settings. It is when I go afk and let it start on its own that some do not work. So since system settings won't let me set a countdown less than one minute, should I do something like sleep 100s instead? I do not use netbook shell, I am using kubuntu with kde 4.6.5, and suspend desktop effects for fullscreen windows is checked in kcmshell4 kwincomposting
I tried a few other screensavers, and so far, most of them seem to work. Swarm seems to be broken. Is there a way to set the screensaver to kick in in under a minute?
errrrr... you mean, calling /usr/lib/kde4/libexec/kscreenlocker DOES work (as expected) but when it's called (from krunner) it does not?? And that is only the case for _one_ screensaver hack (and what's "swarm" precisely, i have no /usr/lib/xscreensaver/swarm". Anyway, yes: call "sleep 70; xprop" and go away until the locker "should" show up. PS: forgot to mention - install xmatrix and/or glmatrix, just for the fun of it ;-)
Running kscreenlocker does not work with swarm as the screensaver. swarm does work when I test it using the screen saver system settings test button. running xprop after the screensaver should have taken effect, I get: $ sleep 70; xprop xprop: error: Can't grab the mouse. after I move the mouse again to turn off the "dead" screensaver and refresh the screen. I checked in /usr/lib/screensaver/ for swarm but it does not show up there; that is in /usr/bin/kswarm.kss . System settings does not seem to get its list of screensavers from there. All of the screensavers from the list seem to be in /usr/bin/
ok, as this is apparently limited to kswarm, this is in fact a known problem ... *** This bug has been marked as a duplicate of bug 74663 ***