Bug 1043174

Summary: [abrt] mate-panel-1.6.1-4.fc19: gtk_widget_get_parent: Process /usr/bin/mate-panel was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: David Ford <dford>
Component: mate-panelAssignee: Dan Mashal <dan.mashal>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: dan.mashal, fedora, rdieter, stefano
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/b3461f6cc7eba1a2b45b6d39a8ef66cae8e54ad5
Whiteboard: abrt_hash:0504178ab7367663945899d207ca5907b7726ee0
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-15 14:34:46 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
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description David Ford 2013-12-14 16:17:12 UTC 
Version-Release number of selected component:
mate-panel-1.6.1-4.fc19

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        mate-panel
crash_function: gtk_widget_get_parent
executable:     /usr/bin/mate-panel
kernel:         3.11.10-200.fc19.i686.PAE
runlevel:       N 5
type:           CCpp
uid:            500

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 gtk_widget_get_parent at gtkwidget.c:6483
 #1 mate_panel_applet_get_panel_widget at applet.c:48
 #2 mate_panel_applet_locked_change_notify at applet.c:192
 #3 g_cclosure_marshal_VOID__STRINGv at gmarshal.c:1004
 #4 _g_closure_invoke_va at gclosure.c:840
 #7 g_settings_real_change_event at gsettings.c:288
 #8 ffi_call_SYSV at ../src/x86/sysv.S:65
 #9 ffi_call at ../src/x86/ffi.c:411
 #10 g_cclosure_marshal_generic_va at gclosure.c:1550
 #11 g_type_class_meta_marshalv at gclosure.c:997

Potential duplicate: bug 952338
Comment 1 David Ford 2013-12-14 16:17:17 UTC 
Created attachment 836726 [details]
File: backtrace
Comment 2 David Ford 2013-12-14 16:17:19 UTC 
Created attachment 836727 [details]
File: cgroup
Comment 3 David Ford 2013-12-14 16:17:22 UTC 
Created attachment 836728 [details]
File: core_backtrace
Comment 4 David Ford 2013-12-14 16:17:23 UTC 
Created attachment 836729 [details]
File: dso_list
Comment 5 David Ford 2013-12-14 16:17:25 UTC 
Created attachment 836730 [details]
File: environ
Comment 6 David Ford 2013-12-14 16:17:27 UTC 
Created attachment 836731 [details]
File: exploitable
Comment 7 David Ford 2013-12-14 16:17:29 UTC 
Created attachment 836732 [details]
File: limits
Comment 8 David Ford 2013-12-14 16:17:32 UTC 
Created attachment 836733 [details]
File: maps
Comment 9 David Ford 2013-12-14 16:17:34 UTC 
Created attachment 836734 [details]
File: open_fds
Comment 10 David Ford 2013-12-14 16:17:36 UTC 
Created attachment 836735 [details]
File: proc_pid_status
Comment 11 David Ford 2013-12-14 16:17:38 UTC 
Created attachment 836736 [details]
File: var_log_messages
Comment 12 Wolfgang Ulbrich 2013-12-29 09:16:26 UTC 
Can you describe a little more detailed what happend?
Did this issue occurs frequently ?
Comment 13 David Ford 2013-12-29 14:15:48 UTC 
Sorry no idea - abrt did this all on its own - I can't even remember what I was doing.

Just a one off - not a frequent problem
David
Comment 14 Wolfgang Ulbrich 2013-12-29 14:57:31 UTC 
Ok, thanks for info, i will leave the report a while open, feel free to report if the issue happens again.