Bug 694366

Summary: [abrt] xsane-gimp-0.998-1.fc14: __libc_message: Process /usr/lib64/gimp/2.0/plug-ins/xsane was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Moritz Baumann <baumanmo>
Component: libusbAssignee: Jan Vcelak <jvcelak>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: jmoskovc, jnovy, jvcelak, nphilipp, rhbugs, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:b55ba69f49e503bb431a74d2c9f1a4b740958901
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-24 14:59:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Moritz Baumann 2011-04-07 06:33:31 UTC 
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.
Comment 1 Moritz Baumann 2011-04-07 06:33:34 UTC 
Created attachment 490480 [details]
File: backtrace
Comment 2 Nils Philippsen 2011-04-07 09:18:33 UTC 
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?
Comment 3 Jan Vcelak 2011-05-24 13:38:53 UTC 
Hi Moritz,

I'm unable to reproduce the bug. Can you? Which USB devices did you have connected to your system?

Jan
Comment 4 Moritz Baumann 2011-05-24 14:35:54 UTC 
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
Comment 5 Jan Vcelak 2011-05-24 14:59:05 UTC 
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.