Hi, > The error indicates that you don't have the console lock. Are there > other users logged in at the same time on other VTs? What are the > contents of /var/run/console.lock before you run 'startx'? There is only one user on the workstation (me) and I am root, too. /var/run/console.lock contains the user name, after I login on a tty: [root@hermes dumas]# cat /var/run/console.lock dumas > What are the contents of /etc/pam.d/login? The default as shipped > should include a call to pam_console to obtain the lock if possible: > session optional /lib/security/pam_console.so I think the lock is obtained. Permissions on a lot of files is allready taken by the user dumas (tty2, tty7, fd0, everything in console.perms). /etc/pam.d/login ................................................................... #%PAM-1.0 auth required /lib/security/pam_securetty.so auth required /lib/security/pam_stack.so service=system-auth auth required /lib/security/pam_nologin.so account required /lib/security/pam_stack.so service=system-auth password required /lib/security/pam_stack.so service=system-auth session required /lib/security/pam_stack.so service=system-auth session optional /lib/security/pam_console.so debug ................................................................... I added the debug. /etc/pam.d/system-auth ................................................................... #%PAM-1.0 # This file is auto-generated. # User changes will be destroyed the next time authconfig is run. auth required /lib/security/pam_env.so auth sufficient /lib/security/pam_unix.so likeauth nullok auth required /lib/security/pam_deny.so account required /lib/security/pam_unix.so password required /lib/security/pam_cracklib.so retry=3 type= password sufficient /lib/security/pam_unix.so nullok use_authtok md5 shadow password required /lib/security/pam_deny.so session required /lib/security/pam_limits.so session required /lib/security/pam_unix.so .................................................................. Pat
