if laptop lid already closed, doesn't detect when it should suspend when mains power removed

[Rachel Greenham]

Binary package hint: gnome-power-manager

This looks like bugs 66126 or 31967; however both are quite old bugs marked as "fix released" a long time ago. So I guess this is a regression of one or the other...

Settings are
On AC Power, lid-closed should go to Blank Screen.
On Battery, lid-closed should suspend.

So on AC power, I close the lid. It goes to blank screen.

Later, I unplug the power. It should go to suspend, but it doesn't. It remains on blank-screen until the lid is opened and the screen woken up, then closed again.

Maybe problem is you're watching for transition events rather than having a state machine? After all, no new lid-closed event would have happened when the power was removed. So it's looking for the *event* "lid closing" rather than the *state* "lid is closed". Surely it should go: "Something changed. State is now: battery power, lid closed, therefore I need to suspend".

(for values of "you" that are probably upstream, I guess. :-) )

ProblemType: Bug
Architecture: i386
Date: Sun Oct 4 23:12:07 2009
DistroRelease: Ubuntu 9.10
Package: gnome-power-manager 2.28.0-0ubuntu1
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
SourcePackage: gnome-power-manager
Tags: ubuntu-unr
Uname: Linux 2.6.31-11-generic i686
XsessionErrors:
 (gnome-settings-daemon:1663): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:1663): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:1721): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:1804): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (netbook-launcher:1724): Clutk-CRITICAL **: ctk_button_focus_activate: assertion `CTK_IS_BUTTON (focusable)' failed

[Mark Cariaga (mzc)]

this is almost close to bug# 487958. but my acer aspire one D250 suspends on AC unplug and re-plug.

[Ryan Thompson (rct86)]

If I recall correctly, there's a hidden gconf key to enable exactly this behavior. Browse around in gconf-editor.

[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.

[Juan Pablo Arias (j4np0l)]

You can configure this behavior by doing the following:

1. Run gconf-editor

2. Go to >apps>gnome-power-manager>actions

3. Check the box next to event_when_closed_battery

Also, on Maverick, this is the default (and it's working like it should, tested with an Asus eee 1001px and Ubuntu 10.10 NE).

Rachel (or anyone else), it would be great if you could confirm that by doing that this problem gets solved.

Thanks in advance

[Rachel Greenham (rachel-strangenoises)]

I don't have access to the machine I was using when I originally reported this (an Asus 1008HA) as it's been lent to a family member. However, I now have Maverick installed dual-boot on my Macbook Pro (ubuntu-desktop, not netbook edition) and can report that the behaviour is indeed as expected now.

For the avoidance of doubt, "as expected" means as per original report, options laptop lid closed on mains->blank screen; laptop lid closed on battery->suspend; close lid on mains, it blanks screen but keeps running; pull mains lead out, it suspends. This is, for me at least, the desired and expected behaviour, so I think we can close this. :-)

[Juan Pablo Arias (j4np0l)]

This bug report is being closed due to your last comment regarding this being fixed with an update. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

[A. Bram Neijt (bneijt)]

I can't get the Maverick behavior to work in Oneiric.

http://mail.gnome.org/archives/commits-list/2010-November/msg06088.html

seems to state that earlier mentioned solutions will not work.

I consider this a problem with Oneiric and can't find how to fix it so the behavior is like reported above.