Bug 689368 - [abrt] control-center-1:2.91.91-1.fc15: g_type_check_instance_cast: Process /usr/bin/gnome-control-center was killed by signal 11 (SIGSEGV)
Summary: [abrt] control-center-1:2.91.91-1.fc15: g_type_check_instance_cast: Process /...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: control-center
Version: 15
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Control Center Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:4e05de46c1e4566bd126ad0c692...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-21 08:52 UTC by toulzemaurice
Modified: 2011-04-29 14:54 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-29 14:54:33 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (42.69 KB, text/plain)
2011-03-21 08:53 UTC, toulzemaurice 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description toulzemaurice 2011-03-21 08:52:58 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 43719 bytes
cmdline: gnome-control-center --overview
component: control-center
Attached file: coredump, 94494720 bytes
crash_function: g_type_check_instance_cast
executable: /usr/bin/gnome-control-center
kernel: 2.6.38-1.fc15.x86_64
package: control-center-1:2.91.91-1.fc15
rating: 4
reason: Process /usr/bin/gnome-control-center was killed by signal 11 (SIGSEGV)
release: Fedora release 15 (Lovelock)
time: 1300696827
uid: 500

How to reproduce
-----
1.j'ai mis en adobe 1998,puis j'ai confirmer que je voulais que ce soit mon profil par défault.
2.j'ai donc mis mon mot de passe et bug.
3.
Comment 1 toulzemaurice 2011-03-21 08:53:02 UTC 
Created attachment 486566 [details]
File: backtrace
Comment 2 Matthias Clasen 2011-04-29 14:54:33 UTC 
I think this is fixed in control-center 3.0.x, with some added filtering to avoid system accounts ever entering the user list.
Note You need to log in before you can comment on or make changes to this bug.