Gnome Power Manager fails to put display to sleep

[ENigma885]

Binary package hint: gnome-power-manager

***Problem:-
- Gnome Power Manager (GPM) fails to put display to sleep after the assigned time.
____________
***Environment:-
1- Ubuntu 9.10 (development version) i386
2- 2.6.31-10-generic Linux kernel
3- Gnome Display Manager 2.27.90-0ubuntu6
4- VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02)
___________
***Details:-

    **What was expected:-
- The display should put to sleep after the preconfigured time in GPM's "Put display to sleep when in active for: X minute/s" elapses.

    **What happens instead:-
- The screen only flashes in the following pattern and is not powered off:
1- when inactive for 1 minute ---> not slept in more than 3:40 minutes + screen flashes after 1:10, 2:20, 3:30..etc
2- when inactive for 5 minutes ---> not slept in more than 15 minutes + screen flashes after 5:10, 10:20..etc
3- when inactive for 10 minutes --> not slept in more than 25 minutes + screen flashes after 10:10, and 20:20 etc
____________
***Attachments :-
1-"usr/share/gnome-power-manager/gnome-power-bugreport"
2- The output from "devkit-power -d".
____________
**Notes:-
- if more attachments r needed please let me know.

ProblemType: Bug
Architecture: i386
Date: Thu Sep 17 04:24:59 2009
DistroRelease: Ubuntu 9.10
Package: gnome-power-manager 2.27.92-0ubuntu1
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.34-generic
SourcePackage: gnome-power-manager
Uname: Linux 2.6.31-10-generic i686

[Christoph Schwyn (christoph-schwyn)]

Same here on a Thinkpad X200s.

[Daniel Arseneault (danielarseno-gmail)]

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.

[ENigma885 (enigma-pentagram)]

Christoph Schwyn and Daniel Arseneault...Can u please confirm having an intel integrated VGA?

[Daniel Arseneault (danielarseno-gmail)]

Yes:
Integrated Graphics Chipset: Intel(R) 945GME

I've also noticed that the screen blanks ok when I disable gnome-screensaver, so the problem could have nothing to do with gnome-power-manager.

[Mikk (mikkkogu)]

i have same problem with my fujitsu siemens sa3650, display goes black but backlight stays on

[guardian626 (guardian626)]

Same problem with GeForce 7600 GT (Nvidia driver 185.18.36) connected to Dell P2310H on Ubuntu 9.10 x86_64.

[João Gomes (jvpgomes)]

I'm not 100% sure that this is the same problem that I'm experimenting, but I think so.

When I turn on the computer and I log in, the display seems to go sleep when it is supposed to go.
However, after a while, the display stops going to the sleep mode when it is inactive and I can see the same icon, with the arrows in the corners, in the notification area.
I have been trying, for a long time, to find out what causes this change in the display behavior, but I couldn't understand what it is.

I noticed that, if I take out the laptop battery and put it again, or vice versa, the display starts failing to go to the sleeping mode. But I couldn't exactly notice a concrete pattern.

If I kill the gnome-power-management process and start it again, everything seems to work properly again.

I also saw the following when running the gnome-power-management in verbose mode:
"TI:23:11:17 TH:0x9146168 FI:gpm-manager.c FN:gpm_manager_idle_changed_cb,632
 - lid is closed, so we are ignoring ->NORMAL state changes"

Why does it say that the lid is close if it is open?
Maybe this has no importance... I don't know.

I have the screensaver disabled.

I have an intel integrated video chipset.

Thank you!

[João Gomes (jvpgomes)]

There is another unexpected behavior that I forgot to mention.

If I turn on the laptop with the battery plugged, in the power management preferences, there are three tabs: On AC Power; On Battery Power; and General.
However, if I turn on the laptop without the battery attached, I can only see two tabs: On AC Power and General.

This is not completely absurd.

But, if I plug the battery with the computer on, it still show only the two tabs: On AC Power and General. And even if I then unplug the AC power and use only the battery power, I continue to see only the same two tabs in the power management preferences.

I don't know if this is related with the problem reported or if it is a new and independent problem.

Thank you!

[João Gomes (jvpgomes)]

Sorry, I also forgot to mention that I updated from Jaunty to Karmic.
In Jaunty, everything was working properly.

[ENigma885 (enigma-pentagram)]

**Just to clear things up:
The problem seems to be related to the update process from Jaunty to Karmic and not Karmic itself. As when I made a clean install for Karmic, the problem completely disappeared.
[Conclusion:- As a workaround, you can try a clean install from scratch]

