Version: (using KDE KDE 3.5.5) Installed from: Ubuntu Packages OS: Linux Using KDE 3.5.5 on Kubuntu Edgy: How to reproduce: 1. Make sure in your kcontrol > 'display settings'; the energy saving is enabled. 2. Go to kcontrol > screensavers; enable e.g. the clock and set it to automatically and 1 minute. 3. Wait 1 min and the clock should come up. 4. Go to kcontrol > 'display settings'l disable energy savings, the time for e.g. your monitor should grey out. 5. Wait 1 minute and the you will see the bug. The screen turns blank or shows a white X on a black background. I had to PC's; one gave the blank scrren, the second one the X. 6. After this has happened you can enable the energy saving option again and you will notice that the screensaver works again. See also this forum-thread: http://kubuntuforums.net/forums/index.php?topic=10331
Also reported to Kubuntu bugs: https://launchpad.net/distros/ubuntu/+source/kdeartwork/+bug/70991
I have similar thing. I set screensaver to blank, I set power saving for monitor to turn it off. And now: * ssaver kicks in * later monitor is turned off * but when I plug it to TV via SVGA port I can see big white X on TV It is really disturbing because I should (as a user) be able to change anything and I don't like hidden behaviour (it makes me suspicious about viruses etc).
Just of curiosity I changed the screen saver to Euler, and instead of it I have blank screen, but when monitor should be turned off I get this white X. opensuse 10.0.
I experience a similar effect. At the beginning of each KDE session the screen does not go black until I lock the screen. Then after unlocking the screen always goes black whenever the keyboard or the mouse has not been used for some time. I found, that before locking 'xset q' displays the lines: Screen Saver: prefer blanking: no allow exposures: yes timeout: 0 cycle: 600 Afterwards it says: Screen Saver: prefer blanking: no allow exposures: yes timeout: 310 cycle: 600 So I assume that KDE changes that setting but fails to set it back after unlocking the screen. My work around is to type xset s off each time once I have unlocked the screen.
*** This bug has been marked as a duplicate of 75254 ***