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

/nv

> 
> from auth.log:
> login[24632]: pam_unix(login:auth): auth could not identify password for 
> [user]
> login[24632]: FAILED LOGIN (1) on '/dev/tty1' FOR 'user', Authentication 
> failure
> login[24632]: pam_securetty(login:auth): unexpected response from failed 
> conversation function
> login[24632]: pam_securetty(login:auth): cannot determine username
> login[24632]: FAILED LOGIN (2) on '/dev/tty1' FOR 'UNKNOWN', Error in service 
> module
> login[24632]: pam_securetty(login:auth): unexpected response from failed 
> conversation function
> login[24632]: pam_securetty(login:auth): cannot determine username
> login[24632]: FAILED LOGIN (3) on '/dev/tty1' FOR 'UNKNOWN', Error in service 
> module
> login[24632]: pam_securetty(login:auth): unexpected response from failed 
> conversation function
> login[24632]: pam_securetty(login:auth): cannot determine username
> login[24632]: FAILED LOGIN (4) on '/dev/tty1' FOR 'UNKNOWN', Error in service 
> module
> login[24632]: pam_securetty(login:auth): unexpected response from failed 
> conversation function
> login[24632]: pam_securetty(login:auth): cannot determine username
> login[24632]: FAILED LOGIN (5) on '/dev/tty1' FOR 'UNKNOWN', Error in service 
> module
> login[24632]: TOO MANY LOGIN TRIES (5) on '/dev/tty1' FOR 'UNKNOWN'
> login[24632]: pam_mail(login:session): cannot determine username
> login[24632]: pam_unix(login:session): close_session - error recovering 
> username
> 
> 
> -- System Information:
> Debian Release: wheezy/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: i386 (i686)
> 
> Kernel: Linux 2.6.32-5-686 (SMP w/4 CPU cores)
> Locale: LANG=C, LC_CTYPE=en (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to 
> C)
> Shell: /bin/sh linked to /bin/dash
> 
> -- no debconf information
> 
> 
> 



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to