**So, can all you please confirm doing an update form Jaunty to Karmic?

[João Gomes (jvpgomes)]

I'm not sure if I understood correctly.
Did you suggest to try a clean install of Karmic or to updated from Jaunty to Karmic?

I'm woking on an important project, and I cannot make a clean install of ubuntu in my computer right now.
Maybe in a few months I'll do it.

[ENigma885 (enigma-pentagram)]

@João Gomes
Exactly, I'm suggesting to clean install. However, I'm not pretty sure of the results. All I said is a just hypothesis of the problem being related to the Jaunty-Karmic update process.

And I was trying to confirm my hypothesis by asking all the affected ppl if they've updated to Karmic through Jaunty or not.

[João Gomes (jvpgomes)]

Ok, I'll add more information when I install Karmic from a clean state.
Thank you!

[João Gomes (jvpgomes)]

This is not a solution, nor even a workaround. It's more a alternative for those of you who, like my self, cannot make a clean install of Karmic right now.
The power manager tool from Xfce works pretty well. The version in the repositories still has this bug:
http://bugzilla.xfce.org/show_bug.cgi?id=6008
But it is not very important for me.

Merry Christmas!

[João Gomes (jvpgomes)]

Hi!

I just made a clean install of Lucid and the problem remains. It is really annoying... :s

I also noticed the following warning messages which I don't know if they're important:

TI:01:24:09 TH:0x94746d8 FI:gpm-button.c FN:gpm_button_xevent_key,203
 - could not map keysym 1008ffa8 to keycode

(gnome-power-manager:18687): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.24.0/gobject/gsignal.c:2273: signal `proxy-status' is invalid for instance `0x94d9270'

TI:01:24:09 TH:0x94746d8 FI:gpm-brightness-hal.c FN:gpm_brightness_hal_init,455
 - No devices of capability laptop_panel

TI:01:24:09 TH:0x94746d8 FI:gpm-phone.c FN:gpm_phone_dbus_connect,261
 - Cannot connect, maybe the daemon is not running: Could not get owner of name 'org.gnome.phone': no such name

TI:01:24:09 TH:0x94746d8 FI:gpm-phone.c FN:gpm_phone_coldplug,76
 - not connected

Appeared here:

 - Verbose debugging 1 (on console 1)GPM_VERBOSE
TI:01:24:09 TH:0x94746d8 FI:gpm-main.c FN:main,210
 - GNOME Power Manager 2.30.0
TI:01:24:09 TH:0x94746d8 FI:gpm-session.c FN:gpm_session_init,511
 - idle: 1, idle_inhibited: 0, suspend_inhibited: 0
TI:01:24:09 TH:0x94746d8 FI:gpm-session.c FN:gpm_session_register_client,367
 - registered startup '(null)' to client id '/org/gnome/SessionManager/Client33'
TI:01:24:09 TH:0x94746d8 FI:egg-console-kit.c FN:egg_console_kit_init,304
 - ConsoleKit session ID: /org/freedesktop/ConsoleKit/Session2
TI:01:24:09 TH:0x94746d8 FI:gpm-button.c FN:gpm_button_grab_keystring,176
 - Grabbed modmask=8000, keycode=124
TI:01:24:09 TH:0x94746d8 FI:gpm-button.c FN:gpm_button_grab_keystring,176
 - Grabbed modmask=8000, keycode=213
TI:01:24:09 TH:0x94746d8 FI:gpm-button.c FN:gpm_button_grab_keystring,176
 - Grabbed modmask=8000, keycode=150
TI:01:24:09 TH:0x94746d8 FI:gpm-button.c FN:gpm_button_xevent_key,203
 - could not map keysym 1008ffa8 to keycode
TI:01:24:09 TH:0x94746d8 FI:gpm-button.c FN:gpm_button_grab_keystring,176
 - Grabbed modmask=8000, keycode=233
TI:01:24:09 TH:0x94746d8 FI:gpm-button.c FN:gpm_button_grab_keystring,176
 - Grabbed modmask=8000, keycode=232
TI:01:24:09 TH:0x94746d8 FI:gpm-button.c FN:gpm_button_grab_keystring,176
 - Grabbed modmask=8000, keycode=160
TI:01:24:09 TH:0x94746d8 FI:gpm-button.c FN:gpm_button_grab_keystring,176
 - Grabbed modmask=8000, keycode=244
