GNOME Bugzilla – Bug 622361
no battery preferences after switching to battery during the hibernation
Last modified: 2010-11-07 01:56:45 UTC
If I hibernate the computer when on ac power and then during the hibernation, I unplug the computer and put the battery in and then resume, I do not get battery preferences tab and so I can not change the preferences... I am using g-p-m 2.30.1.
What's the output of "upower --dump" or "devkit-power --dump" when you've resumed?
Here it is, after hibernation and no battery prefs around...(BTW, if it matters at all, I do get a battery icon appearing in the notification area..) Device: /org/freedesktop/DeviceKit/Power/devices/battery_BAT1 native-path: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:0e/PNP0C0A:00/power_supply/BAT1 vendor: TOSHIBA model: PA3535U serial: 41167 power supply: yes updated: Tue Jun 22 14:19:11 2010 (13 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable: yes state: discharging energy: 42.336 Wh energy-empty: 0 Wh energy-full: 43.2 Wh energy-full-design: 43.2 Wh energy-rate: 0 W voltage: 10.8 V percentage: 98% capacity: 100% technology: lithium-ion History (charge): 1277205546 98.000 discharging 1277205546 0.000 unknown History (rate): 1277205546 0.000 unknown Device: /org/freedesktop/DeviceKit/Power/devices/line_power_ACAD native-path: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:0e/ACPI0003:00/power_supply/ACAD power supply: yes updated: Tue Jun 22 14:19:06 2010 (18 seconds ago) has history: no has statistics: no line-power online: no Daemon: daemon-version: 014 can-suspend: yes can-hibernate yes on-battery: yes on-low-battery: no lid-is-closed: no lid-is-present: yes
Are you closing and re-opening the prefs window?
yes, of course.
Right, I think I've found the cause. I think this bug is a dupe of https://bugzilla.gnome.org/show_bug.cgi?id=617529 and that it should work if you try 2.31.3.
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of bug 617529 ***