Description of problem: All I did was boot into the VM, and log into the Mate desktop with xmonad. I don't think I made any changes at all (not even updating since this was from a netinstall) apart from running a few commands to fix an SELinux warning. Version-Release number of selected component: mate-panel-1.7.1-1.fc21 Additional info: reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: mate-panel crash_function: g_type_check_instance_cast executable: /usr/bin/mate-panel kernel: 3.14.0-0.rc0.git3.1.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (9 frames) #0 g_type_check_instance_cast at gtype.c:4008 #1 container_child_background_set at mate-panel-applet-frame-dbus.c:235 #2 g_simple_async_result_complete at gsimpleasyncresult.c:770 #3 set_applet_property_cb at mate-panel-applet-container.c:560 #4 g_simple_async_result_complete at gsimpleasyncresult.c:770 #5 g_dbus_connection_call_done at gdbusconnection.c:5480 #6 g_simple_async_result_complete at gsimpleasyncresult.c:770 #7 complete_in_idle_cb at gsimpleasyncresult.c:782 #12 gtk_main at gtkmain.c:1257
Created attachment 854668 [details] File: backtrace
Created attachment 854669 [details] File: cgroup
Created attachment 854670 [details] File: core_backtrace
Created attachment 854671 [details] File: dso_list
Created attachment 854672 [details] File: environ
Created attachment 854673 [details] File: exploitable
Created attachment 854674 [details] File: limits
Created attachment 854675 [details] File: maps
Created attachment 854676 [details] File: open_fds
Created attachment 854677 [details] File: proc_pid_status
Created attachment 854678 [details] File: var_log_messages
Still happening?
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
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.