CentOS - Oct 2010 - GDM could not write to you authorization file ... Please contact your system adminstrator

I am the system administrator.

I have a system that was built with a default install which resulted
in everything in a single file system except for /boot

wrote some scripts to split out: /home, /usr, /var, /opt, and /tmp to
separate file systems/logical volumes it looks like it ought to work,

There's plenty of space in all the filesystems and I can log via ssh
and have write access in my home directory.  Logging in via ssh
did result in a new .Xauthority file being automatically created,
but that did not help.

Googleing around I saw a thread where the user was actually out
of disk space, but before that was established somebody asked
if /home was on a different filesystem from /, but what to do in that
case never came up.

Another google thread suggested looking in .xsession-errors,
but I don't have one.

I've found irrelevant ubuntu suggestions regarding ubuntu only
packages.

Still googleing

-- 
Drew Einhorn

"You can see a lot by just looking."
? --? Yogi Berra

what happens with selinux disabled?

-- 
When one door is closed, another is open.
(Robert Nesta Marley)
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.centos.org/pipermail/centos/attachments/20101006/69c19a2c/attachment-0002.html>

There are no selinux related log messages.
Tried disabling it anyway.  Didn't help.

On Tue, Oct 5, 2010 at 11:25 PM, cornel panceac <cpanceac at gmail.com>
wrote:
> what happens with selinux disabled?
>
> --
> When one door is closed, another is open.
> (Robert Nesta Marley)
>
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
>


-- 
Drew Einhorn

"You can see a lot by just looking."
? --? Yogi Berra

This error sounds familiar.  If it is the same problem I've had a couple
of times, every time it happens, I forget what it was I did the last time to
fix it.  :-(  After I remember, it seems almost obvious.
     Assuming you've got the same problem, you need to log into the account
remotely, with out a GUI interface, or as another user.  See if you have a
file ~/.ICEauthority.  If it is there, delete it and then try logging in
again.  I think that is the right file for the problem I've had.  I just
remember that some file got corrupted and I had to delete it before GUI logins
would work.  I hope this helps.  Good luck.

-- 

  Brent L. Bates (UNIX Sys. Admin.)
  M.S. 912				Phone:(757) 865-1400, x204
  NASA Langley Research Center	  	  FAX:(757) 865-8177
  Hampton, Virginia  23681-0001
  Email: B.L.BATES at larc.nasa.gov	http://www.vigyan.com/~blbates/