display doesn't go to DPMS sleep

Bug #203513 reported by bonsiware
132
This bug affects 19 people
Affects Status Importance Assigned to Milestone
gnome-power-manager (Ubuntu)
Confirmed
Undecided
Unassigned
Nominated for Hardy by hirak99
Nominated for Karmic by Flo

Bug Description

Binary package hint: gnome-power-manager

I have hardy updated to now.

With the latest update of gnome-power-manager (from 2.21.92-0ubuntu2 to 2.22.0-0ubuntu1) my laptop has lost the ability to put display to sleep...

thank you!

Revision history for this message
Shirish Agarwal (shirishag75) wrote :

same here , the only change between him & me are I'm on the desktop.

Changed in gnome-power-manager:
status: New → Confirmed
Revision history for this message
Martin Soto (soto255) wrote :

Same situation here running Hardy beta updated earlier today. This is a desktop machine with a flat panel monitor, and an NVidia graphics card (running the proprietary driver.) I'm attaching the output of gnome-power-bugreport.sh, just in case it's useful.

Revision history for this message
Shirish Agarwal (shirishag75) wrote :

Same at my end, didn't know there was a gnome-power-bugreport.sh

Revision history for this message
Shirish Agarwal (shirishag75) wrote :

This one is at /usr/bin/gnome-power-bugreport.sh putting it up here so even if I forget I know what to do.

Revision history for this message
wizard10000 (wizard10000) wrote :

Obligatory "me too" post except mine isn't a laptop. Hardy installed on two test machines, neither will power down the monitor.

Both test machines are 2.8GHz P4 connected to the same monitor through a KVM switch. Monitor is a Samsung 204BW.

Revision history for this message
Jörn Schmidt (josc) wrote :

same here on a laptop.

Revision history for this message
Colin (colinnc) wrote :

Same problem here

Revision history for this message
hirak99 (hirak99) wrote :

I'm using Hardy, same problem here on desktop. Even though I've set display to sleep after 2 minutes, the screen does not go to standby - instead the screensaver continues to display.

I've attached my `gnome-power-manager --no-daemon --verbose` results.

An extract follows:
...
[x11_sync_server_dpms_settings] gpm-dpms.c:130 (06:32:58): Syncing DPMS settings enabled=1 timeouts=0 0 0
[x11_sync_server_dpms_settings] gpm-dpms.c:130 (06:32:58): Syncing DPMS settings enabled=1 timeouts=0 0 0
[gpm_idle_set_check_cpu] gpm-idle.c:236 (06:32:58): Setting the CPU load check to 0
[gpm_manager_init] gpm-manager.c:1782 (06:32:58): creating new inhibit instance
[gpm_manager_init] gpm-manager.c:1792 (06:32:58): creating new control instance
...

Is it because of the timeouts=0 0 0?

Also here's what `xset q` tells about DPMS.
DPMS (Energy Star):
  Standby: 0 Suspend: 0 Off: 0
  DPMS is Enabled
  Monitor is On

Revision history for this message
hirak99 (hirak99) wrote :

Also here's my gnome-power-bugreport.sh

Revision history for this message
Shirish Agarwal (shirishag75) wrote :

Found the attached by doing "sudo killall gnome-power-manager" as well as "gnome-power-manager --no-daemon --verbose 1& > ~/gpm.txt"

[x11_sync_server_dpms_settings] gpm-dpms.c:130 (06:53:15): Syncing DPMS settings enabled=1 timeouts=0 0 0

going on further but perhaps not in the gpm.txt

 [gpm_screensaver_powersave_idle_changed] gpm-screensaver.c:102 (06:55:14): emitting powersave-idle-changed : (1)
[powersave_idle_changed_cb] gpm-idle.c:335 (06:55:14): Received GS powesave idle changed: 1
[gpm_idle_set_mode] gpm-idle.c:98 (06:55:14): Doing a state transition: 1
[gpm_info_event_log] gpm-info.c:594 (06:55:14): Adding 2 to the event log
[gpm_screensaver_powersave_idle_changed] gpm-screensaver.c:102 (06:55:23): emitting powersave-idle-changed : (0)
[powersave_idle_changed_cb] gpm-idle.c:335 (06:55:23): Received GS powesave idle changed: 0
[gpm_idle_set_mode] gpm-idle.c:98 (06:55:23): Doing a state transition: 0
[idle_changed_cb] gpm-manager.c:849 (06:55:23): Idle state changed: NORMAL
[gpm_info_event_log] gpm-info.c:594 (06:55:23): Adding 4 to the event log

