Bug 642309 - [abrt] gnome-color-manager-2.30.2-1.fc13: usb_destroy_configuration: Process /usr/bin/gcm-prefs was killed by signal 11 (SIGSEGV)
Summary: [abrt] gnome-color-manager-2.30.2-1.fc13: usb_destroy_configuration: Process ...
Keywords:
Status: CLOSED DUPLICATE of bug 615183
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-color-manager
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:8aad08ba64e49f4bc83052d7782...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-12 14:48 UTC by Franck WIATROWSKI
Modified: 2010-11-09 16:08 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-09 16:08:49 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (40.38 KB, text/plain)
2010-10-12 14:48 UTC, Franck WIATROWSKI 		no flags Details
View All

Description Franck WIATROWSKI 2010-10-12 14:48:29 UTC 
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: gcm-prefs
component: gnome-color-manager
crash_function: usb_destroy_configuration
executable: /usr/bin/gcm-prefs
kernel: 2.6.34.7-56.fc13.i686.PAE
package: gnome-color-manager-2.30.2-1.fc13
rating: 3
reason: Process /usr/bin/gcm-prefs was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1286892139
uid: 500

comment
-----
i think the problem concern the integrated usb webcam "isight" on macbook, when isight work 
gcm-prefs don't crash and when isight not detected (randomly on reboot) gcm-prefs crash

How to reproduce
-----
1.open gcm-prefs on a macbook 
2.crash
3.
Comment 1 Franck WIATROWSKI 2010-10-12 14:48:33 UTC 
Created attachment 452977 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 16:08:49 UTC 

*** This bug has been marked as a duplicate of bug 615183 ***
Comment 3 Karel Klíč 2010-11-09 16:08:49 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #615183.

Sorry for the inconvenience.
Note You need to log in before you can comment on or make changes to this bug.