Unable to log in user - This gets serious

[Truls Gulbrandsen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tony Dietrich wrote:
| On Tuesday 22 Feb 2005 20:58, Truls Gulbrandsen wrote:
|
|>Alexander Dalloz wrote:
|>| Am Di, den 22.02.2005 schrieb Truls Gulbrandsen um 21:32:
|>|>I have upgraded two of my systems, a TP30 and an IBM desktop, with the
|>|>most resent udates.  After upgrading I am unable to log in as user.  The
|>|>message I receive is: "GDM could not write to your authorization file.
|>|>This could mean that you are out of disk space or that your home
|>|>direcoty could not be opened for writing. In any case, it is not
|>|>possible to log in. Please contact your system administrator".
|>|>
|>|>I am able to log in as root.  I am quite sure that there is enough disk
|>|>space so the problem is probably something else, but what?  Any
|>|>suggestions that will assist.
|>|>
|>|>
|>|>Truls
|>|
|>| Any chance you changed the permissions or ownership of /tmp by accident?
|>|
|>| $ ls -ld /tmp
|>| drwxrwxrwt  31 root root 1688 22. Feb 20:29 /tmp
|>|
|>| This is "chmod 1777" and a must.
|>| Check too the permissions and ownership of your user's /home/<user>
|>| directory.
|>|
|>| Alexander
|>
|>I have only done a "yum update".  The permissions of /tmp is equal to
|>the above.
|>
|>Truls
|
|
| Try removing any sub-directory of /tmp that includes a user's name.
|
| Authorisation files are written to files in directories such as
| mcop-<loginname>, and in some cases updates corrupt the setup of these
| directories, by either changing the userID of the authorisation
process, or
| the method of writing the authorisation file.
|
| If that doesn't work, try checking the home directories of each user
for files
| under the .kde|.gnome|.whatever_window_manager_you_are_using directory
for
| authorisation files.  The rationale for this is the same as above, as
some
| authorisation files are stored in the user's directories in some
cases.  This
| route may have additional consequences though so YMMV, and the risk is
yours.
|
Hi again,
now I get worried.  I am still not able to log in with the established
user ids.  Also, I am unable to create and use new user ids - well i can
create but get the same errormessage.  The only one working is root.
Is this a weakness with this distribution or with Linux?  Am I at risk
(of course I am) that this will happen to pcs with FC3?  Now I don't
risk doing an upgrade and reboot of this "live" machine.

Regards,
Truls



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCHOnxickK29LSyG8RAkQfAKC6Z0PuyTVVxCIwcuk3yrpS+TjE8wCgi11H
6OTmzYQs29yzu/GQw+xc1ZM=
=vby9
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: trulsg.vcf
Type: text/x-vcard
Size: 111 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/fedora-list/attachments/20050223/6612d2f1/attachment-0001.vcf>