Cannot get into KDE from KDM login manager as regular user.
Hi there,
I've been running PCLOS2007 for almost a year now with absolutely minimal problems. Then totally out of the blue I tried logging into my PCLOS2007 box at the KDM login manager and was stuck at the tail end of splash screen sequence. The "pointer" is present though and I can move it about as normal with the mouse. When I reset the server using ctrl-alt-backspace I briefly saw my desktop and all its icons for a split second before going back into the KDM Login manager. I can login as ROOT with no problems. So what I done was to login as regular user again ( user zod) and when I reached the "freeze stage" I opened up a regular console using ctrl-alt-F2, logged in as root and went into the /home/zod directory to have a look at the.xsession-errors file. Here is the output. Code:
s2u: cookie for :0 = 'af0994df4db06ca237ca0255b8a7e0db' Error: "/home/zod/.kde/socket-PCLOS2007" points to "/tmp/ksocket-zod" instead of "/home/zod/tmp/ksocket-zod is the problem. But the directory /home/zod/tmp is linked to /tmp so socket-PCLOS2007 when pointing to /tmp/ksocket-zod should also point to /home/zod/tmp/ksocket-zod should it not ? Are there some linkage problems here ? I've checked the permissions of the files and directories and the ones for root are identical to the ones for user zod. Like I said before I have no problems getting into KDE when user root. Any cures ? cheers, uncle |
Hi, you may need to refresh (check) the system links.
ldconfig and symlink come to mind. ldconfig... Code:
http://linux.maruhn.com/sec/ldconfig.html Code:
symlinks symlinks -csrv /(dir) use man (package-name) or info (package-name) in case the distribution that you use has modified it's purpose. Cheers, Glenn. |
All times are GMT -5. The time now is 01:28 AM. |