topic Re: RHEL4.1 cannot login via gui (gnome) console. in Operating System - Linux

RHEL4.1 cannot login via gui (gnome) console.

Robert Walker_8 — Thu, 28 Jul 2005 00:53:40 GMT

Hi,

I dont know how Ive dun it but I can no longer get in via gnome console! root, std users anything just starts the session up and then bang we are back at the login prompt (even failsafe!).

I have looked at PAM and turned off SELinux. Logins via console without gui (init 3) work ok and the gui comes up with startx.

/var/log has PAM_UNIX saying

Jul 28 15:35:01 fred crond(pam_unix)[3690]: session opened for user root by (uid=0)
Jul 28 15:35:01 fred crond(pam_unix)[3690]: session closed for user root

Nothing very informative even with pam_unix in debug mode.

I do notice that I get errors for:
mtrr: your CPUs had inconsistent fixed MTRR settings
mtrr: probably your BIOS does not setup all CPUs.
mtrr: corrected configuration.

This is system is a proliant DL380 G4 and ran RHEL V3.4 without problems (starting to worry about V4 Update 1 as it appears somewhat different to V3 - ie audit missing etc).

I am also getting an error regarding /dev/cpu/microcode not being found by the S00microcode_ctl startup routine - it appears that V4 doesnt have this either?

Robert.

Re: RHEL4.1 cannot login via gui (gnome) console.

Martin Brachtl — Thu, 28 Jul 2005 04:26:43 GMT

check the disk usage, is'nt the root filesystem full, or something like that?

Re: RHEL4.1 cannot login via gui (gnome) console.

Ivan Ferreira — Thu, 28 Jul 2005 07:58:56 GMT

After verifying the disk space, try moving/renaming xinit files in the home directory, like .xinitrc, .xserverrc, .Xclients.

Re: RHEL4.1 cannot login via gui (gnome) console.

Steven E. Protter — Thu, 28 Jul 2005 09:03:51 GMT

env | grep DISPLAY

if DISPLAY is being redirected that can caus the problem.

I do not believe the microcode error could cause this problem.

I do believe that inadequate space in the HOME directory or /var could also trigger the problem.

SEP

Re: RHEL4.1 cannot login via gui (gnome) console.

Robert Walker_8 — Thu, 28 Jul 2005 18:23:18 GMT

SEP,

Disk spaces wasnt the issue - should have mentioned that in the first instance, nor are there any diskquotering on.

However my problem has been solved, thanks! - you were close on the mark, it was infact me setting the REMOTEHOST and DISPLAY variables in PAM_ENV. It look like a good idea at the time, have tested and either one causes no real problems but both presents a blank blue screen and then you are logged out. Will keep the DISPLAY variable as this saves some typing.

Thanks again to all,

Robert.