Version-Release number of selected component: gdm-3.12.0-1.fc21 Additional info: reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: /usr/sbin/gdm crash_function: gdm_display_dispose executable: /usr/sbin/gdm kernel: 3.14.0-0.rc8.git0.1.fc21.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #4 gdm_display_dispose at gdm-display.c:1253 #6 gdm_display_finish at gdm-display.c:672 #7 remove_user_session at gdm-manager.c:1439 #12 ffi_call_unix64 at ../src/x86/unix64.S:76 #13 ffi_call at ../src/x86/ffi64.c:522 #14 g_cclosure_marshal_generic at gclosure.c:1445 #17 g_signal_emitv at gsignal.c:3045 #18 gdm_dbus_worker_proxy_g_signal at gdm-session-worker-glue.c:3528 #19 ffi_call_unix64 at ../src/x86/unix64.S:76 #20 ffi_call at ../src/x86/ffi64.c:522
Created attachment 880433 [details] File: backtrace
Created attachment 880434 [details] File: cgroup
Created attachment 880435 [details] File: core_backtrace
Created attachment 880436 [details] File: dso_list
Created attachment 880437 [details] File: environ
Created attachment 880438 [details] File: limits
Created attachment 880439 [details] File: maps
Created attachment 880440 [details] File: open_fds
Created attachment 880441 [details] File: proc_pid_status
Created attachment 880442 [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.