Version: (using KDE KDE 3.5.5) Installed from: Unlisted Binary Package OS: Linux No matter what screensaver I select, when it comes on automatically it displays a huge 'X'. Using the 'test' button shows the screensaver fine however. I am on archlinux and this happened right after upgrading to 3.5.5. I did not find a duplicate bug but found this thread that seems to be same issue: http://63.238.77.251/?l=kde-redhat-users&m=116135315621135&w=2
There are several related to this annoyance. I thought I fixed it, but it still happens: Bug: 136891 Bug: 136315
I just installed powersaved, kpowersave and made myself a user of the power group and now I get a screensaver. I am not sure this is related but it's the only difference I can think of. Perhaps powersave is activating the screensaver on its own and bypassing the default process? I disabled klaptopdeamon.
I have no screensaver configured, in Control Center the screensaver checkbox is disabled. Nevertheless since I upgraded to KDE 3.5.5 this same big white X on a black background keeps popping up. When I tried "xset q" in a shell, it showed: > Screen Saver: > prefer blanking: no allow exposures: yes > timeout: 310 cycle: 600 Notice the "timeout: 310", this is entirely different from what I had configured in Control Center. I did "xset s off", and now it shows: > timeout: 0 cycle: 600 So it seems to be finally disabled now. I have no clue though why KDE doesn't set this right. This problem arose when I upgraded to 3.5.5, so either it's a new bug, or something went fishy during upgrade.
Hm, bad news: the above didn't even disable this screensaver. Now I'm really out of options. Any ideas?
I have similar problem: sometimes I have 'big X' and sometimes selected screensaver appears. I use often opera (www browser) as another user (uid 502) in the KDE session (ran with uid 501). This is the only think I can report as the result of random activation between "my screensaver" and "the big X screensaver".
This appears to be fixed in 3.5.6 - it is now like it was in 3.5.4 :-) Nick
*** This bug has been marked as a duplicate of 75254 ***