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 313070 - Power source doesn't update when changed on suspend
Power source doesn't update when changed on suspend
Status: RESOLVED DUPLICATE of bug 163013
Product: gnome-applets
Classification: Other
Component: battery
unspecified
Other All
: Normal normal
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-08-10 08:39 UTC by David Strauss
Modified: 2005-08-10 13:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.1/2.2



Description David Strauss 2005-08-10 08:39:18 UTC
Please describe the problem:
Changing from battery to AC when the OS is running isn't a problem, but if I
suspend, pull the AC power, and resume, the system still thinks I'm running on
AC. Plugging in AC and pulling it again corrects the status back to battery. If
I suspend on battery and resume, it also has the correct status.

Steps to reproduce:
1. Boot on AC power.
2. Suspend.
3. Pull AC power.
4. Resume.


Actual results:
The battery indicator thinks it's still on AC power. Naturally, "time to charge
completion" just continues to increase.

Expected results:
The system should detect that it's on battery power when it resumes.

Does this happen every time?
Yes.

Other information:
Since I'm not familiar with Gnome, I'm not sure if this bug runs much deeper
into the power source detection. I assume it does (even though I hope it
doesn't), but I'm just submitting the obvious cosmetic effect.
Comment 1 Allison Karlitskaya (desrt) 2005-08-10 13:15:43 UTC
Hi.  This is a longtime known problem with laptops that have buggy ACPI
implementations.  The battery status applet in GNOME 2.12 contains a work-around
in the ACPI code.

In addition, the new applet uses the HAL (hardware abstraction layer) backend by
default, which also has a workaround for buggy ACPI implementations.

This should work for you when you upgrade to 2.12.0.



*** This bug has been marked as a duplicate of 163013 ***