Version: (using KDE KDE 3.5.5) Installed from: Ubuntu Packages OS: Linux I can see that people have had simular problems before, with redhat disto. And that the problem is solved. However I have the same problem with my Kubuntu version. 6.10 Edgy KDE 3.5.5 Problem is. When I test run screensaver iether from the config manager or directly from /usr/share/applnk/System/ScreenSavers They all work perfectly. But, when they are suposed to start, after the timeout time, the screen just goes black. Some times theres a big X, locks like a screen saver, but I dont recognize it a screensaver I'v ever seen. I'v tried with different choises of sreensaver and the random one. same result, a black screen. Latest driver for my Geforce 6800 Gt installed with sudo apt-get install nvidia-glx nvidia-kernel-common I had ubuntu with gnome previosly and had no problems w screensavers .
I have submitted a patch for this - the timeout on X screensaver gets set when it shouldn't be after locking session/unlocking session. See bug 136315 Nick
I believe I have a similar problem as the reporter using KDE in Debian Etch version 3.5.5a-2. The screensaver starts as normal when: 1. using the "Test" button in the kcm 2. manually locking the session from the K Menu 3. issuing 'dcop kdesktop KScreensaverIface save' 4. issuing 'dcop kdesktop KScreensaverIface lock' However, when the desktop is inactive for the specified time the screen is either blank or blank with a large X-Windows logo and does not lock*. My relevant kdesktoprc section is: [ScreenSaver] ActionBottomLeft=0 ActionBottomRight=0 ActionTopLeft=2 ActionTopRight=0 DPMS-dependent=true Enabled=true Lock=true LockCornerBottomLeft=false LockCornerBottomRight=false LockCornerTopLeft=true LockCornerTopRight=false LockGrace=1000 Priority=19 Saver=KClock.desktop Timeout=300 'xset s off' will clearly not work for this problem, since I wish for the screensaver to start after inactivity. The problem also does not appear related to Bug 136315, since the screensaver is requested to start automatically and the blanking _does_ occur after the correct interval, but does not display correctly or lock the screen. The problem also occurs regardless of whether the screen has been previously locked. I have seen this problem on two machines, one with an NVidia card using the proprietary nvidia driver and and IBM laptop with and ATI card using the fglrx proprietary driver, so I do not believe the hardware is at fault. It is possible that the fault lies in Debian (and therefore Ubuntu), so a confirmation from a non-Debian-user would be helpful. *While the lack of the correct screensaver is an annoyance, the failure to lock the screen is a security problem!
There is something very wrong here, related too bug 136315 I don't use screensaver, but lock desktop manually. I get up in the morning,. and a screensaver is running (the black screen with a white X). With the patch applied I submitted on bug 136315, this still happens, although xset q show screensaver timeout == 0. So, screensaver gets started no matter what, but it is always that black screen with white X. It's a bit of a mess, really. Nick
*** This bug has been marked as a duplicate of 75254 ***