gnome-power-manager doesn't properly detect power state

[Nick B.]

Binary package hint: gnome-power-manager

gnome-power-manager doesn't correctly detect the power state on my laptop (HP Pavilion dv6500t). When I pull the AC plug out it detects that it was unplugged because the battery icon shows up in the notification area. However when I hover over the icon it still says that it's running on AC power. This makes the "on battery" power management settings invalid since it still thinks it's running on AC. i.e. the screen doesn't dim, the screen doesn't turn off after 15 minutes as specified for "On battery power" etc.

Steps to reproduce
1. Unplug AC power cord
2. Wait for battery icon to appear in the notification area
3. Hover over the icon with the mouse and notice it says that it's running on AC when it's clearly running on battery
4. Notice that none of the "on battery power" preferences take effect since it still thinks it's on AC power

What should happen
Batter icon should appear and indicate that it is running on battery power and "on battery power" preferences should be in effect.

This might be specific to this model of laptop as I have another laptop I can't reproduce this on.

ProblemType: Bug
ACAdapter: Present
Architecture: amd64
Battery: Present
CPUScaling: Present
DistroRelease: Ubuntu 9.04
LaptopPanel: Present
NonfreeKernelModules: nvidia
Package: gnome-power-manager 2.24.2-2ubuntu8
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
SourcePackage: gnome-power-manager
Uname: Linux 2.6.28-11-generic x86_64

$ dbus-monitor --session "type='signal',interface='org.freedesktop.PowerManagement'"

signal sender=org.freedesktop.DBus -> dest=:1.242 serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired string ":1.242"

Disconnecting the power and reconnecting it doesn't give any output in
the dbus-monitor

[Scott Howard (showard314)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please attach the following to the report?

The output of:
dbus-monitor --session "type='signal',interface='org.freedesktop.PowerManagement'"

Can you attach the file gpm.gconf.values.txt and gpm.log to this report after running:
gconftool --recursive-list /apps/gnome-power-manager > gpm.gconf.values.txt
/usr/share/gnome-power-manager/gnome-power-bugreport &> gpm.log

Thanks in advance.

[Nick B. (futurepilot)]

Scott Howard wrote:
> Thanks for taking the time to report this bug and helping to make Ubuntu
> better. Could you please attach the following to the report?
>
> The output of:
> dbus-monitor --session "type='signal',interface='org.freedesktop.PowerManagement'"
>
> Can you attach the file gpm.gconf.values.txt and gpm.log to this report after running:
> gconftool --recursive-list /apps/gnome-power-manager > gpm.gconf.values.txt
> /usr/share/gnome-power-manager/gnome-power-bugreport &> gpm.log
>
> Thanks in advance.
>
> ** Changed in: gnome-power-manager (Ubuntu)
> Status: New => Incomplete
>
>
dbus-monitor --session "type='signal',interface='org.freedesktop.PowerManagement'"
signal sender=org.freedesktop.DBus -> dest=:1.179 serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired
   string ":1.179"

Strangely I've found that if I run "cat /proc/acpi/ac_adapter/ACAD/state" it seems to give something a poke
and it starts working properly for a while. Eventually it goes back to incorrectly reporting the power state.

[Scott Howard (showard314)]

Marking as confirmed since Mandriva is experiencing the same bug.
https://qa.mandriva.com/show_bug.cgi?id=50087

@Nick:
Can you do
1) run: dbus-monitor --session "type='signal',interface='org.freedesktop.PowerManagement'"
2) unplug your AC adapter
3) plug in your AC adapter
4) post the output from dbus-monitor

I'll let Mandriva know about this report and see if we have enough info between our two reports to go upstream with it.

[Nick B. (futurepilot)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Scott Howard wrote:
> Marking as confirmed since Mandriva is experiencing the same bug.
> https://qa.mandriva.com/show_bug.cgi?id=50087
>
> @Nick: Can you do 1) run: dbus-monitor --session
> "type='signal',interface='org.freedesktop.PowerManagement'" 2)
> unplug your AC adapter 3) plug in your AC adapter 4) post the
> output from dbus-monitor
>
> I'll let Mandriva know about this report and see if we have enough
> info between our two reports to go upstream with it.
>
> ** Bug watch added: Mandriva Linux #50087
> http://qa.mandriva.com/show_bug.cgi?id=50087
>
> ** Also affects: gnome-power-manager (Mandriva) via
> http://qa.mandriva.com/show_bug.cgi?id=50087 Importance: Unknown
> Status: Unknown
>
> ** Changed in: gnome-power-manager (Ubuntu) Status: Incomplete =>
> Confirmed
>

Ok, I followed the steps in that order, but I'm not getting anything
more than this:

$ dbus-monitor --session
"type='signal',interface='org.freedesktop.PowerManagement'"
signal sender=org.freedesktop.DBus -> dest=:1.242 serial=2
path=/org/freedesktop/DBus; interface=org.freedesktop.DBus;
member=NameAcquired
   string ":1.242"

Disconnecting the power and reconnecting it doesn't give any output in
the dbus-monitor
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQEcBAEBCAAGBQJKEI2SAAoJEIltSrFpUGte6/AIAIOzzfb1jDE/f/WmujKpMc8A
zcmOYBGsBmT/bRoemd9YaEhxpf4BTDz4DRgg2e3lzVRwvKioIMhgHBbotXPqEOea
K0K65cP11SJFjlm6WtXuFVyNBTQWXhiwf2jN3lX0/HDF3CzVhH+2AeVb85zs8SMR
pBv2MwJaxaJelSnb1zaero7i8TWb3nXSawbdhIcrKFFUk3eoZNl1su/SnnKjYzlB
eB5ojC3RxgsUfXGCZVSdsxmrbyf5qEHyZhOUizdwx3PmMAt3g8qLuPbkGXJJ5wZq
Hiapzo/eSKA6aPLrMjp+QPSM82PWX5bR65hJgnWY/dC8lS49zb9EVC3sU1klUj4=
=w36l
-----END PGP SIGNATURE-----

[Scott Howard (showard314)]

@Nick: Thanks for the response, it is really helpful. Please try the following:

$ lshal -m > lshal.log.txt

and attach lshal.log.txt to the bug report. This may be a problem with HAL/pm-utils.

Since dbus-monitor could not determine that the AC power was unplugged/plugged in, I added pm-utils to the bug report.

[Scott Howard (showard314)]

I'm sorry, I should be more specific:

Please try the following steps:

1) the following command into terminal: "lshal -m > lshal.log.txt"
2) unplug then plug in the AC adapter
3) attach lshal.log.txt to the bug report. This may be a problem with HAL/pm-utils.

[Nick B. (futurepilot)]

Here we go.

[Scott Howard (showard314)]

Nick, thank you for taking the time to report this bug and helping to make Ubuntu better. I've found that this problem is in hal, and that there are many other bugs describing this issue. I'm consolidating them all, so feel free to see bug 213128 and add any additional information if you can or if there is a request.