The notification icon is not updated

Bug #35858 reported by Julien Olivier
20
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-power
Fix Released
Medium
gnome-power-manager (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

When I plug / unplug my laptop's power cord, gnome-volume-manager's notification icon is not updated (it remains in the state it was when I booted). However, the tooltip message is always correct (running on battery / running on AC power).

Revision history for this message
Julien Olivier (julo) wrote :

Sorry for the typos... I obviously meant gnome-power-manager.

Revision history for this message
Andrew Jorgensen (ajorg) wrote :

I'm seeing very similar issues. If I unplug the power I see a change. Likewise if I plug in. But while it's charging it never updates the icon to indicate what the charge percentage is.

Revision history for this message
Richard Hughes (richard-hughes) wrote :

Can you please run lshal -m and see what events you get when charging and discharging. Thanks.

Revision history for this message
Julien Olivier (julo) wrote :

Here's what I get when I un-plug my laptop:

acpi_AC property ac_adapter.present = false
acpi_CMB1 property battery.remaining_time = 3758 (0xeae) (new)
acpi_CMB1 property battery.charge_level.rate = 41374800 (0x2775450)
acpi_CMB1 property battery.voltage.current = 12308 (0x3014)
acpi_CMB1 property battery.reporting.rate = 3831 (0xef7)

And here's what I get when I re-plug it:

acpi_AC property ac_adapter.present = true
acpi_CMB1 property battery.remaining_time removed
acpi_CMB1 property battery.charge_level.rate = 0 (0x0)
acpi_CMB1 property battery.voltage.current = 12166 (0x2f86)
acpi_CMB1 property battery.reporting.rate = 0 (0x0)

But in all cases, the notification icon shows the battery icon.

Revision history for this message
Richard Hughes (richard-hughes) wrote :

This is a problem with your hardware; on my system ACPI generates on unplug:

acpi_ADP1 property ac_adapter.present = false
acpi_BAT1 property battery.remaining_time = 7237 (0x1c45) (new)
acpi_BAT1 property battery.charge_level.rate = 20714 (0x50ea)
acpi_BAT1 property battery.reporting.rate = 20714 (0x50ea)
acpi_BAT1 property battery.rechargeable.is_discharging = true

You see how the is_discharging value is present in my output but not yours? In g-p-m we have to go with what the battery says, rather than the ac_adapter so we can support the different types of multibattery laptops.

Can you do a BIOS update, or maybe fix your DSDT? What laptop do you have?

Revision history for this message
Julien Olivier (julo) wrote :

My laptop is a Fujitsu-Siemens Lifebook S6120. I have no clue how to fix the DSDT or update the BIOS. More over, it would be better to find a solution so that this laptop works out of the box, IMHO, because very few people "fix their DSDT" or "update their BIOS" :)

Revision history for this message
Richard Hughes (richard-hughes) wrote :

Please see http://bugzilla.gnome.org/show_bug.cgi?id=334212 where we are working on a fix.

Revision history for this message
Julien Olivier (julo) wrote :

OK, thanks for the link.

Changed in gnome-power-manager:
status: Unconfirmed → Confirmed
Revision history for this message
Andrew Jorgensen (ajorg) wrote :

I still see this problem.

Revision history for this message
Richard Hughes (richard-hughes) wrote :

Andrew, what does "lshal | grep battery" print when on battery power and AC power?

Revision history for this message
Julien Olivier (julo) wrote :
Download full text (4.1 KiB)

You asked Andrew, but I'll anwser anyway as I'm having the same problem.

Here's what I get when running on AC power:

julien@lifebook ~ $ lshal | grep battery
  battery.charge_level.percentage = 100 (0x64) (int)
  battery.charge_level.rate = 0 (0x0) (int)
  battery.charge_level.last_full = 43200000 (0x2932e00) (int)
  battery.charge_level.current = 43200000 (0x2932e00) (int)
  battery.voltage.current = 12424 (0x3088) (int)
  battery.reporting.rate = 0 (0x0) (int)
  battery.reporting.current = 4000 (0xfa0) (int)
  battery.charge_level.capacity_state = 'ok' (string)
  battery.rechargeable.is_discharging = true (bool)
  battery.rechargeable.is_charging = false (bool)
  battery.is_rechargeable = true (bool)
  battery.charge_level.unit = 'mWh' (string)
  battery.charge_level.granularity_2 = 10800 (0x2a30) (int)
  battery.charge_level.granularity_1 = 10800 (0x2a30) (int)
  battery.charge_level.low = 0 (0x0) (int)
  battery.charge_level.warning = 0 (0x0) (int)
  battery.charge_level.design = 43200000 (0x2932e00) (int)
  battery.voltage.design = 10800 (0x2a30) (int)
  battery.voltage.unit = 'mV' (string)
  battery.reporting.granularity_2 = 1 (0x1) (int)
  battery.reporting.granularity_1 = 1 (0x1) (int)
  battery.reporting.low = 0 (0x0) (int)
  battery.reporting.warning = 0 (0x0) (int)
  battery.reporting.design = 4000 (0xfa0) (int)
  battery.reporting.last_full = 4000 (0xfa0) (int)
  battery.reporting.unit = 'mAh' (string)
  battery.technology = 'LION' (string)
  battery.serial = '1' (string)
  battery.model = 'CP147685-XX' (string)
  battery.vendor = 'Fujitsu' (string)
  battery.present = true (bool)
  info.capabilities = {'battery'} (string list)
  info.category = 'battery' (string)
  battery.type = 'primary' (string)
  linux.acpi_path = '/proc/acpi/battery/CMB1' (string)
  battery.present = false (bool)
  info.capabilities = {'battery'} (string list)
  info.category = 'battery' (string)
  battery.type = 'primary' (string)
  linux.acpi_path = '/proc/acpi/battery/CMB2' (string)

