multihead bug: gnome-screensaver fails to detect keyboard, mouse activity on screens :0.1, :0.2
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gnome-screensaver (Ubuntu) |
New
|
Low
|
Unassigned | ||
Bug Description
Binary package hint: gnome-screensaver
I have a 3-screen workstation setup, with screens :0.0, :0.1, and :0.2. gnome-screensaver fails to detect activity on screens :0.1 and :0.2, although activity on :0.0 is properly noticed. "Activity" is defined here as keyboard and mouse button pushing and mouse motion. After the 2 minutes gnome-screensaver is set to are up, keyboard input is grabbed for a split second. I believe this is while it activates the fading to screensaver. The keyboard input is then noticed and keyboard input comes back after a moment. Mouse motion is not noticed at all, nor are mouse button pushes. This problem was also present in feisty.
I have verified that this is a gnome-screensaver bug instead of an X server inactivity problem, as disabling X screensaver works properly (i.e. switching to black ONLY happens when mouse and keyboard are inactive). I have a guess as to why this occurs, as it looks like gnome-screensaver watches all keyboard and mouse and window activity instead of asking the X server about inactivity as it (IMHO should).
This bug is terribly annoying as I must either turn off the screensaver (and leave my workstation unlocked) or else put up with a second or two of suspended keyboard input every fading cycle (there have been 3 or so while I've been typing this bug report).
| Basilio Kublik (sourcercito) wrote | #1 |
| Changed in gnome-screensaver: | |
| importance: | Undecided → Low |
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 93466, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.