Bug 136161 - Screensaver won't start as expected, instead starts when changing from standby to suspend.
Summary: Screensaver won't start as expected, instead starts when changing from standb...
Status: RESOLVED DUPLICATE of bug 75254
Alias: None
Product: kscreensaver
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Stephan Kulow
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-23 02:01 UTC by R Clarke
Modified: 2007-05-18 21:48 UTC (History)
0 users

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 R Clarke 2006-10-23 02:01:15 UTC
Version:            (using KDE KDE 3.5.3)
Installed from:    Ubuntu Packages
OS:                Linux

I set the screensaver using the "configure desktop" application (listed after right click on desktop), but the screensaver wouldn't start as expected.  After playing with this for a while I found a (rather strange) fix that worked for me so I thought I would fill out a bug report on it. If I turn on the screensaver and have it set to go off either before or concurrent with standby (in pwr mgmt section) and then set suspend to go off after standby, the screensaver kicks in when suspend should. I haven't tried all combinations, but the order of the triggers does seem to make a difference.  Also, if I move the mouse, etc while still in standby mode, the screensaver appears briefly before the desktop repaints.  

Here is what I found:  If I set the screensaver time to 1 min, standby to 1 min, and suspend to 2 min the screen goes black (backlight still on) after 1 min, and then the screensaver kicks on in another 2 min (3 min after last input).

Note:  Closest distro choice on the list was Ubuntu, but actually running Simply Mepis 6.0-1.  I'm not sure what else you might want to know, so just let me know if you need more detail on this.
Comment 1 Matt Fago 2007-01-26 21:53:18 UTC
Is this #128610?
Comment 2 Oswald Buddenhagen 2007-05-18 21:48:55 UTC

*** This bug has been marked as a duplicate of 75254 ***