Red Hat Bugzilla – Bug 832497
powertop crashes on launch due to /sys differences for BAT0
Last modified: 2012-07-14 18:00:15 EDT
Description of problem:
powertop crashes with the following message:
terminate called after throwing an instance of 'std::ios_base::failure'
what(): basic_filebuf::underflow error reading the file
Aborted (core dumped)
open("/sys/class/power_supply/BAT0/power_now", O_RDONLY) = -1 ENOENT (No such file or directory) open("/sys/class/power_supply/BAT0/energy_now", O_RDONLY) = -1 ENOENT (No such file or directory)
right before the crash, neither of these exist in /sys on my system, but instead there are charge_now, current_now, voltage_now.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run powertop on a laptop
powertop crashes and dumps core
I have the same problem but on my laptop powertop works fine when it's on AC power. So I think powertop crashes only when laptop is on battery power. I'm using the same version of powertop but my kernel is kernel-3.4.2-4.fc17.x86_64.
Could you try the following experimental build?
Please let me know whether it helps.
So, I have tried it on my laptop and it works fine. Calibracion has also ended successfully and powertop is running without errors. thank you
*** Bug 835682 has been marked as a duplicate of this bug. ***
Thanks for testing, pushing the update.
powertop-2.0-3.fc17 has been submitted as an update for Fedora 17.
powertop-2.0-3.fc16 has been submitted as an update for Fedora 16.
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing powertop-2.0-3.fc17'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
powertop-2.0-3.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
powertop-2.0-3.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.