If this is your first visit, be sure to
check out the FAQ. You will have to register
before you can post. To start viewing messages,
select the forum that you want to visit from the selection below.
If you have copied text output that contains formatting (colors, highlighting, etc.), please do not enclose it in QUOTE or CODE tags. Just right-click your mouse and choose "Paste Without Formatting" or similar (Paste as plain text).
Re: Found a solution to the screensaver problem...
the screensaver one... the one where it still would not work after the upgrade to 3.5.4
I, along with several others, have created threads in an attempt to find the solution.
Re: Found a solution to the screensaver problem...
howdy,
I have been beating my head angainst my montior, now I have a flat-screen. I been trying to figure this thing out.... And you did it thanks for the tip!!!!!!
ps. The most impressive thing 'bout Kubuntu , is you all."helpful n friendly"
much thanks
Re: Found a solution to the screensaver problem...
This fix used to work for me too but now it doesn't anymore.
I also tried commenting out the DPMS option in the monitor section of xorg.conf but I still get a blank screen when the screensaver should start.
I noticed the first time this happened there was a big capitol X on the screen (just in case that means something to any of the talented folks here)
Next I tried running kcontrol as root, from console using sudo I got this
"X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 147
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 147
Minor opcode: 3
Resource id: 0x0
Failed to open device
ERROR: Communication problem with kcontrol, it probably crashed."
but kcontrol ran anyway & while I was there I saw that no screensaver was selected & nun of them would display.
Long story short I think root is taking over the screensaver.
Is there a fix for that?
Re: Found a solution to the screensaver problem...
Gotblade,
as far as I know, the big white X on a large black screen indicates that the xscreensaver daemon is attempting to do his job but more or less fails due to the absence of a proper configuration ... if, as you assume, this is "root's fault", there sould be a file /root/.xscreensaver (beware of the dot ...) - which is supposed to be killed :P you may also check if as well as on who's account this daemon is running (it is supposed to be the current user).
Re: Found a solution to the screensaver problem...
no .xscreensaver in the root folder.
I need help with how to check out the rest of what you're talking about.
(if nothing else I'd be happy to learn something new)
I should maybe mention the xscreensaver daemon works fine. aka xscreensaver-demo but the kde ones only work in test mode.
Re: Found a solution to the screensaver problem...
OOPS!
I installed xscreensaver as a workaround for this problem & put a .desktop in the autostart folder to start the xscreensaver daemon on startup so I didn't try killing that daemon & running the "solarwinds" screensaver to see if it still wasn't working until now. It's working now but why did it work for a while, with the libs I had, before installing the gnome based screensavers & what got messed up?
Re: Found a solution to the screensaver problem...
Worked for me.
I would like to get the gnome screensavers to work, but I don't understand what putting .desktop in the autostart folder actually means. Could you explain this to me?
Re: Found a solution to the screensaver problem...
This fix worked for me too! The odd thing was that the screensavers workedintially, then stopped the next day (x was intialized before that). Now I'm trying to figure out why some desktop images work and others don't... Matt
Comment