Description of problem: 1) Installed Fedora20 Alpha release as VM within my Fedora19 laptop 2) Ran yum update and rebooted. Version-Release number of selected component: mate-window-manager-1.6.2-4.fc20 Additional info: reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: /usr/bin/marco crash_function: _g_log_abort executable: /usr/bin/marco kernel: 3.11.0-300.fc20.x86_64 runlevel: unknown type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #2 _g_log_abort at gmessages.c:255 #5 meta_ui_get_default_window_icon at ui/ui.c:741 #6 get_fallback_icons at core/iconcache.c:45 #7 meta_read_icons at core/iconcache.c:824 #8 meta_window_update_icon_now at core/window.c:5788 #9 meta_window_new_with_attrs at core/window.c:608 #10 meta_window_new at core/window.c:224 #11 event_callback at core/display.c:2207 #12 filter_func at ui/ui.c:209 #13 gdk_event_apply_filters at gdkevents-x11.c:356
Created attachment 802277 [details] File: backtrace
Created attachment 802278 [details] File: cgroup
Created attachment 802279 [details] File: core_backtrace
Created attachment 802280 [details] File: dso_list
Created attachment 802281 [details] File: environ
Created attachment 802282 [details] File: limits
Created attachment 802283 [details] File: maps
Created attachment 802284 [details] File: open_fds
Created attachment 802285 [details] File: proc_pid_status
Created attachment 802286 [details] File: var_log_messages
I've been noticed about the same issue in a fresh installed f20 in a VM. But this abrt alarm isn't triggered during yum update. Seems the update fixed a non working abrt in your case ;) The crash was triggered outside from Mate with initial-setup, see environ file. Here you see that no MATE session was active. *** This bug has been marked as a duplicate of bug 962009 ***