And here's what I get just after un-plugging it:

julien@lifebook ~ $ lshal | grep battery
  battery.remaining_time = 3755 (0xeab) (int)
  battery.charge_level.percentage = 100 (0x64) (int)
  battery.charge_level.rate = 41407200 (0x277d2e0) (int)
  battery.charge_level.last_full = 43200000 (0x2932e00) (int)
  battery.charge_level.current = 43200000 (0x2932e00) (int)
  battery.voltage.current = 12334 (0x302e) (int)
  battery.reporting.rate = 3834 (0xefa) (int)
  battery.reporting.current = 4000 (0xfa0) (int)
  battery.charge_level.capacity_state = 'ok' (string)
  battery.rechargeable.is_discharging = true (bool)
  battery.rechargeable.is_charging = false (bool)
  battery.is_rechargeable = true (bool)
  battery.charge_level.unit = 'mWh' (string)
  battery.charge_level.granularity_2 = 10800 (0x2a30) (int)
  battery.charge_level.granularity_1 = 10800 (0x2a30) (int)
  battery.charge_level.low = 0 (0x0) (int)
  battery.charge_level.warning = 0 (0x0) (int)
  battery.charge_level.design = 43200000 (0x2932e00) (int)
  battery.volt...

Read more...

Revision history for this message
Andrew Jorgensen (ajorg) wrote :

Since Julien already posted his logs I thought I'd just post the diff between my two logs. Looks like nothing interesting to me. Or perhaps I misunderstood the question.

1,2c1,2
< battery.remaining_time = 4643 (0x1223) (int)
< battery.charge_level.percentage = 59 (0x3b) (int)
---
> battery.remaining_time = 4295 (0x10c7) (int)
> battery.charge_level.percentage = 58 (0x3a) (int)
5,6c5,6
< battery.charge_level.current = 25054380 (0x17e4cac) (int)
< battery.voltage.current = 11320 (0x2c38) (int)
---
> battery.charge_level.current = 24719890 (0x1793212) (int)
> battery.voltage.current = 11286 (0x2c16) (int)
8c8
< battery.reporting.current = 2322 (0x912) (int)
---
> battery.reporting.current = 2291 (0x8f3) (int)

Revision history for this message
Aaron Isotton (aisotton) wrote :

I have the same or a very similar problem. Whenever gnome-power-manager starts up, it displays the correct status, but then it just stays there and never updates (not in case of plug/unplug, neither in case of charging/discharging).

If I do a 'killall gnome-power-manager; gnome-power-manager' the status is updated (and stays there). To me this looks as if gnome-power-manager were hanging somewhere.

Revision history for this message
Aaron Isotton (aisotton) wrote :

Ah, I forgot to say that it worked on dapper. It stopped working on edgy. I am currently running gnome-power-manager 2.14.3-0ubuntu11.

Off-Topic: this malone bug tracker is the worst piece of crap I've ever used. Even Bugzilla is better, and when I compare it to the wonderful greatness of the Debian BTS I just feel sick. No need to register to report a bug! Automated version reporting! Searching which works! Oh Ubuntu.

Revision history for this message
Oliver Grawert (ogra) wrote :

its not supposed to work on edgy yet, g-p-m is waiting for a new hal with policy kit enabled. this bug is only valid for dapper, if it doesnt work with g-p-m 2.15 in edgy once thats out, please file a new bug.

Revision history for this message
Paul Sladen (sladen) wrote :

Off-topic: Aaron. Malone now sucks less than it used it, the reason that is sucks less is because we (the users of Malone) keep telling the Launchpad developers how to improve each little part.

Pick each part that is broken for you, figure out how to improve it and file a (constructive) bug report at:

  https://launchpad.net/products/malone/+filebug

then hopefully it'll continue to get better for all of us to use.

Revision history for this message
Pichu0102 (pichu0102-deactivatedaccount) wrote :

The notification icon does not appear to update when plugged and unplugged here as well, on Dapper Drake. The icon does update once a notification bubble appears, however (such as "You are at critical battery level").

Changed in gnome-power:
status: Needs Info → Confirmed
Changed in gnome-power:
status: Confirmed → Fix Released
Revision history for this message
Daniel Holbach (dholbach) wrote :

Fixed upstream (looks like 2.17.x material).

Changed in gnome-power-manager:
status: Confirmed → Fix Committed
Revision history for this message
Sebastien Bacher (seb128) wrote :

new version available in 7.04, closing

Changed in gnome-power-manager:
status: Fix Committed → Fix Released
Changed in gnome-power:
importance: Unknown → Medium
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.