You are not logged in.
I executed a complete system upgrade yesterday. Now when I attempt to login in (through the terminal, not graphically) it allows me to enter my username and then instead of prompting for a password it immediately reports "incorrect password" about four times and the returns to the login prompt again. I have no idea where to begin debugging this and would appreciate some input.
Thank you,
Brendan
Offline
Is it possible to get a copy of your /etc/inittab posted for us to look at?
Offline
Thank you so much for the quick reply! Here is my inittab:
#
# /etc/inittab
#
# Runlevels:
# 0 Halt
# 1(S) Single-user
# 2 Not used
# 3 Multi-user
# 4 Not used
# 5 X11
# 6 Reboot
## Only one of the following two lines can be uncommented!
# Boot to console
id:3:initdefault:
# Boot to X11
#id:5:initdefault:
rc::sysinit:/etc/rc.sysinit
rs:S1:wait:/etc/rc.single
rm:2345:wait:/etc/rc.multi
rh:06:wait:/etc/rc.shutdown
su:S:wait:/sbin/sulogin -p
# -8 options fixes umlauts problem on login
c1:2345:respawn:/sbin/agetty -8 -s 38400 tty1 linux
c2:2345:respawn:/sbin/agetty -8 -s 38400 tty2 linux
c3:2345:respawn:/sbin/agetty -8 -s 38400 tty3 linux
c4:2345:respawn:/sbin/agetty -8 -s 38400 tty4 linux
c5:2345:respawn:/sbin/agetty -8 -s 38400 tty5 linux
c6:2345:respawn:/sbin/agetty -8 -s 38400 tty6 linux
# Serial Virtual Console for KVM and others VMs
#s0:2345:respawn:/sbin/agetty -8 -s 9600 ttyS0 linux
# Hypervisor Virtual Console for Xen and KVM
#h0:2345:respawn:/sbin/agetty -8 -s 38400 hvc0 linux
ca::ctrlaltdel:/sbin/shutdown -t3 -r now
# Example lines for starting a login manager
#x:5:respawn:/usr/bin/xdm -nodaemon
#x:5:respawn:/usr/sbin/gdm -nodaemon
#x:5:respawn:/usr/bin/kdm -nodaemon
x:5:respawn:/usr/bin/slim >/dev/null 2>&1
# End of file
Offline
Please use [ code ] tags when pasting to the boards.
Have you tried commenting the slim entry?
Offline
Sorry about forgetting the code tag. I commented out the slim line and still same result. It actually says "incorrect login" not "incorrect password". If I try logging in as root its the same result but it mentions "su:" in the error as well. Are there any other config files I could post that might give you a clue?
Thanks again
Offline
Could "id:3:initdefault" combined with "x:5:respawn:/usr/bin/slim >/dev/null 2>&1" the cause?
Offline
So I rolled back PAM one version and that seemed to fix everything. Strange that no one else seems to be reporting any problems though
Offline
Make sure your system if fully up-to-date
Offline
So I rolled back PAM one version and that seemed to fix everything. Strange that no one else seems to be reporting any problems though
The same problem: https://bbs.archlinux.org/viewtopic.php?id=141160
Offline