Summary: | screensaver shows big X instead of selected screensaver | ||
---|---|---|---|
Product: | kscreensaver | Reporter: | Joshua <js> |
Component: | general | Assignee: | kscreensaver bugs tracking <kscreensaver-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | erik, rdieter, schwarzer |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Joshua
2006-11-19 21:26:17 UTC
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 |