Screensaver not working

What is your screensaver set as?

> What is your screensaver set as?
>
> ** Changed in: kubuntu-meta (Ubuntu)
> Status: Unconfirmed => Needs Info

I was using the clock screensaver but I also tried with some other
screensavers with the same result.
In the configuration screen if I use the test button everything is correct but
once I apply the changes and exit, the screen saver image doesn't appear,
just a blank screen.

I have the exact same issue with KDE 3.5.5 on Kubuntu Edgy. I only get the big X on occasion, most of the time the screen is just blank. It seems some of the screensavers will display the X and some the blank screen.

I get this as well, KDE 3.5.5 on Kubuntu Edgy 6.10 and Beryl/XGL. As cnobile said, "I only get the big X on occasion, most of the time the screen is just blank".

Strangely, though I can't explain it, doing killall kdesktop;kdesktop after logging in made the screensaver work...(with or without beryl, i915, regular X)

With a default fresh install of edgy, w/ the "Blank" screensaver I have the big White X across my screen as well.

Confirmed, if you kill kdesktop then restart it the screensaver begins to work. I found I had to put a sleep between the kill and restart like this: killall kdesktop;sleep 1;kdesktop&

The restart also gave me these errors which may or may not have any significance:
 X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device

By-the-way, I'm using a Lenovo 3000 N100 laptop.

Same issue here. However, I have the additional issue of when I press the test button nothing happens.

I thought my GL graphics were messed upm but Google earth works and my GL screensavers on Gnome, etc.

Cnoble:

The x errors are harmless, but if you wish to fix it, comment out all references to wacom (the tablet driver, stylus, tablet eraser) in your xorg.conf

Andrew,

Now that's good to know, being filling up my terminal for a while now. Thanks.

Could you please check if enabling "monitor power saving" as described in Bug #70991 makes the screensaver work?

Yes, enabling power saving makes the screensaver work but just for the current
session. When you reboot (I haven't tried with logout) the power saving
setting is lost and you must re-enable it again.
I've also found out that no matter what I do I can not change the frequency of
the monitor. It stays at 60Hz...
It seems, that for some reason, modifications in the screen section of system
settings are not enforced and registered in the configuration file (xorg.conf
I suppose).
I think all this things are connected and the screensaver doesn't work because
of them.

Em Sexta, 24 de Novembro de 2006 10:55, o yamal escreveu:
> Could you please check if enabling "monitor power saving" as described
> in Bug #70991 makes the screensaver work?

In my case this did nothing. I've had the "monitor power saving" on all along. Also commenting out the wacom entries from /etc/X11/xorg.conf caused me not to boot into X at all, so I put them back.

Cnobile: for removing these most annoying wacom entries see http://www.ubuntufrums.org/showthread.php?t=185930 (from post #12 onward). Unfortunately, it won't help solving this bug though.

Antonio: not remembering the dpms setting may or may not be a seperate issue, a number of bugs have been reported on this; see bug #65791 and others linked from there.

Has anything happened with this bug yet? I've kept my laptop updated and nothing has come through as a fix yet.

Are you running Edgy or Feisty? I haven't noticed any such problems with Feisty in awhile...

Edgy, read the 4th and other messages in this bug. This has been broken forever. I'm a developer, so if nobody is working on this bug point me in a direction and I'll take a look at it myself. As I intimated I don't know this architecture at all, but I do know C and Python very well.

fixed in feisty, gutsy.

Ubuntu Edgy Eft is no longer supported, so a SRU will not be issued for this release. Marking Edgy as Won't Fix.