GNOME Bugzilla – Bug 594760
dpms broken again
Last modified: 2020-11-06 20:13:56 UTC
Since a couple of weeks gpm fails to turn off any screens. After the specified time the screen turns off for half a second only to return immediately. This repeats itself forever. Im using gpm 2.27.92 on ubuntu karmic on 3 different computers (2 all-intel thinkpads and a amd+nvidia desktop). Output from gpm --verbose: - emitting idle-changed : (0) TI:18:38:43 TH:0x9385168 FI:gpm-idle.c FN:gpm_idle_session_idle_changed_cb,357 - Received gnome session idle changed: 0 TI:18:38:43 TH:0x9385168 FI:gpm-idle.c FN:gpm_idle_evaluate,213 - session_idle=0, session_inhibited=0, x_idle=1 TI:18:38:43 TH:0x9385168 FI:gpm-idle.c FN:gpm_idle_idletime_reset_cb,394 - idletime reset TI:18:38:43 TH:0x9385168 FI:gpm-idle.c FN:gpm_idle_evaluate,213 - session_idle=0, session_inhibited=0, x_idle=0 TI:18:38:43 TH:0x9385168 FI:gpm-idle.c FN:gpm_idle_set_mode,133 - Doing a state transition: normal TI:18:38:43 TH:0x9385168 FI:gpm-backlight.c FN:gpm_backlight_notify_system_idle_changed,451 - we have just been idle for 60,431086s TI:18:38:43 TH:0x9385168 FI:gpm-backlight.c FN:gpm_backlight_notify_system_idle_changed,476 - changing powersave idle status to 0 TI:18:38:43 TH:0x9385168 FI:gpm-backlight.c FN:gpm_backlight_brightness_evaluate_and_set,202 - no dimming hardware TI:18:38:43 TH:0x9385168 FI:gpm-idle.c FN:gpm_idle_evaluate,238 - X not idle timeout was set to 1m. The msg "X not idle" appears right after the screens come back from their half-a-second sleep. output from gp-bugreport: Distro version: squeeze/sid Kernel version: 2.6.31-9-generic g-p-m version: 2.27.92 HAL version: 0.5.13 System manufacturer: missing System version: missing System product: missing AC adapter present: no Battery present: no Laptop panel present: no CPU scaling present: yes Battery Information: DeviceKit data: Daemon: daemon-version: 010 can-suspend: yes can-hibernate yes on-battery: no on-low-battery: no lid-is-closed: no lid-is-present: no GNOME Power Manager Process Information: HAL Process Information: 111 25163 0.0 0.1 6644 2200 ? Ss Sep07 0:01 /usr/sbin/hald root 25164 0.0 0.0 3568 1160 ? S Sep07 0:00 \_ hald-runner root 25208 0.0 0.0 3644 1168 ? S Sep07 0:18 \_ hald-addon-storage: polling /dev/sr0 (every 2 sec) root 25212 0.0 0.0 3656 920 ? S Sep07 0:00 \_ /usr/lib/hal/hald-addon-cpufreq 111 25213 0.0 0.0 3464 908 ? S Sep07 0:00 \_ hald-addon-acpi: listening on acpid socket /var/run/acpid.socket root 25226 0.0 0.0 3672 1276 ? S Sep07 0:58 \_ hald-addon-input: Listening on /dev/input/event0 /dev/input/event1 /dev/input/event3 /dev/input/event4
I can confirm this behaviour; running ubuntu karmic. (intel graphics) I have set the timeout to turn off the monitor to 1 minute. After 1 minute the monitor turns off but is immediately turned on again. I have attached a full log of this behaviour. (gpm --verbose)
Created attachment 143110 [details] GPM log: turning off screen fails
Confirming with 2.27.92-0ubuntu1
2.28 released with this bug still open??
(In reply to comment #4) > 2.28 released with this bug still open?? No, ubuntu need to add two patches to the xserver. See http://blogs.gnome.org/hughsie/2009/08/17/gnome-power-manager-and-blanking-removal-of-bodges/
Thanks richard. so can this bug be closed?
Ubuntu has had the patches since they were available. That doesn't rule out potential differences between xorg-server 1.6 and 1.7 which might result in this. I tried F12alpha, but the screensaver refused to start ;)
richard: these patches are already applied in ubuntu. "xset dpms force off" can turn the monitor off. g-p-m is not able to do so. (the monitor goes on again immediatley after g-p-m tries to turn it off)
Right, I confirm what Dominik says, we should have all patches linked in the evil gpm/xorg/idle threads already, but whem gpm shuts down the screen it turns on immediately, while xset dpms force off works.
Richard: There was a third patch that was needed :) http://cgit.freedesktop.org/xorg/xserver/commit/?id=c1d901d723c3bee523736eacc15b44a7dff484fe Things seem to be working with it, so this bug should be closed. Sorry for the hassle.
I still have a minor issue with gpm-2.29.1 (on Ubuntu Karmic). The Screen is always and reliably shut off, but i cant get any timeouts longer than 10m. If i set it to 30m or 1h it will still turn off the screen after 10m. Here is the --verbose output after i set it to 1h: TI:03:19:14 TH:0x890c168 FI:gpm-idle.c FN:gpm_idle_evaluate,275 - setting up blank callback for 3600s TI:03:20:04 TH:0x890c168 FI:gpm-session.c FN:gpm_session_presence_status_changed_cb,133 - emitting idle-changed : (1) TI:03:20:04 TH:0x890c168 FI:gpm-idle.c FN:gpm_idle_session_idle_changed_cb,357 - Received gnome session idle changed: 1 TI:03:20:04 TH:0x890c168 FI:gpm-idle.c FN:gpm_idle_evaluate,213 - session_idle=1, session_inhibited=0, x_idle=1 TI:03:29:08 TH:0x890c168 FI:gpm-idle.c FN:gpm_idle_idletime_reset_cb,394 - idletime reset TI:03:29:08 TH:0x890c168 FI:gpm-idle.c FN:gpm_idle_evaluate,213 - session_idle=1, session_inhibited=0, x_idle=0 TI:03:29:08 TH:0x890c168 FI:gpm-idle.c FN:gpm_idle_set_mode,133 - Doing a state transition: normal TI:03:29:08 TH:0x890c168 FI:gpm-backlight.c FN:gpm_backlight_notify_system_idle_changed,506 - we have just been idle for 593,422179s TI:03:29:08 TH:0x890c168 FI:gpm-backlight.c FN:gpm_backlight_notify_system_idle_changed,524 - resetting idle dim time to 10s TI:03:29:08 TH:0x890c168 FI:gpm-idle.c FN:gpm_idle_set_timeout_dim,302 - Setting dim idle timeout: 10s TI:03:29:08 TH:0x890c168 FI:gpm-backlight.c FN:gpm_backlight_notify_system_idle_changed,531 - changing powersave idle status to 0 TI:03:29:08 TH:0x890c168 FI:gpm-backlight.c FN:gpm_backlight_brightness_evaluate_and_set,298 - 1. main brightness 1,000000 TI:03:29:08 TH:0x890c168 FI:gpm-backlight.c FN:gpm_backlight_brightness_evaluate_and_set,318 - 2. battery scale 1,000000, brightness 1,000000 TI:03:29:08 TH:0x890c168 FI:gpm-backlight.c FN:gpm_backlight_brightness_evaluate_and_set,336 - 3. idle scale 1,000000, brightness 1,000000 TI:03:29:08 TH:0x890c168 FI:gpm-brightness.c FN:gpm_brightness_trust_cache,107 - using cache for value 100 (probably okay) TI:03:29:08 TH:0x890c168 FI:gpm-backlight.c FN:gpm_backlight_brightness_evaluate_and_set,344 - values are the same, no action TI:03:29:08 TH:0x890c168 FI:gpm-idle.c FN:gpm_idle_evaluate,238 - X not idle TI:03:29:08 TH:0x890c168 FI:gpm-session.c FN:gpm_session_presence_status_changed_cb,133 - emitting idle-changed : (0) TI:03:29:08 TH:0x890c168 FI:gpm-idle.c FN:gpm_idle_session_idle_changed_cb,357 - Received gnome session idle changed: 0 TI:03:29:08 TH:0x890c168 FI:gpm-idle.c FN:gpm_idle_evaluate,213 - session_idle=0, session_inhibited=0, x_idle=0 TI:03:29:08 TH:0x890c168 FI:gpm-idle.c FN:gpm_idle_evaluate,238 - X not idle TI:03:29:21 TH:0x890c168 FI:gpm-idle.c FN:gpm_idle_idletime_alarm_expired_cb,379 - idletime alarm: 1
Still not fixed in 2.30
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years. If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/gnome-power-manager/-/issues/ Thank you for reporting this issue and we are sorry it could not be fixed.