see if something can be known or done something about this bug

Revision history for this message
Shirish Agarwal (shirishag75) wrote :

The one above was of later, this one is of the previous attempt.

Revision history for this message
Colin (colinnc) wrote :

Here is my gnome-power-bugreport

Revision history for this message
Dan Washusen (dan-reactive) wrote :

Same here; I'm on Hardy using an nvidia card with the proprietary drivers connected to a LCD monitor.

If I issue "xset dpms 0 0 60", the monitor powers off as expected but reverts to the behavior mentioned above when X restarts...

Revision history for this message
Shirish Agarwal (shirishag75) wrote :

aha, a cursory look at my as well shown by hirak99 see the timeouts

[x11_sync_server_dpms_settings] gpm-dpms.c:130 (06:53:15): Syncing DPMS settings enabled=1 timeouts=0 0 0

no wonder we are not able to do the same. Looking at xset's man page it says

 dpms flags...
               The dpms option allows the DPMS (Energy Star) parameters to be set. The option can take up to
               three numerical values, or the ‘force’ flag followed by a DPMS state. The ‘force’ flags forces
               the server to immediately switch to the DPMS state specified. The DPMS state can be one of
               ‘standby’, ‘suspend’, ‘off’, or ‘on’. When numerical values are given, they set the inactivity
               period (in units of seconds) before the three modes are activated. The first value given is
               for the ‘standby’ mode, the second is for the ‘suspend’ mode, and the third is for the ‘off’
               mode. Setting these values implicitly enables the DPMS features. A value of zero disables a
               particular mode.

Revision history for this message
daponz (daponz) wrote : Re: [Hardy] display doesn't go to sleep after today's gnome-power-manager update

same situation here :/

Revision history for this message
Michael Losonsky (michl) wrote :

Same problem here after recent Hardy Beta update. There
was an automatic crash report I ignored.

I think this is an important bug. Certainly an LTS distro
should have power management work properly for many
important reasons.

Revision history for this message
jbond00747 (jeff-cowart) wrote :

I'm also having what appears to be the same problem. Dell Latitude D830n w/ Intel Graphics.

Revision history for this message
fjgaude (tanzen) wrote :

Hardy 64-bit desktop, latest updates, Viewsonic VP201s monitor, nvidia 7600GS, will not go to sleep.

Revision history for this message
hirak99 (hirak99) wrote :

Hardy 32-bit desktop, latest updates, Samsung monitor, NVidia 8600 GTS, will not go to sleep.

Revision history for this message
mannheim (kronheim) wrote :

I downloaded and compiled the most recent Gnome source for gnome-power-manager (version 2.23.1 in trunk), and this fixed the problem for me. So, unless this is a quirk of the build process, it seems that this bug is somehow fixed upstream. But I couldn't find any reference to it.

Also, there is a duplicate of this bug at #207553.

Revision history for this message
Michael Losonsky (michl) wrote :

As of right now (31.3.08, 2300) the latest version available in synaptic is 2.22.0.

Revision history for this message
Pär Bohrarper (par-bohrarper) wrote :

Yeah, me too. I have dual monitors on an Nvidia 7600, none of them go to sleep since hardy upgrade.

Revision history for this message
aldebx (aldebx) wrote :

Maybe needless to say but I confirm this bug on my HP Pavilion laptop with nVidia card

Revision history for this message
mxyzptlk (mxyzptlk) wrote :

Confirmed with an nvidia GeForce 8600GT

Revision history for this message
Maimon Mons (mmcmonster) wrote :

I was bit with this bug up until yesterday or maybe this morning, but the latest set of updates has fixed it.

Revision history for this message
Maimon Mons (mmcmonster) wrote :

gnome-power-manager is now at v 2.22.1-1ubuntu2 in synaptic. :-)

Revision history for this message
Michael Losonsky (michl) wrote :

The latest update included gnome-power-manager 2.22.1 which
takes care of this bug.

Changed in gnome-power-manager:
status: Confirmed → Fix Released
Revision history for this message
Dan Washusen (dan-reactive) wrote :

Yep, fixed in gnome-power-manager 2.22.1-1ubuntu2...

Revision history for this message
hirak99 (hirak99) wrote :

Bravo!

Revision history for this message
bonsiware (bonsiware-deactivatedaccount) wrote :

Fixed here too!

Revision history for this message
Liken Otsoa (liken) wrote :

