Bug 88649 - screensavers do not start after the configured time
Summary: screensavers do not start after the configured time
Status: RESOLVED NOT A BUG
Alias: None
Product: kscreensaver
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kscreensaver bugs tracking
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-02 00:26 UTC by Mathias Homann
Modified: 2008-05-19 17:59 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mathias Homann 2004-09-02 00:26:51 UTC
Version:            (using KDE KDE 3.3.0)
Installed from:    SuSE RPMs
Compiler:          gcc version 3.3.3 (SuSE Linux)
OS:                Linux (i686) release 2.6.5-7.108-default

i can select and preview a screensaver, testing it works, too. but the screensaver does not start after the configured time, and also the screen-corner-autolock setting has no effect.
seems independent of which screensaver i select.
Comment 1 kapta 2004-09-03 03:22:13 UTC
i have the same problem i'm using suse 9.1 with the latest updates, kde 3.3.0, i also can't see any previews of the screensavers!
Comment 2 Michael Nottebrock 2004-09-03 20:07:17 UTC
Same on FreeBSD.
Comment 3 Michael Nottebrock 2004-09-03 20:08:38 UTC
I have gotten exactly one screensaver to work properly: Desktop Distortions/Science (which is kscience.kss).
Comment 4 kapta 2004-09-03 22:03:02 UTC
i have exactly the same thing, only Distortions/Science and Blank screen work, screen saver does not start at configured time, but if you uncheck "Make aware of power management" the screen saver does start after the configured time. but most the other screen savers don't work,  
Comment 5 Mathias Homann 2004-09-03 22:31:25 UTC
i can confirm the power management thing, as soon as i uncheck it, the screensaver starts after the configured time.
Comment 6 Michael Nottebrock 2004-09-03 22:53:32 UTC
I would suppose the power management thing is a feature, not a bug (no screensavers if you have display powermanagement turned on). I just reread the original error description again and I have to add one important thing: Except for "Science", all screensavers display just a blank screen when they kick in after the configured time. The mini preview and the 'test' button work as expected.
Comment 7 Michael Nottebrock 2004-09-03 22:56:34 UTC
Some of the savers also don't even blank the screen, instead, they just copy the desktop and then do nothing. This can be easily be mistaken as that they aren't starting at all - but you can see the clock applet 'stopping' with such blankers.
Comment 8 kapta 2004-09-04 02:51:30 UTC
"I would suppose the power management thing is a feature, not a bug (no screensavers if you have display powermanagement turned on)"

even if its a feature it should'nt work by disabling the screensaver all together, it should just make sure the screensaver switches off or something when the computer power settings kick in such as standby mode or something.
Comment 9 missive 2004-09-05 15:03:20 UTC
Screensaver problems for me also... Works using "test" but
will not start when locking the screen.

When it tries to start
on the console, I am getting messages like this: 
 
 SetClientVersion: 0 8 
 SetGrabKeyState - disabled 
 QPixmap: Cannot create a QPixmap when no GUI is being used 
 
 X Error in laser: 
 X Error of failed request: BadWindow (invalid window parameter) 
   Major opcode of failed request:  3 (X_GetWindowAttributes) 
   Resource id in failed request:  0x7 
   Serial number of failed request:  2071
Comment 10 kapta 2004-09-10 00:51:19 UTC
ok i think i've found the solution to this, but hope its also fixed by default.

open console login as root

and type:

ln -s /usr/X11R6/lib/xscreensaver /usr/lib

and

ln -s /usr/X11R6/lib/X11/xscreensaver/config/ /etc/xscreensaver

after this my screensavers seem to work perfectly, kde 3.3 rocks!
Comment 11 Michael Nottebrock 2004-09-10 02:28:18 UTC
Doesn't make a difference here.
Comment 12 Stephan Kulow 2004-10-05 15:24:24 UTC
ok, one issue: the paths for the SUSE xscreensaver package changed. This breaks some things if you update xscreensaver but not kdeartwork or the other way around. But it's not a bug in the KDE code.

The other issue: xscreensaver 4.18 got a major regression that makes it impossible to run it as dedicated screensaver (interestingly enough it works from Random). The bug is fixed in the latest packages on ftp.suse.com and in the upcoming SUSE version (and was never broken on the released versions).

The third problem seems to be a misunderstanding of the powermanagement option, I suggest to open a dedicated problem report for that - this bug is crowded with tons of other problems.
Comment 13 ddhie$4-fFkt 2004-10-27 18:35:01 UTC
Yes i also beleive the screen saver should start but then be stopped when the monitor is shutdown due to power managment. As it is the screen saver simply does not start at all when the "make aware of power managment" box is checked. Would be very nice to see this resolved in 3.3.2 ;P. 
Comment 14 Chris Jones 2004-11-21 13:11:28 UTC
I have the same problem using KDE 3.3.1 on Fedora Core 3, on a desktop box and also on a laptop where even the blank screen doesn't kick in...

I have tried the above fix :-

ln -s /usr/X11R6/lib/xscreensaver /usr/lib 
ln -s /usr/X11R6/lib/X11/xscreensaver/config/ /etc/xscreensaver 

but I cannot do this since /usr/X11R6/lib/X11/xscreensaver/config doesn't exist on FC3. I guess the distros have things in different places ? Have any other Fedora users got this fix to work ?
Comment 15 Rex Dieter 2004-12-07 22:13:38 UTC
Chris, 

Please file the FC3 issue in a separate report (I have a fix), so that I can document the patch.

-- Rex
Comment 16 John Baldwin 2006-06-13 15:43:58 UTC
I still see this on FreeBSD with KDE 3.4.x and even KDE 3.5.2.  Given the general nature of this problem (not SUSE or xscreensaver specific) I don't see why this was marked "resolved".
Comment 17 Michael Nottebrock 2006-06-13 16:56:23 UTC
I can confirm that this bug has, if anything, gotten worse (at least on FreeBSD) in 3.5.3. Now, no screensaver will start at all at the configured time, neither the native KDE savers, nor the wrapped xscreensavers, regardless of the state of DPMS power management.