Operation Manual

his password correctly, use the YaST User Managementmodule to change
the user's password. Pay attentionto the[ Caps Lock] key and unlock it, if
necessary.
2
Login as
root
and check
/var/log/messages
for error messages of the login
process and of PAM.
3 Try to log in from a console(using[ Ctrl] +[ Alt] +[ F1]). If this is successful,
the blame cannot be put on PAM, becauseit is possible to authenticatethis
useron this machine.Try to locateany problemswith the X Window System
or the desktop(GNOME or KDE).For more information, refer to Section“Login
Successfulbut GNOME DesktopFails” (page 98) and Section “Login Successful
but KDE Desktop Fails” (page 99).
4 If the user'shome directoryhas beenusedwith anotherLinux distribution,
remove the
Xauthority
file in the user'shome.Use a consolelogin via[
Ctrl
]
+[ Alt] +[ F1] and run
rm .Xauthority
as this user. This should eliminateX
authenticationproblems for this user. Try graphical login again.
5 If graphicallogin still fails,do a consolelogin with[ Ctrl] +[ Alt] +[ F1]. Try to
start an X sessionon another display—thefirst one(
:0
) is alreadyin use:
startx -- :1
This should bring up a graphicalscreen and your desktop.If it does not, check
the log files of the X Window System(
/var/log/Xorg. displaynumber.log
)or
the log file for your desktopapplications(
.xsession-errors
in the user'shome
directory) for any irregularities.
6 If the desktopcould not startbecauseof corrupt configurationfiles,proceed
with Section “Login Successfulbut GNOME DesktopFails” (page 98) or Section
“Login Successfulbut KDE Desktop Fails” (page 99).
The following are some common reasons why networkauthenticationfor a particular
user may fail on a specificmachine:
• The usermay haveentered thewrong password.
• The username exists in the machine's local authentication files and is also pro-
vided by a network authenticationsystem, causing conflicts.
• The home directory exists but is corrupt or unavailable. Perhaps it is write pro-
tected or is on a server that is inaccessibleat the moment.
• The userdoesnot havepermissionto log in to thatparticularhostin theauthen-
tication system.
• The machinehas changedhostnames,for whateverreason,and the userdoes
not have permissionto log in to that host.
96 Start-Up