I continue with problems and this fix. First time screen turns off, second time not, after suspend/resume fails. Frecuently it fails.
I need to xset dpms 0 0 120 or lock and unlock screen to activate something again.

Revision history for this message
MikeMan (michaelsbaxter) wrote :

After the latest security updates last week in Hardy, I'm seeing this same problem again.

Generated the attached by running "gnome-power-manager --no-daemon --verbose" and then launching System->Preferences->Power Management and adjusting the time to put the monitor asleep.

The DPMS timeout is always 0 0 0 no matter what I do.

Now my LDC is marked with the outline of several windows...

Anyone else seeing this? Other ideas I can chase down?

I'm using stock everything for Hardy, Dell E173FP monitor, Intel 82865G Graphics Controller in Dell Desktop.

Revision history for this message
MikeMan (michaelsbaxter) wrote :

This seems to have been resolved in the last update, it's now working fine.

Thanks to the Ubuntu people that make it all happen!

Mike

Revision history for this message
gatopeich (gatoguan-os) wrote :

Still wrong with gnome-power-manager 2.22.1-1ubuntu4.

gnome-power-manager disables DMPS timers. Here is a fast way to reproduce the issue:

$ xset dpms 0 0 120 ; xset q | grep Standby
  Standby: 0 Suspend: 0 Off: 120

$ gnome-power-preferences
   [change "Put display to sleep..." setting, then close]

$ xset q | grep Standby
   Standby: 0 Suspend: 0 Off: 0

Revision history for this message
hendrikwout (hendrikwout) wrote :

