abrt 1.0.9 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: /usr/libexec/upowerd comment: See similar bug reported against F-12 (bug#578467) component: upower executable: /usr/libexec/upowerd global_uuid: a8a81fbc5f59c4b1eec84b7e309ae44049812d0a kernel: 2.6.33.1-19.fc13.x86_64 package: upower-0.9.2-1.fc13 rating: 4 reason: Process /usr/libexec/upowerd was killed by signal 11 (SIGSEGV) release: Fedora release 13 (Goddard) How to reproduce ----- 1. Boot F-13 on a MacbookPro 5,5 OR 2. Run /usr/libexec/devkit-power-daemon by hand
Created attachment 405320 [details] File: backtrace
I think this is the same as a previously reported issue against F-12, only the package ownership of the file /usr/libexec/devkit-power-daemon has changed. See bug#578467.
Okay, I think I see the bug (in libusb). Could you please start a gdb session ("sudo gdb /usr/libexec/uppower", then input "r --verbose") into the debugger and press enter. Then, when it crashes, can you type "up" or "down" as required until the line above the prompt says something like: #3 0x00007fa8f3521256 in usb_destroy_configuration ( dev=<value optimized out>) at descriptors.c:429 Then in the prompt can you type "p cf->interface" If that value is -1, then I know where the bug is. Otherwise, it's back to the drawing board. Thanks. Richard.
Created attachment 405872 [details] upower gdb output.txt (In reply to comment #3) > Okay, I think I see the bug (in libusb). Could you please start a gdb session > ("sudo gdb /usr/libexec/uppower", then input "r --verbose") into the debugger > and press enter. > > Then, when it crashes, can you type "up" or "down" as required until the line > above the prompt says something like: > > #3 0x00007fa8f3521256 in usb_destroy_configuration ( > dev=<value optimized out>) at descriptors.c:429 > > Then in the prompt can you type "p cf->interface" > > If that value is -1, then I know where the bug is. Otherwise, it's back to the > drawing board. Thanks. See attached gdb output for full details ... #4 0x00000034046021c3 in usb_destroy_configuration (dev=<value optimized out>) at descriptors.c:414 414 free(as->extra); (gdb) p cf->interface $1 = (struct usb_interface *) 0x657bb0
@Richard - any progress on this one? If it helps at all it seems to crash on many other MacBook models as well and it seems to happen a lot more often when booting on battery than when booting on AC...
Alex, it's a libusb problem we're debugging now.
Great - any help I can give?
@Richard - there's an upstream bug report in libusb which was filed by Martin Pitt which may give you some more info if you're still trying to debug this - http://www.libusb.org/ticket/11 Unfortunately since libusb-0.1 is unmaintained now I don't expect this to get fixed by upstream - perhaps would be worth porting upower to use libusb-1.0 instead to remove the reliance on this old, buggy library...
commit 2b826a316954eec9951b9bf98b853560cfd70828 Author: Richard Hughes <richard> Date: Tue May 18 09:37:17 2010 +0100 Port UPower to libusb1 to avoid crappy unfixable crashes
Could you try rebuilding the upower src.rpm available here please, and telling me if it fixes the problem: http://people.freedesktop.org/~hughsient/fedora/13/SRPMS/ Thanks.
*** Bug 587206 has been marked as a duplicate of this bug. ***
Scratch build submitted to koji (download x86_64 and i686 packages from http://koji.fedoraproject.org/koji/taskinfo?taskID=2194039). I'm running this upowerd and will see how it goes after a few days of use.
Seems to work again on my MacBook Pro 5,5 13" with RPM from @12. Two times I put my MacBook in its cover with the lid closed assuming it would suspend (auch :o)
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13'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 13 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 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.