Login Problem

Just in case, check the filelib-security-pamloginuid.so . Also do "rpm -V pam".

So the graphical login works, while the standard non-graphical login does not?

Sounds like this is not related to the runlevels per se.

From a gdm session, run

$ ps -ef grep getty root 1737 1 0 2005 tty1 00:00:00sbin-mingetty tty1 root 1738 1 0 2005 tty2 00:00:00sbin-mingetty tty2 root 1739 1 0 2005 tty3 00:00:00sbin-mingetty tty3 root 1740 1 0 2005 tty4 00:00:00sbin-mingetty tty4 root 1741 1 0 2005 tty5 00:00:00sbin-mingetty tty5 root 1742 1 0 2005 tty6 00:00:00sbin-mingetty tty6 quique 13575 13530 0 17:33 pts-2 00:00:00 grep getty

$ sudo strace -p 1738 -f -otmp-getty.strace ## the tty2 pid Process 1738 attached - interrupt to quit

And while this hangs, ctrl-alt-f2, and attempt to log in. Switch back to Ctrl-Alt-F7, and hit Ctrl-C in the terminal window. Inspect the filetmp-getty.strace, e.g. with "less" or "vim".

The file is usually rather voluminous, and not very easy to read. However, search for the error message you see in the log. It will look like this:

13342 connect(0, {safamily=AFFILE, path="-dev-log"}, 16) = 0

(the key item is path="-dev-log", then the first item in the parenthesis, the number zero in this case is the file descriptor, and the subsequent "send" call uses the same file descriptor. The message contains the date, as you see. The message is not shown in full, but you should be able to identify it by the date.)

Then look in the lines above the error message, for lines ending like this:

lstat64("tty2", 0xbf96806c) = -1 ENOENT (No such file or directory)

i.e., use the search pattern ?=.*E .

This may reveal what the problem is.

-Enrique