After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 557539 - gnome-screensaver not detecting activity on the second screen (:0.1) in a dual-screen
gnome-screensaver not detecting activity on the second screen (:0.1) in a dua...
Status: RESOLVED DUPLICATE of bug 529531
Product: gnome-screensaver
Classification: Deprecated
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: gnome-screensaver maintainers
gnome-screensaver maintainers
Depends on:
Blocks:
 
 
Reported: 2008-10-23 03:21 UTC by Shawn Rapaz
Modified: 2008-11-12 16:55 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Shawn Rapaz 2008-10-23 03:21:24 UTC 
Please describe the problem:
gnome-screensaver not detecting keyboard and mouse activity on the
second screen (:0.1) in a dual-screen. If working in one screen the other screen will start using the screen saver.

Steps to reproduce:
1. This problem can only be reproduced using dual monitor. Single monitor is fine.



Actual results:
The screen that is not currently active goes into screensaver mode.

Expected results:


Does this happen every time?
Yes, this happens every time.

Other information:
This only happens with gnome-screensaver.
Comment 1 Curt Sampson 2008-10-23 03:45:26 UTC 
Actually, the screensaver comes up on both screens, as normal. The basic issue is just that activity on :0.1 does not prevent the screensaver from starting. As well, while working on screen 1, I find that on a regular basis something grabs my focus and I need to move the mouse from one window to another and back again to get it back. (I use fvwm with point-to-focus.)
Comment 2 William Jon McCann 2008-11-12 16:55:29 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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