Description of problem:
When I disconnect my laptop from wall power things do not update to indicate that I am now running on battery.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Unplug MSI MegaBook S271 from wall
2. Notice power management not detecting the event
The laptop I have actually comes in two flavors. There is one with PATA and one with SATA. I have the latest BIOS installed for the PATA version. That BIOS version is 1.22
capacity state: ok
charging state: charged
present rate: unknown
remaining capacity: unknown
present voltage: 10000 mV
Created attachment 363753 [details]
Created attachment 363754 [details]
Created attachment 363755 [details]
reassigning to acpid
Steven M. Parrish - KDE Triage Master
- PackageKit Triager
Fedora Bugzappers volunteer triage team
I'm not quite sure this is a userspace problem. I upgraded to F12 on the laptop and while it was installing I was eager to know if my problem was fixed so I checked /proc/acpi/battery/BAT1/state after unplugging from the wall and saw reasonable values instead of unknown. After I boot from the hard disk things go back to unknown again. I even tried from single user mode.
I took a look at the kernel cmdline for the installer kernel and didn't see anything special being passed that I could try on my regular kernel to get things fixed.
Updating version to reflect my last post about it being a problem on F12 as well.
Stupid question: is the acpid running> Test it:
sudo service acpid status
Please, try to start acpi_listen in terminal. Then plug out and plug in AC adapter from/to socket. If it works correctly you should see written events in the terminal. Let me know about your findings.
I see the status changed to NEEDINFO, but I'm unclear on what further information I should provide.
Ah, sorry, I don't know why but my comment #7 was checked private. Perhaps you can read it now.
acpid was running when I checked.
After I started acpi_listen I unplugged the laptop and plugged it back in. No events were displayed. Just to make sure something acpi related was happening I pressed the power button and "button/power PWRF 00000080 00000001" showed up. The correct dialog popped up asking me about shutting down or rebooting.
I didn't see any other events when running acpi_listen.
Thanks for the test. There are no plug/unplug events to handle. Therefore acpid has nothing to do. I suppose this is probably kernel issue so I'm going to switch the component.
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12. 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 '12'.
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 12'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 12 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:
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.