I have this problem on ibex alpha :( : screen doesn't turn off.
I installed nvidia 173 through envy-ng (installing from standard ubuntu repository didn't do it right).

I have a: 01:00.0 VGA compatible controller: nVidia Corporation GeForce 8400M GS (rev a1).

laptop:~$ xset q
Keyboard Control:
  auto repeat: on key click percent: 0 LED mask: 00000002
  auto repeat delay: 500 repeat rate: 30
  auto repeating keys: 00ffffffdffffbbf
                        fadfffdfffdfe5ef
                        ffffffffffffffff
                        ffffffffffffffff
  bell percent: 50 bell pitch: 400 bell duration: 100
Pointer Control:
  acceleration: 2/1 threshold: 4
Screen Saver:
  prefer blanking: yes allow exposures: yes
  timeout: 0 cycle: 0
Colors:
  default colormap: 0x20 BlackPixel: 0 WhitePixel: 16777215
Font Path:
  /home/henne/.gnome2/share/cursor-fonts,/usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi,/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,/home/henne/.gnome2/share/fonts
Bug Mode: compatibility mode is disabled
DPMS (Energy Star):
  Standby: 0 Suspend: 0 Off: 0
  DPMS is Enabled
  Monitor is On
File paths:
  Config file: /etc/X11/xorg.conf
  Modules path: /usr/lib/xorg/modules
  Log file: /var/log/Xorg.0.log

Revision history for this message
Shirish Agarwal (shirishag75) wrote :

On Intrepid it works for me (atleast atm)

xset q
Keyboard Control:
  auto repeat: on key click percent: 0 LED mask: 00000000
  auto repeat delay: 500 repeat rate: 30
  auto repeating keys: 00ffffffdffffbbf
                        fadfffdfffdfe5ef
                        ffffffffffffffff
                        ffffffffffffffff
  bell percent: 50 bell pitch: 400 bell duration: 100
Pointer Control:
  acceleration: 2/1 threshold: 4
Screen Saver:
  prefer blanking: yes allow exposures: yes
  timeout: 600 cycle: 600
Colors:
  default colormap: 0x20 BlackPixel: 0 WhitePixel: 16777215
Font Path:
  /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi,/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType
Bug Mode: compatibility mode is disabled

What is disturbing though is this line

timeout: 600 cycle: 600 I have set it at 1 minute, not 10 minutes.

DPMS (Energy Star):
  Standby: 0 Suspend: 0 Off: 0
  DPMS is Enabled
  Monitor is On
File paths:
  Config file: /etc/X11/xorg.conf
  Modules path: /usr/lib/xorg/modules
  Log file: /var/log/Xorg.0.log

Revision history for this message
Kenneth Loafman (kenneth-loafman) wrote :

Still fails for me here. Screensaver goes active but no power down.

$ aptitude show gnome-power-manager
Package: gnome-power-manager
State: installed
Automatically installed: yes
Version: 2.22.1-1ubuntu4.1
...
$ gnome-power-preferences
  [set to 20 minute timeout
$ xset q
Keyboard Control:
  auto repeat: on key click percent: 0 LED mask: 00000000
  auto repeat delay: 500 repeat rate: 30
  auto repeating keys: 00ffffffdffffbbf
                        fadfffdfffdfe5ef
                        ffffffffffffffff
                        ffffffffffffffff
  bell percent: 50 bell pitch: 400 bell duration: 100
Pointer Control:
  acceleration: 2/1 threshold: 3
Screen Saver:
  prefer blanking: yes allow exposures: yes
  timeout: 0 cycle: 0
Colors:
  default colormap: 0x20 BlackPixel: 0 WhitePixel: 16777215
Font Path:
  /home/ken/.gnome2/share/cursor-fonts,/usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi,/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,/home/ken/.gnome2/share/fonts
Bug Mode: compatibility mode is disabled
DPMS (Energy Star):
  Standby: 0 Suspend: 0 Off: 0
  DPMS is Enabled
  Monitor is On
File paths:
  Config file: /etc/X11/xorg.conf
  Modules path: /usr/lib/xorg/modules
  Log file: /var/log/Xorg.0.log

Revision history for this message
Bartek Celary (karaphka) wrote :

I have the same problem from at least 6 months. Currently on latest Jaunty. The xset/xset q/gnome-power-preferences/xset q reproduction also shows the timers are reset. The monitor does not suspend. It only does it once after gnome log in.

Revision history for this message
Martin Pool (mbp) wrote :

This seems to be broken in Jaunty too.

If I run 'xset dpms force off' (or suspend or sleep) then it turns off correctly.

summary: - [Hardy] display doesn't go to sleep after today's gnome-power-manager
- update
+ display doesn't go to DPMS sleep
Revision history for this message
Martin Pool (mbp) wrote :

As a workaround, you can run 'xset dpms 300' (in each session) which will turn on power saving at a lower level.

Changed in gnome-power-manager (Ubuntu):
status: Fix Released → Confirmed
Revision history for this message
Scott Howard (showard314) wrote :

Discussion of a similar bug in Karmic is going on here: bug #385633

Revision history for this message
Patrick Pfeifer (patrick2000) wrote :

my god .... after aiming for one decade to establish linux as desktop os, it still doesn't have a working screensaver .... :-((

Revision history for this message
AndreK (andre-k) wrote :

same problem with workstation with Nvidia card - "xset dpms force off" works.
Setting off-time in power-manager does *not* work.

Revision history for this message
AndreK (andre-k) wrote :

Additional info: I am using updated Karmic Koala beta.

Revision history for this message
Flo (spam01) wrote :

Same problem here on an Eee PC 1005HA-H with Intel 945GM graphics, running latest Karmic Netbook Remix.

Screen goes blank but does not shut off. "xset dpms force off" correctly disables the screen.

Revision history for this message
Daniel Arseneault (danielarseno-gmail) wrote :

Same problem confirmed for my Aspire One 250 netbook. An icon of a screen with arrows in the corners appears in the notification area instead, and goes away as soon as you move the mouse or hit a key.

Revision history for this message
Daniel Arseneault (danielarseno-gmail) wrote :

Screen seems to blank fine when gnome-screensaver is disabled. The problem could be with the screensaver.

Revision history for this message
Rola (pabswiss) wrote :

same here with eee 1005ha-P. on karmic final.

using xset-dpms works, but nothing else.

I disabled screensaver to see if it actually sleeps, but I'm not confident since trying to turn off the screen through eeepc-acpi hotkey doesn't work either (I just get a notification on screen saying "Display OFF", lovely but otherwise useless).

Revision history for this message
Twisted Lincoln, Inc. (twistedlincoln) wrote :

Using "xset dpms force standby" works properly for me once the screensaver is completely disabled. Otherwise, I have the same issues reported here.

Revision history for this message
Lemmiwinks (lemmiwinks) wrote :

same problem for me on a dell 1520 laptop. "xset dpms force off" works correctly...

Revision history for this message
João Gomes (jvpgomes) wrote :

The problem still exists in Lucid.

Revision history for this message
Guillermo Simeon (p-contact-espacecode-net-deactivatedaccount) wrote :

I have a kid computer with same problem.

Problem :
The screen doesn't sleep-standby-off with gnome-power-manager settings ok

Installation :
1-Ubuntu 10.10
2-Qimo packages

Computer :
Toshiba satellite a10
Intel 852/855 gm graphic

Workaround :
Terminal
xset +dpms

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.