Bug 682457 - [abrt] control-center-1:2.91.6-10.fc16: __libc_message: Process /usr/bin/gnome-control-center was killed by signal 6 (SIGABRT)
Summary: [abrt] control-center-1:2.91.6-10.fc16: __libc_message: Process /usr/bin/gnom...
Keywords:
Status: CLOSED DUPLICATE of bug 684542
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-color-manager
Version: rawhide
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:24b216523ec3fbfa5b625c12359...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-05 17:47 UTC by Sander D
Modified: 2011-04-26 10:23 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-26 10:23:05 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (33.84 KB, text/plain)
2011-03-05 17:47 UTC, Sander D
no flags Details

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 ***


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