After resume from suspend, power-indicator is unaware of battery changes

[Chris]

When resuming from suspend, power-indicator seems to be frozen. Remaining time is not updated, even if I (un)plug AC.

Only way to restore normal operation without reboot is to start gnome-power-manager... the indicator becomes responsive again.

Probably related to https://bugs.launchpad.net/indicator-power/+bug/983928 and/or https://bugs.launchpad.net/indicator-power/+bug/994745

[Chris (cmavr8)]

FYI this is still happening on a fully updated 12.04 installation. It was also a problem in 11.10 and probably earlier.

gnome-power-manager version: 3.4.0-0ubuntu1
indicator-power version: 2.0-0ubuntu1
upower version: 0.9.15-3git1

[Sebastien Bacher (seb128)]

could you run "upower -d" wait some minutes and run it again and add the logs to the bug? is the percentage updated?

[Chris (cmavr8)]

Thanks for replying Sebastien,
upower -d seems to "awaken" the indicator!

Great discovery, I can invoke the command in a script inside /usr/lib/pm-utils/sleep.d/ so we may have a workaraound!

Anyway, please find attached the upower -d results, but I think they don't matter since indicator is also working after the first upower -d.

[Sebastien Bacher (seb128)]

Is that still an issue in the current version?

[Charles Kerr (charlesk)]

I'm not able to reproduce this in 13.10.

There does appear to be a minor bug in UPower in that we're not getting a resume-from-suspend signal from it; however, I am seeing it update its devices right after we resume from suspend anyway. So even without the resume signal, the outcome is that I'm still seeing the devices get fresh information after we resume.

I'm marking this ticket as incomplete. Please reopen this ticket with more information if the problem persists for you.

[Clay B. (cbaenziger)]

I can confirm I still see this (or particularly do not see the state update after resume from sleep) on an Acer C720p in 16.04 as well; I had previously seen it in 15.10 on this machine but have seen it work on a modified 14.04 sometime ago.

The upower -d suggestion is not working for me (and running upower --monitor has no state changes when plugging/unplugging), nor is running gnome-power-statistics (it eventually fails with the following).

Failure of gnome-power-statistics:
(gnome-power-statistics:17074): libupower-glib-WARNING **: up_client_get_devices failed: Timeout was reached

If I run upower -e to enumerate power sources I end up with a segmentation fault. I'll post the strace output as an attachment.

[Clay B. (cbaenziger)]

User visible upower -e output:
cwb@vagabond:~/$ upower -e
(upower:17782): libupower-glib-WARNING **: up_client_get_devices failed: Timeout was reached
Segmentation fault (core dumped)

[Clay B. (cbaenziger)]

Also under 16.04 I see the acpi(1) command and /sys paths work to get the status fine:
cwb@vagabond:~/$ cat /sys/class/power_supply/BAT0/status
Full
cwb@vagabond:~/$ acpi
Battery 0: Full, 100%

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Eric Park (ericswpark)]

I'm having this issue - however unplugging the charging cable immediately updates the correct percentage. I'm running Ubuntu 16.04 LTS and I've put in some Unity tweaks, but this shouldn't matter.