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 480230 - Doesn't has good activity support for multihead
Doesn't has good activity support for multihead
Status: RESOLVED DUPLICATE of bug 427905
Product: gnome-screensaver
Classification: Deprecated
Component: general
2.20.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-screensaver maintainers
gnome-screensaver maintainers
Depends on:
Blocks:
 
 
Reported: 2007-09-25 14:19 UTC by Germán Poo-Caamaño
Modified: 2007-12-08 18:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Germán Poo-Caamaño 2007-09-25 14:19:01 UTC
I have:

* Ubuntu Gutsy, but previoulsy was Feisty with the same issue.
* A multihead setting, where my laptop is the :0.0 and 
  a external LCD display (using VGA connection of my 
  notebook) is :0.1.  Driver i810.
* Screensaver preferences are:
  * Regard the computer as idle after 10 minutes.
  * Activate screensaver when computer is idle.

If I work continously in :0.1, after a while (10 minutes) both
screen starts a fade out, having the same behaviour if the
computer was idle, but it wasn't idle.  This happens even if I'm
use the mouse over :0.1.

When I see the fade out, I just move the mouse from :0.1 to :0.0.

The expected behaviour is the screensaver should start the fade
out only when the computer were actually idle.  Without activity
in all displays.

Other information:
* Power Management:
  * Put display to sleep when inactive for 40 minutes 
    (on AC Power, which I know is one of my use cases).
  * Put display to sleep when inactive for 15 minutes
    (On Battery Power).
Comment 1 Teppo Turtiainen 2007-12-08 18:17:08 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 ***