Hide Forgot
abrt version: 1.1.17 architecture: x86_64 Attached file: backtrace, 15836 bytes cmdline: /usr/lib64/gimp/2.0/plug-ins/xsane -gimp 11 10 -query 0 component: xsane Attached file: coredump, 1568768 bytes crash_function: __libc_message executable: /usr/lib64/gimp/2.0/plug-ins/xsane kernel: 2.6.35.11-83.fc14.x86_64 package: xsane-gimp-0.998-1.fc14 rating: 4 reason: Process /usr/lib64/gimp/2.0/plug-ins/xsane was killed by signal 6 (SIGABRT) release: Fedora release 14 (Laughlin) time: 1302157552 uid: 500 How to reproduce ----- 1. opening gimp 2. 3.
Created attachment 490480 [details] File: backtrace
This crash happens beneath usb_find_devices() in libusb, changing component. The relevant calls are these: usb_find_devices() `- usb_free_dev(...) `- usb_destroy_configuration(...) `- free(...) [ _int_free(...) ) `- ... Unfortunately, abrt doesn't preserve the "*** glibc detected *** %s: %s: 0x%s ***\n" error message and I don't see how this can be reconstructed from the backtrace. I don't know how feasible implementing this in abrt would be. Jiří, what do you think?
Hi Moritz, I'm unable to reproduce the bug. Can you? Which USB devices did you have connected to your system? Jan
Hi Jan, sorry I upgraded all my F14-> F15 (thus being unable to reproduce this). I think it was on my MacBookPro5,3 with the internal isight camera attached via USB. But I did not press acquire image or anything. Best, Moritz
libusb was abandoned by upstream developers in 2007. In F15 there is a libusb compatibility layer which uses newer libusb1. More information can be found on http://libusb.org. I expect, that the problem is gone with the new library. I'm closing this bug report now. Anyway, thank you for your report.