Bug#600755: [Pkg-shadow-devel] Bug#600755: Autologin fails with login from shadow 4.1.3.1
On Mon, 15 Nov 2010 23:29:01 +0100 Nicolas François nicolas.franc...@centraliens.net wrote: I did not reproduce this. Could you check if there are some information logged in /var/log/syslog or /var/log/auth.log. The problem has been solved on the Gentoo bug tracker: http://bugs.gentoo.org/show_bug.cgi?id=324419 It was a configuration issue. Including the console device for the CONSOLE option in login.defs causes the login program to fail: CONSOLE console:tty1:tty2:tty3:tty4 But shouldn't this still be considered a bug? The previous versions of login did not have trouble when reading the same login.defs configuration file. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#600755: [Pkg-shadow-devel] Bug#600755: Autologin fails with login from shadow 4.1.3.1
Hello, On Fri, Nov 19, 2010 at 11:52:25AM -0500, frank.pet...@comcast.net wrote: The problem has been solved on the Gentoo bug tracker: http://bugs.gentoo.org/show_bug.cgi?id=324419 It was a configuration issue. Including the console device for the CONSOLE option in login.defs causes the login program to fail: CONSOLE console:tty1:tty2:tty3:tty4 Thanks for the additional information. A bug was introduced in 4.1.4 in the CONSOLE parser, when CONSOLE does not point to a file with a list of ttys. The bug is in libmisc/console.c and will be fixed soon. -- Nekral -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#600755: [Pkg-shadow-devel] Bug#600755: Autologin fails with login from shadow 4.1.3.1
On Mon, 15 Nov 2010 23:29:01 +0100 Nicolas François nicolas.franc...@centraliens.net wrote: I did not reproduce this. Could you check if there are some information logged in /var/log/syslog or /var/log/auth.log. It might be that login is more strict regarding having an entry in UTMP before it is started, which might not be the case with the autologin method you are using. There might also be output indicating why login failed. You may have to block your script at the end (e.g. with 'read') or you can redirect login's stdout and stderr. I can't get any output at all. It seems the login program does not even execute. For example, after logging in as root using an older version (4.1.3.1) of login, when I manually execute login -f user with the newer login, the command hangs. There is no response and I need to do Ctl-C to regain control. Using the older login (4.1.3.1) allows the command login -f user to execute normally. I have been searching and also cannot find any reports that reproduce this problem. It could be just a peculiarity of my configuration somehow. Until I can do some more debugging, I'll just use login from shadow-4.1.3.1. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#600755: [Pkg-shadow-devel] Bug#600755: Autologin fails with login from shadow 4.1.3.1
Hello, On Tue, Oct 19, 2010 at 02:45:44PM -0400, frank.pet...@comcast.net wrote: My system is Gentoo, but Gentoo uses the shadow package that is maintained by Debian and it is appropriate to make a report here. I have been using the following autologin procedure on my machine to avoid passwords for some time without problems: http://www.gentoo-wiki.info/TIP_Passwordless_Login However, using any version of shadow greater than 4.1.3.1 causes this autologin procedure to fail. The system will only hang at boot and there are no errors logged. The trouble begins with login from shadow-4.1.4. Any login taken from shadow-4.1.3.1 or earlier allows the autologin procedure to succeed. There have been some changes to the login program that may cause this problem and it may be related to PAM. I do not use PAM on my system. A bug report was filed on the Gentoo bug tracker (https://bugs.gentoo.org/show_bug.cgi?id=324419) but this is definitely an upstream issue and needs to be reported to the Debian list. I did not reproduce this. Could you check if there are some information logged in /var/log/syslog or /var/log/auth.log. It might be that login is more strict regarding having an entry in UTMP before it is started, which might not be the case with the autologin method you are using. There might also be output indicating why login failed. You may have to block your script at the end (e.g. with 'read') or you can redirect login's stdout and stderr. -- Nekral -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
