26.10.2012 Views

SUSE LINUX Documentation - Index of

SUSE LINUX Documentation - Index of

SUSE LINUX Documentation - Index of

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

2 Determine the directory server the machine relies on for authentication and make<br />

sure that it is up and running and properly communicating with the other machines.<br />

3 Determine that the user's username and password work on other machines to<br />

make sure that his authentication data exists and is properly distributed.<br />

4 See if another user can log in to the misbehaving machine.<br />

If another user can log in without difficulty or if root can log in, log in and<br />

examine the /var/log/messages file. Locate the time stamps that correspond<br />

to the login attempts and determine if PAM has produced any error messages.<br />

5 Try to log in from a console (using Ctrl + Alt + F1 ).<br />

If this is successful, the blame cannot be put on PAM or the directory server on<br />

which the user's home is hosted, because it is possible to authenticate this user<br />

on this machine. Try to locate any problems with the X Window System or the<br />

desktop (GNOME or KDE). For more information, refer to Section 9.4.3, “ Login<br />

Successful but GNOME Desktop Fails ” (page 230) and Section 9.4.4, “ Login<br />

Successful but KDE Desktop Fails” (page 230).<br />

6 If the user's home directory has been used with another Linux distribution, remove<br />

the Xauthority file in the user's home. Use a console login via Ctrl + Alt<br />

+ F1 and run rm .Xauthority as this user. This should eliminate X authentication<br />

problems for this user. Try a graphical login again.<br />

7 If graphical login still fails, do a console login with Ctrl + Alt + F1 . Try to<br />

start an X session on another display, the first one (:0) is already in use:<br />

startx -- :1<br />

This should bring up a graphical screen and your desktop. If it does not, check<br />

the log files <strong>of</strong> the X Window System (/var/log/Xorg.displaynumber<br />

.log) or the log file for your desktop applications (.xsession-errors in<br />

the user's home directory) for any irregularities.<br />

8 If the desktop could not start because <strong>of</strong> corrupt configuration files, proceed with<br />

Section 9.4.3, “ Login Successful but GNOME Desktop Fails ” (page 230) or<br />

Section 9.4.4, “ Login Successful but KDE Desktop Fails” (page 230).<br />

Common Problems and Their Solutions 229

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!