Bug 1045835

Summary: [abrt] mate-panel: g_slist_remove_all(): mate-panel killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Pavel Mlčoch <pavkamlc>
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, samtygier, stefano
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/7f5046866433ec0cff5eb3d5b9b44c61cdd2828e
Whiteboard: abrt_hash:fb18da4f5f102334eb096de96990d6d2a0d8c53f
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-12 11:11:57 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 Pavel Mlčoch 2013-12-22 12:58:05 UTC 
Version-Release number of selected component:
mate-panel-1.6.1-4.fc19

Additional info:
reporter:       libreport-2.1.10
backtrace_rating: 4
cmdline:        mate-panel
crash_function: g_slist_remove_all
executable:     /usr/bin/mate-panel
kernel:         3.12.5-200.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            1001

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 g_slist_remove_all at gslist.c:458
 #1 gtk_rc_clear_realized_style at gtkrc.c:1665
 #2 g_hash_table_foreach at ghash.c:1526
 #3 gtk_rc_reset_styles at gtkrc.c:1711
 #4 gtk_settings_notify at gtksettings.c:1423
 #10 g_object_notify_by_spec_internal at gobject.c:1136
 #11 g_object_notify at gobject.c:1178
 #12 _gtk_settings_handle_event at gtksettings.c:2151
 #13 gtk_main_do_event at gtkmain.c:1500
 #19 gtk_main at gtkmain.c:1257
Comment 1 Pavel Mlčoch 2013-12-22 12:58:10 UTC 
Created attachment 840335 [details]
File: backtrace
Comment 2 Pavel Mlčoch 2013-12-22 12:58:12 UTC 
Created attachment 840336 [details]
File: cgroup
Comment 3 Pavel Mlčoch 2013-12-22 12:58:15 UTC 
Created attachment 840337 [details]
File: core_backtrace
Comment 4 Pavel Mlčoch 2013-12-22 12:58:17 UTC 
Created attachment 840338 [details]
File: dso_list
Comment 5 Pavel Mlčoch 2013-12-22 12:58:19 UTC 
Created attachment 840339 [details]
File: environ
Comment 6 Pavel Mlčoch 2013-12-22 12:58:21 UTC 
Created attachment 840340 [details]
File: exploitable
Comment 7 Pavel Mlčoch 2013-12-22 12:58:24 UTC 
Created attachment 840341 [details]
File: limits
Comment 8 Pavel Mlčoch 2013-12-22 12:58:26 UTC 
Created attachment 840342 [details]
File: maps
Comment 9 Pavel Mlčoch 2013-12-22 12:58:29 UTC 
Created attachment 840343 [details]
File: open_fds
Comment 10 Pavel Mlčoch 2013-12-22 12:58:31 UTC 
Created attachment 840344 [details]
File: proc_pid_status
Comment 11 Pavel Mlčoch 2013-12-22 12:58:33 UTC 
Created attachment 840345 [details]
File: var_log_messages
Comment 12 Wolfgang Ulbrich 2013-12-29 09:09:39 UTC 
Can you describe a little more detailed what happend?
Did this issue occurs frequently ?
Comment 13 Sam Tygier 2014-05-28 07:49:50 UTC 
Looks like i hit this Bug 1101919