abrt 1.0.8 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: /usr/libexec/devkit-power-daemon comment: Just boot F12+updates on my laptop. I noticed that it doesn't recognize my battery anymore. Closer inspection of /var/log/messages shows that devkit-power-daemon crashed during boot. component: DeviceKit-power executable: /usr/libexec/devkit-power-daemon kernel: 2.6.32.10-90.fc12.x86_64 package: DeviceKit-power-014-1.fc12 rating: 4 reason: Process /usr/libexec/devkit-power-daemon was killed by signal 11 (SIGSEGV) release: Fedora release 12 (Constantine) How to reproduce ----- 1. Just boot my F12+updates system 2. Inspect /var/log/messages and notice that devkit-power-daemon crashed 3. No longer have battery icon on desktop, I assume this is related
Created attachment 403729 [details] File: backtrace
Can you reproduce this? Thanks.
(In reply to comment #2) > Can you reproduce this? Thanks. I've noticed that my battery isn't recognized on just about every boot on this system. This is the first time I ran abrt-gui as root to report this failure. I suspect the two are linked, but not certain. Is there something specific you're looking for ... or just whether this is a frequently occurring problem?
(In reply to comment #3) > Is there something specific you're looking for Ideally a "devkit-power-daemon --verbose" log that shows the crash. I would be interested to know if f13 is also affected by the failure. Thanks.
Created attachment 403801 [details] /usr/libexec/devkit-power-daemon --verbose --debug-functions --debug-modules (In reply to comment #4) > (In reply to comment #3) > > Is there something specific you're looking for > > Ideally a "devkit-power-daemon --verbose" log that shows the crash. I would be > interested to know if f13 is also affected by the failure. Thanks. I'm not able to install F-13 at the moment due to bug#576681. I've attached the output from running "devkit-power-daemon --verbose --debug-functions --debug-modules"
Okay, that looks like a problem in libusb. I'll have a look later when I'm at my development machine.
(In reply to comment #6) > Okay, that looks like a problem in libusb. I'll have a look later when I'm at > my development machine. I've installed F-13-Beta and am able to reproduce this issue. See ABRT-filed bug#580570 against upower.
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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
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.