Description of Problem: When the screen saver starts to engage and the screen fades to black, you move the mouse to stop it but it just keeps going until it fases out totally and then detects the mouse movement and the screen saver goes off. If you hit a keyboard key instead (while it is fading to black), it stops the screen saver immediately. Version-Release number of selected component (if applicable): How Reproducible: Let the screen saver start to engage and then move the mouse. Actual Results: Screen saver engages. Expected Results: Screen saver stops immediately. Additional Information: The mouse is a Microsoft X05-87477 Optical USB Mouse.
Reassigning to xscreensaver. I don't really see how this has anything to do with XFree86. (I also can't reproduce it)
I can confirm that this bug still exists in Fedora Core 1.
*** Bug 110042 has been marked as a duplicate of this bug. ***
Can you provide greater specific details about which particular screensaver you are using, with what settings, what timing, wether DPMS is on or not, and any other relevent details? Can both of you please attach your X server log and config file also? Just in case there is something patternic to be seen in them. The problem does not seem to be a "screensaver is broken for everyone in all circumstances" problem, so we need to know what the specific circumstances are that this problem occurs in, in order to be able to reproduce it locally.
Created attachment 95976 [details] PSN - xscreensaver config x86 Visual confirmation based on wall clock timing although it's quite subtle. Tested on both Fedora x86 and Fedora ppc. Platform fedora core 1 XFree86-4.3.0-42 xscreensaver-4.14-2
Created attachment 95977 [details] PSN - XFree86 log Steps I used to reproduce: 1) Hit lock screen 2) Move moush (touchpad - synaptics and touchpad adb) - observe time 3) Unlock 4) Hit lock screen 5) Hit key 6) Unlock 7) Hit lock screen 8) Wait until fade complete
Created attachment 95978 [details] PSN - XF86Config Only major difference to a standard config is synaptics driver, however have tested on alternate (ibook2 adb touchpad) configuration.
I think this happens for me in FC2. In particular, I have a Logitech Trackman Wheel and, when I'm just using the wheel to scroll through a document, the screensaver doesn't seem to recognize the movement and, so, activates while I'm scrolling around (after timeout period).
Hi, This bug is being closed because it has been in the NEEDINFO state for a long time now. Feel free to reopen the bug report if the problem still happens for you and you can provide any information that was requested.