Bug 682457

Summary: [abrt] control-center-1:2.91.6-10.fc16: __libc_message: Process /usr/bin/gnome-control-center was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Sander D <sander.dijkhuis>
Component: gnome-color-managerAssignee: Richard Hughes <rhughes>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: control-center-maint, rhughes, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:24b216523ec3fbfa5b625c1235919c33eb637e80
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-26 10:23: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 Sander D 2011-03-05 17:47:49 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 34651 bytes
cmdline: gnome-control-center region
comment: This seems to happen only when "Noname - HP Webcam [2 MP Macro]" has not been shown in the Devices section yet, which takes a few seconds. When it is shown, clicking All Settings does not cause a crash.
component: control-center
Attached file: coredump, 72474624 bytes
crash_function: __libc_message
executable: /usr/bin/gnome-control-center
kernel: 2.6.38-0.rc6.git0.1.fc16.x86_64
package: control-center-1:2.91.6-10.fc16
rating: 4
reason: Process /usr/bin/gnome-control-center was killed by signal 6 (SIGABRT)
release: Fedora release 16 (Rawhide)
time: 1299346822
uid: 500

How to reproduce
-----
1. In GNOME Shell, open the top-right status menu.
2. Click System Settings.
3. Click Color.
4. Click All Settings.
Comment 1 Sander D 2011-03-05 17:47:52 UTC 
Created attachment 482462 [details]
File: backtrace
Comment 2 Richard Hughes 2011-04-26 10:23:05 UTC 

*** This bug has been marked as a duplicate of bug 684542 ***