GNOME Bugzilla – Bug 67593
gnome-login-check crashes, preventing gdm from working (gnome-login-check Crash at 62.49.193.250)
Last modified: 2004-12-22 21:47:04 UTC
Package: gnome-core Version: 0.1 Severity: >Synopsis: gnome-login-check crashes, preventing gdm from working >Class: sw-bug System: Intel P3 633, RedHat Linux 7.0 >Description: Every time I try to log in using gdm, the gnome session fails to start, and it takes me straight back to the login screen. On attempting to use startx instead, I get an error message saying gnome-login-check has crashed, core dumped etc. Have verified all the relevant rpms. >How-To-Repeat: ------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-12-27 12:40 ------- The original reporter (henry@40princes.com) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, gnome-core-maint@bugzilla.gnome.org.
Ok we are getting a few different reports of this.
*** Bug 67869 has been marked as a duplicate of this bug. ***
*** Bug 69402 has been marked as a duplicate of this bug. ***
*** Bug 69470 has been marked as a duplicate of this bug. ***
*** Bug 70603 has been marked as a duplicate of this bug. ***
*** Bug 71302 has been marked as a duplicate of this bug. ***
*** Bug 72517 has been marked as a duplicate of this bug. ***
Here is the stack trace from bug 72517: Package: gnome-build Severity: normal Version: 0.1 Synopsis: gnome-login-check application crashed Bugzilla-Product: gnome-build Bugzilla-Component: miscellaneous Description: Just logged into redhat 7.2 system as the user "oracle" and got this message. Debugging Information: (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...0x4050ee29 in __wait4 () from /lib/libc.so.6
+ Trace 18581
*** Bug 73096 has been marked as a duplicate of this bug. ***
*** Bug 73235 has been marked as a duplicate of this bug. ***
*** Bug 65953 has been marked as a duplicate of this bug. ***
*** Bug 66080 has been marked as a duplicate of this bug. ***
hmmm that stack trace above is fairly useless/confusing. I'm not sure if this is a serious bug or not.
*** Bug 73932 has been marked as a duplicate of this bug. ***
*** Bug 75502 has been marked as a duplicate of this bug. ***
*** Bug 83268 has been marked as a duplicate of this bug. ***
I think this has been fixed in the latest releases. Please confirm.
Closing as fixed.