In the attachment there are parts of the auth.log from the time in question, I left out duplicate parts. My editing in the config to fix the problem could be the reason for errors at the end of the log.
I also tried to reproduce the bug, by setting auth-common and auth- password back to the "old" version from my first post. In a second terminal, I tried to do a 'sudo -s' and got this in Terminal: Segmentation fault. Unfortunately this doesn't seems to be the same problem to me, since the behaviour is different (didn't get any error in terminal in the first place). But anyway, here is the entry in auth.log corresponding to the new login try: Nov 16 22:40:01 my-username-desktop CRON[19449]: pam_unix(cron:session): session opened for user root by (uid=0) Nov 16 22:40:01 my-username-desktop CRON[19449]: pam_unix(cron:session): session closed for user root >I suppose it could have an effect on gdm's behavior /after/ a failed login, >but that doesn't seem to be the problem you're reporting? No, I don't think so. Maybe I mistyped at my first login try, but I also restarted and still couldn't log in. ** Attachment added: "parts_of_auth.log" http://launchpadlibrarian.net/19704777/parts_of_auth.log -- login impossible, no error message https://bugs.launchpad.net/bugs/292791 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
