Bug 919517

Summary: [abrt] control-center-3.4.3-1.fc17: magazine_chain_pop_head: Process /usr/bin/gnome-control-center was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: snog_
Component: control-centerAssignee: Control Center Maintainer <control-center-maint>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: control-center-maint, mkasik, ofourdan, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:9316a2688466af688f5f638a09d8b6e84b353f34
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-31 22:33:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: build_ids
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: smolt_data
none
File: var_log_messages none

Description snog_ 2013-03-08 17:36:45 UTC 
Version-Release number of selected component:
control-center-3.4.3-1.fc17

Additional info:
backtrace_rating: 4
cmdline:        gnome-control-center --overview
crash_function: magazine_chain_pop_head
executable:     /usr/bin/gnome-control-center
kernel:         3.7.9-104.fc17.i686
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 magazine_chain_pop_head at gslice.c:532
 #1 thread_memory_magazine1_alloc at gslice.c:835
 #2 g_slice_alloc at gslice.c:994
 #3 g_variant_iter_new at gvariant.c:2878
 #4 g_settings_schema_get_value at gsettingsschema.c:642
 #5 g_settings_schema_key_init at gsettingsschema.c:751
 #6 g_settings_set_enum at gsettings.c:1182
 #7 style_changed_cb at cc-background-panel.c:785
 #8 g_cclosure_marshal_VOID__VOIDv at gmarshal.c:115
 #9 _g_closure_invoke_va at gclosure.c:840

Potential duplicate: bug 740701
Comment 1 snog_ 2013-03-08 17:37:11 UTC 
Created attachment 707127 [details]
File: backtrace
Comment 2 snog_ 2013-03-08 17:37:26 UTC 
Created attachment 707128 [details]
File: build_ids
Comment 3 snog_ 2013-03-08 17:37:46 UTC 
Created attachment 707129 [details]
File: cgroup
Comment 4 snog_ 2013-03-08 17:38:01 UTC 
Created attachment 707130 [details]
File: core_backtrace
Comment 5 snog_ 2013-03-08 17:38:08 UTC 
Created attachment 707131 [details]
File: dso_list
Comment 6 snog_ 2013-03-08 17:38:15 UTC 
Created attachment 707132 [details]
File: environ
Comment 7 snog_ 2013-03-08 17:38:21 UTC 
Created attachment 707133 [details]
File: limits
Comment 8 snog_ 2013-03-08 17:38:34 UTC 
Created attachment 707134 [details]
File: maps
Comment 9 snog_ 2013-03-08 17:38:40 UTC 
Created attachment 707135 [details]
File: open_fds
Comment 10 snog_ 2013-03-08 17:38:43 UTC 
Created attachment 707136 [details]
File: proc_pid_status
Comment 11 snog_ 2013-03-08 17:38:49 UTC 
Created attachment 707137 [details]
File: smolt_data
Comment 12 snog_ 2013-03-08 17:38:54 UTC 
Created attachment 707138 [details]
File: var_log_messages
Comment 13 Fedora End Of Life 2013-07-03 21:27:44 UTC 
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 14 Fedora End Of Life 2013-07-31 22:33:30 UTC 
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.