Bug 520242 - Gnome-power-manager applet doesn't detect when i unplug the a/c power supply
Summary: Gnome-power-manager applet doesn't detect when i unplug the a/c power supply
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-power-manager
Version: 11
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2009-08-29 16:22 UTC by Lorenzo
Modified: 2010-06-28 14:22 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-06-28 14:22:46 UTC

Attachments (Terms of Use)
not detecting power changes. (12.74 KB, image/png)
2009-10-31 18:51 UTC, Peter Robinson
no flags Details

Description Lorenzo 2009-08-29 16:22:58 UTC
Description of problem:
Gnome-power-manager applet sometimes doesn't notice when I unplug the A/C supply

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Wait for full battery charging
2.Unplug the A/C Power Supply
Actual results:
Gnome-power-manager applet doesn't notice that i've unplugged a/c power supply and remains like it's still plugged

Expected results:
Gnome-power-manager applet notices that i've unplugged power supply and starts informing me about battery duration

Additional info:

Comment 1 Andrew Walrond 2009-09-23 09:51:31 UTC
Same problem here on my Dell Laptop. Same version of gnome-power-manager.

I believe this was working fine until an update broke it.

Only one thing to add:

If I unplug the power, it doesn't detect the 'battery discharging' condition. If I plug the power back in, it suddenly says gives me the 'battery discharging' popup, before realising the power is back on again a few seconds later and changing to 'charging' mode.

Comment 2 Peter Robinson 2009-10-31 18:51:05 UTC
Created attachment 366963 [details]
not detecting power changes.

I'm seeing the same issue on my Dell Latitude D630. It doesn't seem to always detect the power state changes or takes ages to do so. Whether that be add/remove power or add/remove batteries (I have two). It also seems to occasionally not detect any status as the attached screen shot shows.

Comment 3 Bug Zapper 2010-04-28 10:03:54 UTC
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 4 Bug Zapper 2010-06-28 14:22:46 UTC
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.