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: g_type_check_instance_is_fundamentally_a executable: /usr/sbin/gdm kernel: 3.16.0-0.rc2.git1.2.fc21.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 g_type_check_instance_is_fundamentally_a at gtype.c:3978 #2 g_hash_table_remove_internal at ghash.c:1300 #3 ffi_call_unix64 at ../src/x86/unix64.S:76 #4 ffi_call at ../src/x86/ffi64.c:525 #5 g_cclosure_marshal_generic_va at gclosure.c:1541 #6 _g_closure_invoke_va at gclosure.c:831 #9 on_reauthentication_started_cb at gdm-session.c:889 #10 g_simple_async_result_complete at gsimpleasyncresult.c:763 #11 reply_cb at gdbusproxy.c:2623 #12 g_simple_async_result_complete at gsimpleasyncresult.c:763
Created attachment 912722 [details] File: backtrace
Created attachment 912723 [details] File: cgroup
Created attachment 912724 [details] File: core_backtrace
Created attachment 912725 [details] File: dso_list
Created attachment 912726 [details] File: environ
Created attachment 912727 [details] File: exploitable
Created attachment 912728 [details] File: limits
Created attachment 912729 [details] File: maps
Created attachment 912730 [details] File: open_fds
Created attachment 912731 [details] File: proc_pid_status
Created attachment 912732 [details] File: var_log_messages
Another user experienced a similar problem: Sometimes gdm crashes in gnome-shell shield reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/sbin/gdm crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/sbin/gdm kernel: 3.15.3-200.fc20.x86_64 package: gdm-3.12.2-2.fc21 reason: gdm killed by SIGSEGV runlevel: N 5 type: CCpp uid: 0
Forwarded to this bug by abrt. This constitutes a data loss bug as it results in gnome-shell crashing along with all work in-progress, bug 1118997. Occurred when entering wrong password at shield, but seems transient at this point. I did get notification of a wrong password, then got a "reload" of gdm and the login screen. gdm-3.12.2-3.fc21.x86_64 kernel-3.16.0-1.fc21.x86_64 [root@twenty1 ccpp-2014-08-05-19:23:50-946]# dmesg | grep -i gdm [ 3905.109886] gdm[946]: segfault at 14 ip 00007f4971cd0db7 sp 00007fff1dbee788 error 4 in libgobject-2.0.so.0.4102.0[7f4971c9d000+50000] [root@twenty1 ccpp-2014-08-05-19:23:50-946]# dmesg | grep -i gnome-shell [ 3905.687954] gnome-shell[1760]: segfault at 10 ip 00007fe5d123e79c sp 00007fffe1192290 error 4 in r600_dri.so[7fe5d115e000+4d3000]
trying to unlock screen, after suspend crashed gdm.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.