Power Management Settings Are Not Applied / Retained

Bug #406599 reported by tekstr1der
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gnome-power-manager (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Binary package hint: gnome-power-manager

Upon updating to gnome-power-manager (2.27.2+git20090729-0ubuntu2), settings found under System>Preference>Power Management are ignored after being set. After exiting Power Management, immediately opening it again will show the customizations just made, however, enacting a power event such as closing laptop lid will not only ignore the setting (does not suspend, though the option is selected), but will revert all settings back to default (check power management and see all settings reverted).

The same hold true for other settings such as pressing the suspend button. Even after setting it to suspend in Power Managment, it does nothing.

Also, clicking on the "Make Default" button appears to have no effect on any of this. All settings return to the defaults that ship with gnome-power-manager.

ProblemType: Bug
Architecture: i386
Date: Wed Jul 29 16:30:34 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: wl
Package: gnome-power-manager 2.27.2+git20090729-0ubuntu2
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-4.23-generic
SourcePackage: gnome-power-manager
Uname: Linux 2.6.31-4-generic i686

Revision history for this message
tekstr1der (tekstr1der) wrote :
Revision history for this message
Kai Jauch (kaijauch) wrote :

I tried to reproduce it, but couldn't. My settings are stored and still displayed after closing and reopening "Power Management". Everything is working fine here.

Could it be that your disk is full and the configuration thus cannot be saved to disk?

gnome-power-manager:
  Installed: 2.27.2+git20090729-0ubuntu2
  Candidate: 2.27.2+git20090729-0ubuntu2
  Version table:
 *** 2.27.2+git20090729-0ubuntu2 0
        500 http://de.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

Revision history for this message
tekstr1der (tekstr1der) wrote :

No, disk is not nearly full.

As I stated in the report, closing and reopening Power Management WILL show the customizations you have made. However, after a suspend or hibernate or reboot, the settings will revert to shipped defaults. My settings don't stick.

Revision history for this message
Kai Jauch (kaijauch) wrote :

Whoops, misread that, sorry. It would appear that the settings I make are honoured, though. If I set suspend on lid-close, it suspends fine (and the settings are still there after I resume), if I set it to do nothing, it does nothing.
However, rebooting makes them revert to default.

Revision history for this message
Kai Jauch (kaijauch) wrote :

Logging out seems to suffice in order to make the settings revert to default.

Revision history for this message
Scott Howard (showard314) wrote :

Thanks for the report. I can't reproduce this bug either (after suspending the settings are still the same). We can try some things to figure out what is causing this.

First, you can follow the instructions at:
https://wiki.ubuntu.com/DebuggingGNOMEPowerManager#Getting%20info%20from%20GPM
to run gnome-power-manager in verbose mode. When shutting down/resuming, see if any messages show up in the terminal.

Second, you can reset your gnome-power-manager gconf settings to the default. You can follow the instructions here:
https://wiki.ubuntu.com/DebuggingGNOMEPowerManager#Getting%20GConf%20values
You should back up your current gconf settings prior to resetting to default (there are instructions on how to back them up). Once they are reset to the default, see if the bug persists.

Changed in gnome-power-manager (Ubuntu):
status: New → Incomplete
Revision history for this message
tekstr1der (tekstr1der) wrote :

Okay, thanks for the debugging steps. This seems to be multiple issues. As Kai Jauch confirmed, the settings are indeed reverting to default after logout/login or reboot. That is issue #1 and is primary to the original bug report. To be fair, setting the option to suspend upon laptop lid closed has not been working for me in Karmic for some time. Worked fine with Intrepid and Jaunty. This compounds the issue, but here are some results from debugging:

1.)Reset power options to default with: $ gconftool --recursive-unset /apps/gnome-power-manager
2.)Launching Preferences>Power Management shows most drop lists are blank or say "Do nothing". Specifically, under the Battery Power tab, laptop lid closed has "Do Nothing" selected.
3.)$ killall gnome-power-manager
4.)$ gnome-power-manager --verbose --no-daemon
5.)close laptop lid, screen is blank
6.)open laptop lid, screen is displayed
7.)use the battery applet in panel to suspend, wait 30 second while suspended, resume from suspend
8.)terminal shows: (gnome-power-manager:3755): devkit-power-gobject-DEBUG: DBUS timed out, but recovering
9.)open Preferences>Power Management. Select Battery Tab, change option for laptop lid closed to suspend
9.)close laptop lid. screen is blank. no suspend. setting is ignored
10.)open laptop lid. screen is displayed.
11.)open Preferences>Power Management. Select Battery Tab, observe laptop lid closed option is now set to "Blank screen"

Any more info I could provide to help with this?

Revision history for this message
Scott Howard (showard314) wrote : Re: [Bug 406599] Re: Power Management Settings Are Not Applied / Retained

Thanks for the debugging info. We have some more commits coming
through over the next week (I believe 2.27.3-0ubuntu1 will be
officially released Monday on Ubuntu). Let's try to test again once it
is released. I'll leave it incomplete for now until we try against the
newest release.

tags: added: ping-2.27.3
Revision history for this message
Scott Howard (showard314) wrote :

The bug still exists, I'm condensing similar bug reports to: bug 407491. Please follow that bug and add any additional information.

tags: removed: ping-2.27.3
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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