[Bug 387311] New: can't login via gdm
https://bugzilla.novell.com/show_bug.cgi?id=387311 Summary: can't login via gdm Product: openSUSE 11.0 Version: Beta 2 Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome@forge.provo.novell.com ReportedBy: mmeeks@novell.com QAContact: qa@suse.de Found By: --- I did a network install of beta2 from the DVD on some rather old hardware, there were a number of very strange things that happened in the "Automatic Configuration" stage: possibly yast2-gtk issues. Anyhow - at the end of the day - apparently everything installed, and I logged in once. However on subsequent re-boots I can enter user / password details to gdm and then it hangs: in /var/log/messages I get: gdm[2804]: gkr-pam: couldn't get the user-name: Conversation error and then (apparently) nothing happens (at some length) ;-) I can log-in fine on the console; so clearly gdm specific. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=387311 User mmeeks@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=387311#c1 --- Comment #1 from Michael Meeks <mmeeks@novell.com> 2008-05-06 10:39:15 MST --- interestingly - it seems like (for whatever reason) when I ran my straces, that gdm had managed to do whatever it does to authenticate as me, and was then blocking on gconfd. gconfd appeared to be deadlocked from a signal handler, which was running some nasty cleanup process taking the GContext lock (or something). Unfortunately the gconfd trace was fairly unusable, and factory is knackered wrt. installing any sort of packages just now (making life hard to debug). Anyhow a killall -9 gconfd-2 caused the login process to resume & eventually even complete. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=387311 User jpr@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=387311#c2 JP Rosevear <jpr@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Critical |Major --- Comment #2 from JP Rosevear <jpr@novell.com> 2008-05-12 08:01:32 MST --- I can't say as I know what to do with this bug, we have no other reports currently or in the past 11.0 cycle that are similar. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=387311 User jpr@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=387311#c3 JP Rosevear <jpr@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |mmeeks@novell.com --- Comment #3 from JP Rosevear <jpr@novell.com> 2008-05-13 13:41:19 MST --- Michael, can you still repeat the login hang? Any chance of better debug info? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=387311 User mmeeks@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=387311#c4 Michael Meeks <mmeeks@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|mmeeks@novell.com | --- Comment #4 from Michael Meeks <mmeeks@novell.com> 2008-05-14 03:00:04 MST --- sadly not; let me try one more time though.
From the gconfd partial trace I got it -looked- like gconf was shutting down while we logged in - so, presumably some shutdown race condition that caused a SEGV and from that deadlock - but ...
I assume this is a really rare occurence. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=387311 User mmeeks@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=387311#c5 --- Comment #5 from Michael Meeks <mmeeks@novell.com> 2008-05-14 03:21:58 MST --- sigh; sadly it works fine for me now; it's really likely to be a rare & hard-to-repeat race - the bad trace is: # find the blocking socket: fuser /tmp/orbit-michael/linc-1fe0-0-384a3d583935c /tmp/orbit-michael/linc-1fe0-0-384a3d583935c: 8160 linux:~ # ps auwx | grep 8160 michael 8160 0.0 3.3 16856 8468 ? S 15:10 0:03 /usr/lib/GConf/2/gconfd-2 4 # gdb on gconf: Thread 1 (Thread 0xb7d676c0 (LWP 8160)): #0 0xffffe430 in __kernel_vsyscall () #1 0xb7fdc7a9 in __lll_lock_wait () from /lib/libpthread.so.0 #2 0xb7fd7c66 in _L_lock_89 () from /lib/libpthread.so.0 #3 0xb7fd7572 in pthread_mutex_lock () from /lib/libpthread.so.0 #4 0xb7f0dc33 in g_main_loop_quit () from /usr/lib/libglib-2.0.so.0 #5 0x0804fdc9 in ?? () #6 0x0806c2b0 in ?? () #7 0x08bc8890 in ?? () #8 0xb7e2dcee in ?? () from /lib/libc.so.6 #9 0xb7f8a3b8 in ?? () from /usr/lib/libglib-2.0.so.0 #10 0xb7f8a3e0 in ?? () from /usr/lib/libglib-2.0.so.0 #11 0xb7f8a3b8 in ?? () from /usr/lib/libglib-2.0.so.0 #12 0xbffaaec8 in ?? () #13 <signal handler called> #14 0xb7f0ef68 in ?? () from /usr/lib/libglib-2.0.so.0 #15 0x0806159c in ?? () #16 0xb7f8a768 in ?? () from /usr/lib/libglib-2.0.so.0 #17 0xbffaaed8 in ?? () #18 0xb7f0f08f in g_source_destroy () from /usr/lib/libglib-2.0.so.0 #19 0xb8036fc5 in ?? () from /usr/lib/libORBit-2.so.0 #20 0x00000000 in ?? () #0 0xffffe430 in __kernel_vsyscall () -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=387311 User mmeeks@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=387311#c6 --- Comment #6 from Michael Meeks <mmeeks@novell.com> 2008-05-14 05:13:52 MST --- I guess the deadlock is only to be expected in this case - reading the code. It's not that clear to me why gconfd likes to catch various signals and try to clean itself up (at the risk of deadlocking like this) - an outright termination might be cleaner. Unclear what to do. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=387311 User jpr@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=387311#c7 JP Rosevear <jpr@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #7 from JP Rosevear <jpr@novell.com> 2008-07-02 14:14:28 MDT --- Resolving as invalid, please re-open if you can get better replication. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com