Comment 6 for bug 163865
Revision history for this message
| Kevin Fishburne (kevinfishburne) wrote | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I'd like to add to the last comment that regardless of the power preferences the screensaver needs to be disabled as well. Only disabling power options is not enough.
I sell desktop PCs for a living and have already had to tell a customer that he'd need to disable the screensaver to keep this from happening. Hopefully this will be given a reasonably high priority since it is something that many users will find extremely annoying and be unable to easily diagnose.
I'm not a programmer but will try to help speed a bugfix along in whatever way I can. Normally mouse movement and keystrokes prevent the machine from being considered idle. The problem here is that when certain applications are in focus mouse and/or keyboard events are not picked up by whatever process determines the machine's idle state. I ran some tests and found the following:
1) No Compiz, no problem.
2) No screensaver, no problem.
3) Compiz, screensaver, application is windowed, mouse movement, no problem.
4) Compiz, screensaver, application is windowed, keyboard movement, problem.
5) Compiz, screensaver, application is full screen, mouse movement, problem.
5) Compiz, screensaver, application is full screen, keyboard movement, problem.
In these tests I was using a fully updated Gutsy with NVIDIA's latest binary driver. I was using LTris, and made sure the mouse cursor didn't leave the app and that the app was in focus.
From the results you can see that the problem persists even if the app is not in full screen mode, except in the case of mouse movement. The problem is just more transparent because the app doesn't lose focus like it does when in full screen mode. I'm guessing the bug lies in whatever process determines the system's idle state (probably the window manager) and the way some apps grab mouse and keyboard input. Maybe Compiz's method of mouse/keyboard polling should be taken to a lower level so it is immune from what any apps may do. Surely there's some reliable way to see if someone's flailing at the mouse and keyboard.
Kevin