Description of problem: probably fallout from systemd-207-2 breakage, but gnome3 should be more resilient Version-Release number of selected component: gnome-session-3.9.91-1.fc20 Additional info: reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: /usr/bin/gnome-session --autostart /usr/share/gdm/greeter/autostart crash_function: _g_log_abort executable: /usr/bin/gnome-session kernel: 3.12.0-0.rc0.git26.1.fc21.x86_64 runlevel: N 5 type: CCpp uid: 42 Truncated backtrace: Thread no. 1 (5 frames) #2 _g_log_abort at gmessages.c:255 #5 gsm_manager_quit at gsm-manager.c:533 #6 end_phase at gsm-manager.c:591 #7 remove_clients_for_connection at gsm-manager.c:1720 #8 gsm_manager_bus_filter at gsm-manager.c:1804
Created attachment 798722 [details] File: backtrace
Created attachment 798723 [details] File: cgroup
Created attachment 798724 [details] File: core_backtrace
Created attachment 798725 [details] File: dso_list
Created attachment 798726 [details] File: environ
Created attachment 798727 [details] File: limits
Created attachment 798728 [details] File: maps
Created attachment 798729 [details] File: open_fds
Created attachment 798730 [details] File: proc_pid_status
Created attachment 798731 [details] File: var_log_messages
Confirm on 3.10.0
Same for me on 3.10. I'm not sure if this is a stand alone issue or related to: https://bugzilla.gnome.org/show_bug.cgi?id=709810 which I was debugging and then after reboot I saw ABRT reporting this bug.
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
no comments for long time.