Version-Release number of selected component: gdm-3.12.2-2.fc21 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/sbin/gdm crash_function: gdm_display_finish executable: /usr/sbin/gdm kernel: 3.16.0-0.rc4.git0.1.fc21.1.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 gdm_display_finish #1 remove_user_session #6 ffi_call_unix64 at ../src/x86/unix64.S:76 #7 ffi_call at ../src/x86/ffi64.c:525 #8 g_cclosure_marshal_generic at /lib64/libgobject-2.0.so.0 #11 g_signal_emitv at /lib64/libgobject-2.0.so.0 #12 gdm_dbus_worker_proxy_g_signal #13 ffi_call_unix64 at ../src/x86/unix64.S:76 #14 ffi_call at ../src/x86/ffi64.c:525 #15 g_cclosure_marshal_generic at /lib64/libgobject-2.0.so.0
Created attachment 916730 [details] File: backtrace
Created attachment 916731 [details] File: cgroup
Created attachment 916732 [details] File: core_backtrace
Created attachment 916733 [details] File: dso_list
Created attachment 916734 [details] File: environ
Created attachment 916735 [details] File: exploitable
Created attachment 916736 [details] File: limits
Created attachment 916737 [details] File: maps
Created attachment 916738 [details] File: open_fds
Created attachment 916739 [details] File: proc_pid_status
Created attachment 916740 [details] File: var_log_messages
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.