From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041111 Firefox/1.0 Description of problem: I use APM for sleep on my thinkpad. When I wake the machine up, it seems to immediately kick into the screen saver. This takes time to enter and time to return from, slowing the wakeup process. My guess is that the screen saver is being fooled by what seems to be a long period of inactivity. Version-Release number of selected component (if applicable): xscreensaver-4.18-4 How reproducible: Always Steps to Reproduce: 1. enable screensaver 2. /usr/bin/apm -s 3. wait a while 4. wake up machine Actual Results: screen saver immediately kicks in Expected Results: no screen saver, since powering up the machine is a "user action" Additional info:
The same thing happens on my thinkpad using ACPI sleep mode. This is very annoying and should be fixed.
When you close the lid, the CPU halts immediately. When you open the lid, it starts up again -- except now the wall clock has jumped dramatically. There's no way for xscreensaver to know that the machine had been suspended, only that suddenly a lot of time has passed, and now it's time for the screen to blank.
Fedora Core 3 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC5 updates or in the FC6 test release, reopen and change the version to match. Thank you!
Closing per lack of response to previous request for information. This bug was originally filed against a much earlier version of Fedora Core, and significant changes have taken place since the last version for which this bug is confirmed. Note that FC3 and FC4 are supported by Fedora Legacy for security fixes only. Please install a still supported version and retest. If it still occurs on FC5 or FC6, please reopen and assign to the correct version. Otherwise, if this a security issue, please change the product to Fedora Legacy. Thanks, and we are sorry that we did not get to this bug earlier.