found 614049 1.1-2 notfound 614049 1.0-1 thanks Hi!
On Sat, 2011-02-19 at 18:25:35 +0200, Nikola Vladov wrote: > On Sat, Feb 19, 2011 at 11:15:02AM +0100, L.Schmidt wrote: > > Package: ngetty > > Version: 1.0-1 > > Severity: grave > > Justification: renders package unusable > > problem manifests during login dialog, or after dialog was completed. either > > case, the screen is blanked, and the "login:" prompt is presented again, > > after a variable time elapsed since login or login attempt - mostly between > > 1 and 20 seconds. According auth.log, username or password are > > irretrievable, > > even though actual login is possible, albeit not persistent. Downgrading pam > > to wheezy version doesn't change the behaviour. downgrading ngetty to 1.0, > > from wheezy, causes error symptoms to disappear, and reverts to apparently > > stable login behaviour again. > > Hmmm, > > something make problem on login. Ngetty doesn't change terminal setting > like agetty. Could you try for me the following: > > log as root on some terminal and start > > starce /sbin/agetty 38400 tty8 2>/tmp/XXX.getty > > Then login on tty8 and after that immediatelly logout. > Edit then the file /tmp/XXX.getty and remove your password. > > Similarly also for: > starce /sbin/ngetty 8 2>/tmp/XXX.ngetty > and > starce -f /sbin/ngetty 8 2>/tmp/XXX.nfgetty > > Then send me the files /tmp/XXX.*getty > > Since my native system is not debian, I cannot repoduce your > problems. I am the author of ngetty. > > If yoy have mmingetty try also > > starce /sbin/mingetty 8 2>/tmp/XXX.mgetty > > Say me also which getty works correct. You could try > also ngetty-1.0 and ngetty-1.1. How do you start ngetty > by inittab or by init.d script Found this problem too the other day when upgrading but didn't have the time to file a bug report. Anyway, the problem here is that init starts the agettys from inittab and ngetty starts itself too from the new init script. And both gettys fight for the terminal. This will happen if one has not deactivated the gettys entries in inittab, it might also happen if one has configured inittab to start the ngetty helper. The correct solution here is to remove the init script, and the users should change the inittab themselves. This also agrees with the sance from the sysvinit maintainer in #613618. thanks, guillem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