TI:01:24:09 TH:0x94746d8 FI:gpm-button.c FN:gpm_button_grab_keystring,176
 - Grabbed modmask=8000, keycode=238
TI:01:24:09 TH:0x94746d8 FI:gpm-button.c FN:gpm_button_grab_keystring,176
 - Grabbed modmask=8000, keycode=237
TI:01:24:09 TH:0x94746d8 FI:gpm-button.c FN:gpm_button_grab_keystring,176
 - Grabbed modmask=8000, keycode=236

(gnome-power-manager:18687): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.24.0/gobject/gsignal.c:2273: signal `proxy-status' is invalid for instance `0x94d9270'
TI:01:24:09 TH:0x94746d8 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_setup_display,170
 - No outputs have backlight property
TI:01:24:09 TH:0x94746d8 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_init,717
 - no XRANDR extension, so aborting init
TI:01:24:09 TH:0x94746d8 FI:egg-dbus-proxy.c FN:egg_dbus_proxy_connect,73
 - already connected to org.freedesktop.Hal
TI:01:24:09 TH:0x94...

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. A new version of GNOME Power Manager is available on Maverick and we are wondering if this bug is still an issue for you with that version? Could you please test and comment back? Thanks in advance.

[Mikk (mikkkogu)]

now it's working, but still there is prblem with resuming from sleep, but i think this is different problem and story with my Amilo Sa 3650

[João Gomes (jvpgomes)]

No, it's not working.
It still presents the same behavior.

For instance, right now I booted the laptop unplugged from power. After one hour of working, I plugged it and the display stopped going to sleep.

I'm running a clean installation of Maverick.

I was also looking at the changelog document of the latest version of the gnome-power-manager package and I didn't see any information about a correction of this problem, so it would be expectable that it could continue to exist in Maverick.

This problem exists since gnome-power-manager stopped using HAL.
I will continue to use Xfce power manager as it is much more reliable and stable. By the way, Xfce power manager is still using HAL.

From what I could read from other users it may also be a problem restricted to computers with intel graphics. But I cannot confirm this.

Again, I'd like to emphasize the following message that I can see when running gnome power manager with verbose mode:
"lid is closed, so we are ignoring ->NORMAL state changes"
And, obviously, the lid is NOT closed.

And, the following is what is showed when the laptop display should, supposedly go off, when I move the mouse.

TI:17:14:54 TH:0x887c8b8 FI:gpm-tray-icon.c FN:gpm_tray_icon_add_device,261
 - adding device /org/freedesktop/UPower/devices/battery_BAT0
TI:17:14:58 TH:0x887c8b8 FI:gpm-idle.c FN:gpm_idle_set_mode,108
 - Doing a state transition: blank
TI:17:15:03 TH:0x887c8b8 FI:gpm-idle.c FN:gpm_idle_idletime_reset_cb,391
 - idletime reset
TI:17:15:03 TH:0x887c8b8 FI:gpm-idle.c FN:gpm_idle_evaluate,187
 - session_idle=0, idle_inhibited=0, suspend_inhibited=0, x_idle=0
TI:17:15:03 TH:0x887c8b8 FI:gpm-idle.c FN:gpm_idle_set_mode,108
 - Doing a state transition: normal
TI:17:15:03 TH:0x887c8b8 FI:gpm-manager.c FN:gpm_manager_idle_changed_cb,804
 - lid is closed, so we are ignoring ->NORMAL state changes
TI:17:15:03 TH:0x887c8b8 FI:gpm-idle.c FN:gpm_idle_evaluate,192
 - X not idle

[João Gomes (jvpgomes)]

I could finally understand a way of reproducing this problem.

I have ubuntu maverick, fully updated, with an Intel graphics chipset.

The laptop has the battery attached and is plugged to the power.

After booting, when the computer is idle, the display goes off as it should.
However, if I close the lid and then open it, the display cannot go off anymore when the computer is idle.
The output of the verbose mode is similar to what I described in the previous comment.

This is not the only case in which this problem happens, but it is till now the only one in which I can always reproduce the problem.

[João Gomes (jvpgomes)]

I forgot to say that, even if kill and restart the gnome power manager, the problem remains.

The only way is to reboot or at least go to sleep mode and come back.

[João Gomes (jvpgomes)]

I think (but I'm not an expert on this) that the situation that I reported may be related with this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/376793

Though it isn't the same problem, it seems to be the same cause.