Version-Release number of selected component: mate-panel-1.12.2-2.fc23 Additional info: reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: mate-panel crash_function: g_slist_remove_all executable: /usr/bin/mate-panel global_pid: 1674 kernel: 4.5.5-201.fc23.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 #4 gtk_settings_notify at gtksettings.c:1423 #10 g_object_notify_by_spec_internal at gobject.c:1154 #11 g_object_notify at gobject.c:1202 #12 _gtk_settings_handle_event at gtksettings.c:2151 #13 gtk_main_do_event at gtkmain.c:1511 #19 gtk_main at gtkmain.c:1268 Potential duplicate: bug 1101919
Created attachment 1165803 [details] File: backtrace
Created attachment 1165804 [details] File: cgroup
Created attachment 1165805 [details] File: core_backtrace
Created attachment 1165806 [details] File: dso_list
Created attachment 1165807 [details] File: environ
Created attachment 1165808 [details] File: exploitable
Created attachment 1165809 [details] File: limits
Created attachment 1165810 [details] File: maps
Created attachment 1165811 [details] File: mountinfo
Created attachment 1165812 [details] File: namespaces
Created attachment 1165813 [details] File: open_fds
Created attachment 1165814 [details] File: proc_pid_status
Created attachment 1165815 [details] File: var_log_messages
Can you provide a valid description? Steps to reproduce? Did this issue occurs frequently ? Is the problem still exists with the latest updates?
I don't really know what happened... It's a long time ago that this happened in a fresh install. Not sure this was on VM or metal. Probably trying to run some automated setup scripts by invoking gsettings command directly and without using UI that got MATE crashed and restarted. I suppose you can close it since I don't think it will trigger again for now...
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 EOL if it remains open with a Fedora 'version' of '23'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 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 this bug is closed as described in the policy above. 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.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.