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 580638 - Screen goes on standby at random times
Screen goes on standby at random times
Status: RESOLVED DUPLICATE of bug 580570
Product: gnome-power-manager
Classification: Deprecated
Component: gnome-power-manager
2.26.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME Power Manager Maintainer(s)
GNOME Power Manager Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2009-04-28 18:09 UTC by freggy1
Modified: 2009-05-14 09:55 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
gnome-power-manager --verbose log (91.61 KB, text/plain)
2009-04-28 19:40 UTC, freggy1 		Details

Description freggy1 2009-04-28 18:09:04 UTC 
With gnome-power-manager 2.26.1 sometimes while I'm using my machine, the monitor goes to standby only a few seconds after I stop moving my mouse. This in spite of the fact that I have set the standby time to 7 minutes.

With 2.26.0, I think the monitor actually never did go to standby, even though I had configured it so in gnome-power-manager.

System is Mandriva 2009.1 x86_64 with GNOME 2.26.1.
Comment 1 freggy1 2009-04-28 19:40:08 UTC 
Created attachment 133521 [details]
gnome-power-manager --verbose log

gnome-power-manager --verbose log.

The problem of the unwanted monitor standby happend around 21:37
Comment 2 Roman 2009-05-03 15:08:41 UTC 
I have the same problem. System is Mandriva 2009.1 x86_64 with GNOME 2.26.1
and it seems the gnome-power-manager ignores its settings. It goes to standy
in random time in spite of that I set it to go never standby. When I unplugged
power AC, nothing happens, nor the icon of power manager in task panel changes, nor the display dims as I set in preferences.
Comment 3 Michael Kanis 2009-05-14 09:55:19 UTC 
This looks like a dupe of bug 580570.

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