Re: [Bug 516520] Re: pam_unix(gdm:auth): conversation failed
*** This bug is a duplicate of bug 553200 *** https://bugs.launchpad.net/bugs/553200 On 04/15/2010 01:09 AM, Martin Pitt wrote: *** This bug is a duplicate of bug 553200 *** https://bugs.launchpad.net/bugs/553200 Ah, that would explain also why I'm not able to reproduce the issue with any of the previous descriptions (changing gdmsetup, etc.). So I'm going to mark this as a duplicate of bug 553200. Thanks for all the help Martin. -- pam_unix(gdm:auth): conversation failed https://bugs.launchpad.net/bugs/516520 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 516520] Re: pam_unix(gdm:auth): conversation failed
On 04/13/2010 10:48 PM, Chris Thompson wrote: By disabling I mean using the System-Administration-Hardware Drivers and then specifying Remove as the action against Nvidia proprietary driver. Confirmed that doing the same works for me as well. Removed the driver via the same method, changed login screen to show user names, rebooted, got the username, clicked, entered password desktop is up. Thanks! Now I'll try testing by reinstalling nvidia-96 and then with just nouveau. I'll be watching #553200 as well. Thanks again Chris. -- pam_unix(gdm:auth): conversation failed https://bugs.launchpad.net/bugs/516520 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 516520] Re: pam_unix(gdm:auth): conversation failed
Now I'll try testing by reinstalling nvidia-96 and then with just nouveau. Reinstalling nvidia-96 reverts gdm back to the original symptoms. I'll have a look at trying: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/553200/comments/33 -- pam_unix(gdm:auth): conversation failed https://bugs.launchpad.net/bugs/516520 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 516520] Re: pam_unix(gdm:auth): conversation failed
NoOp [2010-04-08 17:25 -]: So what's actually left for you on this bug? To get the gdm menu working :-) gdm menu → is that System → Administration → Login Window configuration program? (i. e. gdmsetup). Or the login screen itself, which you see when you start the computer and disabled automatic login? I played around with gdmsetup a bit: Switched the automatic login user two times, disabled automatic login in favor or timed login (Allow 10 seconds for other users to login), and reenabled it again, etc. This all worked, so I really need very precise details about what's wrong here. From what I could understand from the bug trail so far, your problem seems to be that custom.conf gets broken as soon as you change something. However, you obfuscated your custom.conf in the bug trail (like in comment 42) to say username instead of the actual username, so it's not clear to me whether it had a working one or an invalid one (which seemed to be the case in the meantime). So, I understand that right now you have working autologin for the gg or ggserv user. What do you try to to in gdmsetup (please describe the exact steps), how does custom.conf look before and after? I. e. in which steps can you reproduce the broken custom.conf? Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- pam_unix(gdm:auth): conversation failed https://bugs.launchpad.net/bugs/516520 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 516520] Re: pam_unix(gdm:auth): conversation failed
Hello Chris, Chris Thompson [2010-04-12 11:01 -]: Attempt to login in user crt: gdm login screen asks for password, but mouse is frozen and no keyboard input accepted. After about 7 seconds gdm login screen redisplayed. This sounds like an entirely different problem. Can you please do ubuntu-bug and select the display symptom? Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- pam_unix(gdm:auth): conversation failed https://bugs.launchpad.net/bugs/516520 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 516520] Re: pam_unix(gdm:auth): conversation failed
On 04/12/2010 01:54 AM, Martin Pitt wrote: NoOp [2010-04-08 17:25 -]: So what's actually left for you on this bug? To get the gdm menu working :-) gdm menu → is that System → Administration → Login Window configuration program? (i. e. gdmsetup). Or the login screen itself, which you see when you start the computer and disabled automatic login? I played around with gdmsetup a bit: Switched the automatic login user two times, disabled automatic login in favor or timed login (Allow 10 seconds for other users to login), and reenabled it again, etc. This all worked, so I really need very precise details about what's wrong here. From what I could understand from the bug trail so far, your problem seems to be that custom.conf gets broken as soon as you change something. However, you obfuscated your custom.conf in the bug trail (like in comment 42) to say username instead of the actual username, so it's not clear to me whether it had a working one or an invalid one (which seemed to be the case in the meantime). So, I understand that right now you have working autologin for the gg or ggserv user. What do you try to to in gdmsetup (please describe the exact steps), how does custom.conf look before and after? I. e. in which steps can you reproduce the broken custom.conf? Martin I'm not sure what exactly you aren't understanding; I'v described the exact steps multiple times tested using multiple scenarios and logins. In the simplest terms, the symptoms are exactly as Chris Thompson has described. So as to remove any confusion regarding multiple users on the system I've deleted/removed *all* users with the exception of 'gg'. Set autologin to off (prompt for username at gdm startup), and the symptoms are exactly as prevously described by me and the others on this report. In order to get to the desktop I then have to Ctrl-Alt-F1 to get to a console, 'sudo nano /etc/gdm/custom.conf' and change it back to 'AutomaticLoginEnable=true', 'sudo stop gdm', 'sudo start gdm'. That gets you to the desktop, then go back to the console (Ctrl-Alt-F1), logout of the console '$ exit', and use Ctrl-Alt-F8 to get back to the desktop. -- pam_unix(gdm:auth): conversation failed https://bugs.launchpad.net/bugs/516520 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 516520] Re: pam_unix(gdm:auth): conversation failed
NoOp [2010-04-06 16:31 -]: Modified custom.conf to: [daemon] AutomaticLogin=laptop If you don't actually have a laptop user, this doesn't look healthy. How did it get there, was that damaged this way with System - Administration - Login Window? Or did you add it by hand? rebooted and the session results in bringing up the standard gdm menu list. Selected gg-main and it goes into the loop. Ctrl-Alt-F1 to console - log in as gg, So is your user gg or gg-main? - 'sudo nano /etc/gdm/custom.conf', - change from 'laptop' to 'gg', - 'sudo stop gdm' and then 'sudo start gdm' - back into user 'gg' desktop. This looks like it worked? -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- pam_unix(gdm:auth): conversation failed https://bugs.launchpad.net/bugs/516520 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 516520] Re: pam_unix(gdm:auth): conversation failed
NoOp [2010-04-07 14:50 -]: For some unknown reason, the screen resolution has been modified during the upgrade process to an unsupported value. I changed the screen resolution according the monitor's specs and the login loop problem disappeared. Ah, that would explain it, too. You can try deleting ~/.config/monitors.xml, which will not touch the resolution during login any more. Admittedly I'm still confused about this bug. There are several reporters, several situations with various valid and invalid login names, and now the screen resolution issue... -- pam_unix(gdm:auth): conversation failed https://bugs.launchpad.net/bugs/516520 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 516520] Re: pam_unix(gdm:auth): conversation failed
On 04/08/2010 02:53 AM, Martin Pitt wrote: NoOp [2010-04-06 16:31 -]: Modified custom.conf to: [daemon] AutomaticLogin=laptop If you don't actually have a laptop user, this doesn't look healthy. How did it get there, was that damaged this way with System - Administration - Login Window? Or did you add it by hand? I'd modified it by hand. I had taken your Can you please check if your /etc/gdm/custom.conf still tries to log in the laptop user automatically? to mean modify to try with 'laptop'. It's of course back to 'gg'. rebooted and the session results in bringing up the standard gdm menu list. Selected gg-main and it goes into the loop. Ctrl-Alt-F1 to console - log in as gg, So is your user gg or gg-main? User is 'gg' home for that user is 'gg'. 'gg-main' is the machine sometime back I'd changed the 'full name' to 'gg-main' just so that I'd remember the machne name. Doesn't matter. If I change the full name to 'gg' so that 'gg' shows up on the gdm menu, the results are the same. To avoid further confusion in troubleshooting this bug I've changed it back to 'gg'. - 'sudo nano /etc/gdm/custom.conf', - change from 'laptop' to 'gg', - 'sudo stop gdm' and then 'sudo start gdm' - back into user 'gg' desktop. This looks like it worked? Yes. -- pam_unix(gdm:auth): conversation failed https://bugs.launchpad.net/bugs/516520 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 516520] Re: pam_unix(gdm:auth): conversation failed
On 04/08/2010 02:55 AM, Martin Pitt wrote: NoOp [2010-04-07 14:50 -]: For some unknown reason, the screen resolution has been modified during the upgrade process to an unsupported value. I changed the screen resolution according the monitor's specs and the login loop problem disappeared. Ah, that would explain it, too. You can try deleting ~/.config/monitors.xml, which will not touch the resolution during login any more. Tried that - No change. Checked the other users monitors.xml isn't in their ~/.config. However, I wouldn't expect that to make any difference anyway as that is user dependent. As mentioned, the situation occurs even when custom.conf is reset to log in as another user on reboot also occurs when I create a new user. I've also tested on the system side by using the previous karmic xorg.conf and also tested by moving xorg.conf completely out of the way. -- pam_unix(gdm:auth): conversation failed https://bugs.launchpad.net/bugs/516520 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 516520] Re: pam_unix(gdm:auth): conversation failed
NoOp [2010-04-08 15:21 -]: User is 'gg' home for that user is 'gg'. 'gg-main' is the machine sometime back I'd changed the 'full name' to 'gg-main' just so that I'd remember the machne name. Doesn't matter. If I change the full name to 'gg' so that 'gg' shows up on the gdm menu, the results are the same. To avoid further confusion in troubleshooting this bug I've changed it back to 'gg'. Ah, thanks for the explanation. So the AutomatiLogin= argument needs to be an user name, not a machine name. - 'sudo nano /etc/gdm/custom.conf', - change from 'laptop' to 'gg', - 'sudo stop gdm' and then 'sudo start gdm' - back into user 'gg' desktop. This looks like it worked? Yes. So what's actually left for you on this bug? -- pam_unix(gdm:auth): conversation failed https://bugs.launchpad.net/bugs/516520 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 516520] Re: pam_unix(gdm:auth): conversation failed
On 04/08/2010 08:47 AM, Martin Pitt wrote: ... - 'sudo nano /etc/gdm/custom.conf', - change from 'laptop' to 'gg', - 'sudo stop gdm' and then 'sudo start gdm' - back into user 'gg' desktop. This looks like it worked? Yes. So what's actually left for you on this bug? To get the gdm menu working :-) The above is from the console. I can: 1. Change the custom.conf to any of the valid users while in the desktop (after getting there by autologin first). Example, from the 'gg' desktop, change to 'ggserv': [daemon] AutomaticLogin=ggserv AlwaysLoginCurrentSession=false AutomaticLoginEnable=true TimedLoginEnable=false TimedLogin=ggserv TimedLoginDelay=30 DefaultSession=gnome.desktop 2. Ctrl-Alt-F1-6 and get to the console and login as 'gg' (that username has admin privileges). Note: I can also use nano to change custom.conf after console login of course. 3. 'sudo stop gdm' then 'sudo start gdm' that will bring up the 'ggserv' desktop. If I want to switch back to 'gg' I cannot use the gdm menu, I must go back to the console, change the custom.conf again back to 'gg' (Ctrl-Alt-F1), and then start/stop gdm to get back to the 'gg' desktop. Confusing, but that is the only way that I can switch to another user. -- pam_unix(gdm:auth): conversation failed https://bugs.launchpad.net/bugs/516520 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 516520] Re: pam_unix(gdm:auth): conversation failed
When I had the problem that is how I got myself logged in, yes. I had to unlock the keyring manually, but that was it. Right now it is working as it should (see earlier post; one of many updates solved it). cheers Tom -- pam_unix(gdm:auth): conversation failed https://bugs.launchpad.net/bugs/516520 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 516520] Re: pam_unix(gdm:auth): conversation failed
NoOp, thanks, the PAM related files/outputs look alright. Can you please check if your /etc/gdm/custom.conf still tries to log in the laptop user automatically? Also, can you try changing DefaultSession=gnome to DefaultSession=gnome.desktop? (Log into a text terminal with Ctrl+Alt+F1 and do sudo nano /etc/gdm/custom.conf). Finally, do you have the ubuntu-desktop package installed? Modified custom.conf to: [daemon] AutomaticLogin=laptop AlwaysLoginCurrentSession=false AutomaticLoginEnable=true TimedLoginEnable=false TimedLogin=laptop TimedLoginDelay=30 DefaultSession=gnome.desktop rebooted and the session results in bringing up the standard gdm menu list. Selected gg-main and it goes into the loop. Ctrl-Alt-F1 to console - log in as gg, - 'sudo nano /etc/gdm/custom.conf', - change from 'laptop' to 'gg', - 'sudo stop gdm' and then 'sudo start gdm' - back into user 'gg' desktop. Yes, I have ubuntu-destop version: $ apt-cache policy ubuntu-desktop ubuntu-desktop: Installed: 1.195 Candidate: 1.195 Version table: *** 1.195 0 500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status installed. Attached are auth.log (for today only), 0-greeter.log.1 0-greeter.log. ** Attachment added: auth.log http://launchpadlibrarian.net/43260196/auth.log ** Attachment added: 0-greeter.log.1 http://launchpadlibrarian.net/43260197/0-greeter.log.1 ** Attachment added: 0-greeter.log http://launchpadlibrarian.net/43260198/0-greeter.log -- pam_unix(gdm:auth): conversation failed https://bugs.launchpad.net/bugs/516520 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 516520] Re: pam_unix(gdm:auth): conversation failed
NoOp [2010-04-03 0:23 -]: gdm-simple-greeter[2584]: WARNING: Unable to lookup user name laptop: Success Is your user name actually called laptop? If so, can you please give me the output of these commands: getent passwd laptop ls -l /etc/passwd /etc/shadow grep passwd /etc/nsswitch.conf Thanks! -- pam_unix(gdm:auth): conversation failed https://bugs.launchpad.net/bugs/516520 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 516520] Re: pam_unix(gdm:auth): conversation failed
.. gdm-simple-greeter[2584]: WARNING: Unable to lookup user name laptop: Success Is your user name actually called laptop? If so, can you please give me the output of these commands: getent passwd laptop ls -l /etc/passwd /etc/shadow grep passwd /etc/nsswitch.conf No. There may have been an effort to add a user 'laptop' quite some time ago (this machine went from dapper thru lucid). I have my 'Users Settings' to show all users groups there is no 'laptop' in either. $ cat /etc/passwd shows no 'laptop' user, nor does 'groups laptop'. $ getent passwd laptop results in nothing. $ ls -l /etc/passwd /etc/shadow -rw-r--r-- 1 root root 2694 2010-04-05 11:24 /etc/passwd -rw-r- 1 root shadow 1717 2010-04-05 11:24 /etc/shadow $ grep passwd /etc/nsswitch.conf passwd: compat (group shadow show the same). I do however have a user 'gg-laptop'. These are the getent for the standard users: g...@gg-main:~$ getent passwd gg-laptop gg-laptop:x:1003:1002:gg-laptop:/home/gg-laptop:/bin/bash g...@gg-main:~$ getent passwd gg gg:x:1000:1000:gg-main:/home/gg:/bin/bash g...@gg-main:~$ getent passwd gg2xp gg2xp:x:1001:1001:gg2xp:/home/gg2xp:/bin/bash $ getent passwd ggserv ggserv:x:1004:1003:ggserv:/home/gg-server:/bin/bash g...@gg-main:~$ getent passwd ggxg ggxg:x:1002:1000:ggxg:/home/ggxg:/bin/bash g...@gg-main:~$ getent passwd ggxp ggxp:x:1005:1005:ggxp:/home/ggxp:/bin/sh -- pam_unix(gdm:auth): conversation failed https://bugs.launchpad.net/bugs/516520 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 516520] Re: pam_unix(gdm:auth): conversation failed
On 04/01/2010 03:01 PM, Johannes Rohr wrote: I have seen the same. What solved it for me was purging gdm and reinstalling it, this indicates that there is indeed something wrong with the conffiles ( dpkg --purge --force-depends gdm gdm-guest-session ) That worked - once. Note: I'd even mv'ed /etc/gdm out of the way to /etc/x-gdm-x and then of course reinstalled gdm gdm-guest-session and ubuntu-desktop. Rebooted I could login via gdm, but when I rebooted tried to log in again I got the loop again as soon as I tried to enter the password. Mouse freezes, screen goes black, gdm starts again, select user, rinse, repeat. Had to go back to recovery mode again, resume, login via the console, 'startx'. Then create an /etc/gdm/custom.conf file again so that I can at least autologin with the primary user: [daemon] AutomaticLogin=username AlwaysLoginCurrentSession=false AutomaticLoginEnable=true TimedLoginEnable=false TimedLogin=username TimedLoginDelay=30 DefaultSession=gnome Rebooted w/autologin 4 times just to be sure that is working. Also tried with a different username/account in the 'custom.conf' and rebooted several time that works as well. So I think as Steve Martin point out, this is most likely a PAM isse. @Steve/Martin: the machine is 100% under my control so I'm willing to provide additional info and/or purge/modify any PAM/passwd's if that will help. -- pam_unix(gdm:auth): conversation failed https://bugs.launchpad.net/bugs/516520 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
