Same issue; however I found that at the end of the recovery mode messages, I hit enter, msgs to to last, and then from there I can do Ctrl-Alt-F1 and get into a console. From that I can login, stop gdm (need to use 'sudo /etc/init.d/gdm stop'), and then 'startx' and I'm in.
auth.log is showing: Mar 31 10:18:17 x gdm-session-worker[1259]: pam_succeed_if(gdm:auth): requirement "user ingroup nopasswdlogin" not met by user "x" Mar 31 10:18:23 x gdm-session-worker[1259]: pam_unix(gdm:auth): conversation failed Mar 31 10:18:23 x gdm-session-worker[1259]: pam_unix(gdm:auth): auth could not identify password for [x] Mar 31 10:18:23 x gdm-session-worker[1259]: pam_winbind(gdm:auth): getting password (0x00000388) Mar 31 10:18:23 x gdm-session-worker[1259]: pam_winbind(gdm:auth): Could not retrieve user's password Mar 31 10:19:32 xn gdm-session-worker[1503]: pam_succeed_if(gdm:auth): requirement "user ingroup nopasswdlogin" not met by user "x" Mar 31 10:19:39 x gdm-session-worker[1503]: pam_unix(gdm:auth): conversation failed Mar 31 10:19:39 x gdm-session-worker[1503]: pam_unix(gdm:auth): auth could not identify password for [x] Mar 31 10:19:39 x gdm-session-worker[1503]: pam_winbind(gdm:auth): getting password (0x00000388) Mar 31 10:19:39 x gdm-session-worker[1503]: pam_winbind(gdm:auth): Could not retrieve user's password Added note: This is on a system that was upgraded from 9.10 to 10.04. Had similar issue on a clean 10.04 install that has been kept upgraded from beta1. Gdm on that system is however working this afternoon. Looking at yesterday's auth.log on that machine shows the same errors yesterday, none today. -- lucid lynx - login screen stuck in a loop - SYSTEM BROKEN https://bugs.launchpad.net/bugs/516520 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
