Bug 1293096

Summary: [abrt] mate-panel: g_slist_remove_all(): mate-panel killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Kalin Tsonchev <kalintsonchev>
Component: gtk2Assignee: Matthias Clasen <mclasen>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: fedora, mclasen, stefano
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/93660919bff1cf305f04d40419ebe157faa99ac9
Whiteboard: abrt_hash:fb18da4f5f102334eb096de96990d6d2a0d8c53f;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 18:37:06 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: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Kalin Tsonchev 2015-12-20 07:36:18 UTC 
Description of problem:
The laptop shut down after the battery died and this is what happend when rebooting the system.

Version-Release number of selected component:
mate-panel-1.12.1-1.fc22

Additional info:
reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        mate-panel
crash_function: g_slist_remove_all
executable:     /usr/bin/mate-panel
global_pid:     2287
kernel:         4.2.6-201.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 g_slist_remove_all at gslist.c:445
 #1 gtk_rc_clear_realized_style at gtkrc.c:1665
 #2 g_hash_table_foreach at ghash.c:1607
 #3 gtk_rc_reset_styles at gtkrc.c:1711
 #9 g_object_notify_by_spec_internal at gobject.c:1149
 #10 g_object_notify at gobject.c:1197
 #11 apply_queued_setting at gtksettings.c:1519
 #12 gtk_settings_set_property_value_internal at gtksettings.c:1713
 #13 _gtk_settings_set_property_value_from_rc at gtksettings.c:1738
 #14 gtk_rc_parse_statement at gtkrc.c:2966

Potential duplicate: bug 1101919
Comment 1 Kalin Tsonchev 2015-12-20 07:36:23 UTC 
Created attachment 1107898 [details]
File: backtrace
Comment 2 Kalin Tsonchev 2015-12-20 07:36:24 UTC 
Created attachment 1107899 [details]
File: cgroup
Comment 3 Kalin Tsonchev 2015-12-20 07:36:26 UTC 
Created attachment 1107900 [details]
File: core_backtrace
Comment 4 Kalin Tsonchev 2015-12-20 07:36:28 UTC 
Created attachment 1107901 [details]
File: dso_list
Comment 5 Kalin Tsonchev 2015-12-20 07:36:29 UTC 
Created attachment 1107902 [details]
File: environ
Comment 6 Kalin Tsonchev 2015-12-20 07:36:30 UTC 
Created attachment 1107903 [details]
File: limits
Comment 7 Kalin Tsonchev 2015-12-20 07:36:32 UTC 
Created attachment 1107904 [details]
File: maps
Comment 8 Kalin Tsonchev 2015-12-20 07:36:33 UTC 
Created attachment 1107905 [details]
File: mountinfo
Comment 9 Kalin Tsonchev 2015-12-20 07:36:35 UTC 
Created attachment 1107906 [details]
File: namespaces
Comment 10 Kalin Tsonchev 2015-12-20 07:36:36 UTC 
Created attachment 1107907 [details]
File: open_fds
Comment 11 Kalin Tsonchev 2015-12-20 07:36:37 UTC 
Created attachment 1107908 [details]
File: proc_pid_status
Comment 12 Kalin Tsonchev 2015-12-20 07:36:39 UTC 
Created attachment 1107909 [details]
File: var_log_messages
Comment 13 Fedora End Of Life 2016-07-19 18:37:06 UTC 
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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