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 581598 - low battery event triggered even when connected to ac
low battery event triggered even when connected to ac
Status: RESOLVED OBSOLETE
Product: gnome-power-manager
Classification: Deprecated
Component: gnome-power-manager
2.26.x
Other All
: Normal normal
: ---
Assigned To: GNOME Power Manager Maintainer(s)
GNOME Power Manager Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2009-05-06 14:30 UTC by Tamási János
Modified: 2012-03-23 09:50 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description Tamási János 2009-05-06 14:30:08 UTC
Please describe the problem:
Gnome power manager does not respect ac connected state, and always trigger low battery event, if battery level is cirtical. 
If you wake up from sleep, and your low battery policy is to go sleep if battery low, gnome power manager always sleeps the machine after wake up while battery level is critical.

Steps to reproduce:
1. left battery to discharge
2. connect to ac when battery level is critical



Actual results:
low battery event repeatedly triggered while charge level below critical

Expected results:
do not trigger low battery event if conneceted to ac

Does this happen every time?
yes

Other information:
Comment 1 Pascal Terjan 2009-05-11 11:54:36 UTC
Confirmed by a Mandriva user with gnome-power-manager 2.26.1 and devicekit-power 006
Comment 2 Erwan Velu 2009-05-11 11:55:21 UTC
I've been facing that bug in the following use case: 

Plug battery to laptop
Plug AC to laptop
Power on laptop
Battery is charging
When battery is charged, remove it
Plug a discharged battery (0%) to charge it
System is powered off.

That's a pretty annoying bug when you want to charge many batteries
Comment 3 Piotr Iwaniuk 2009-07-18 20:19:08 UTC
This bug seems to be present in gnome-power-manager 2.26.2. It happened to me when I did following steps:
1. discharge the battery completely,
2. connect AC adapter,
3. boot Linux and login to Gnome.