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 529531 - Screensaver not detecting activity on second screen
Screensaver not detecting activity on second screen
Status: RESOLVED DUPLICATE of bug 427905
Product: gnome-screensaver
Classification: Deprecated
Component: daemon
2.22.x
Other All
: Normal normal
: ---
Assigned To: gnome-screensaver maintainers
gnome-screensaver maintainers
: 557539 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-04-23 12:17 UTC by Robert Hoekstra
Modified: 2008-11-13 17:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Robert Hoekstra 2008-04-23 12:17:31 UTC
Please describe the problem:
When I have a second screen of X (screen :1), not using Xinerama, separate desktop, The screensaver will not notice when I am active on that second screen. It will lock my screen if I am not active on the primary (':0') screen.

It is not a new bug, but I cannot find it at gnome.org, I found it at Ubuntu (launchpad.net) #93466 and redhat #238315.
I myself am using Gentoo, which bugtracker does not have a record. But I am sure this has nothing to do with the distribution I am using.

For information, I am running on a laptop with ATI X1600 card, in multi-head config with the fglrx drivers. none of above bugs reveal a solution

Steps to reproduce:
1. Set up system with multi head (don't know if it is related to fglrx)
2. be active on the second screen



Actual results:
the screensaver kicks in even when active on the second screen (writing mail or giving presentation)

Expected results:
The screensaver should keep reseting the idle timer and not kick in when active on screens other than 0.

Does this happen every time?
This issue is structural

Other information:
I'd be more than happy to provide additional information when needed.
Comment 1 William Jon McCann 2008-11-12 16:55:29 UTC
*** Bug 557539 has been marked as a duplicate of this bug. ***
Comment 2 William Jon McCann 2008-11-13 17:58:34 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 427905 ***