After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 554060 - gnome-power-manager does not update all information after suspend
gnome-power-manager does not update all information after suspend
Status: RESOLVED NOTGNOME
Product: gnome-power-manager
Classification: Deprecated
Component: general
2.24.x
Other All
: Normal major
: ---
Assigned To: GNOME Power Manager Maintainer(s)
GNOME Power Manager Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2008-09-27 11:02 UTC by vincenzo_ml
Modified: 2012-03-23 09:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description vincenzo_ml 2008-09-27 11:02:12 UTC 
Please describe the problem:
This bug has been reported in the ubuntu bug tracker at

https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/274727

If the battery of my notebook charges or discharges it is shown in the icon-bar (don't know how its called) and updates recently. If I suspend my system to RAM and resume it after a while, the icon and the tooltip is not updated anymore. The popup-menu and the battery informations show me the right information, but the power history gives me wrong information.

Steps to reproduce:
1. discharge the battery to a certain level
2. plug in ac adapter to charge battery
3. suspend to RAM while charging
4. wait until battery is charged and resume




Actual results:
The battery applet does not function well, and the system is not hibernated on battery critical even tough configured to do so.

Expected results:
The system should continue working as before hibernation.

Does this happen every time?
Yes

Other information:
Comment 1 James Westby 2008-09-30 10:14:50 UTC 
Hi,

I believe this bug can be closed.

The Ubuntu bug was caused when a patch was applied both
upstream and the Ubuntu patch wasn't removed. It applied
with fuzz, but to the wrong bit of code, and so the wrong
code was compiled. The patch has been dropped and things
are working much better.

Thanks,

James