Problem starting ordinary user in KDE

Hi
I have a problem starting an ordinary user
using KDE. The system has worked fine in the past,
but now halts with a grey screen after typing the
password in KDM and hitting enter. I have tried
creating another new user and letting KDE create its
new files. But the result is the same - the system
halts.

Fatal server error:
Server is already active for display 0
If this server is no longer running, remove /tmp/.X0-lock
and start again.

When reporting a problem related to a server crash, please send
the full server output, not just the last messages.
This can be found in the log file "/var/log/XFree86.".
Please report problems to xfree86@xfree86.org.

You should at least get a gray patterned background, and a large cross cursor (probably a menu on the mouse buttons too). You can leave this server with Ctrl+Alt+Backspace.
Please post the results of X.log

_XSERVTransSocketOpen: socket() failed for tcp
_XSERVTransSocketOpenCOTSServer: Unable to open socket for tcp
_XSERVTransOpen: transport open failed for tcp/cliffhangers:20
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for tcp

ok, as I read the log, X starts fine: you see a gray patterned background and you have a cross cursor and you have been able to exit X with Ctrl+Alt+Backspace.
This proofes that the problem is not the server itself, just its runtime configuration (xinitrc, xserverrc), or most likely the configuration of KDE (panel, desktop, windo manager).

We can now track down the problem, try following:

/usr/X11R6/bin/xinit /usr/X11R6/bin/xterm -- 2:0 -auth

(please adapt paths)
You should get a X server with cross cursor and a 80x24 xterm window (but no window frames etc.).
In the xterm window try to start (on of following):

mwm
fvwm
twm
kde # will produce a lot of messages/warnings/errors

You can exit this application with Ctrl-C, then exit the sesseion with Ctrl-D (or the command exit) in xterm.

If at least mwm or fvwm works, then check if kde works. If kde does not start please post the messages.

0

cliffhanger121599Author Commented: 2002-07-13

<<ok, as I read the log, X starts fine: you see a gray patterned background and you have a cross cursor and you have been able to exit X with Ctrl+Alt+Backspace.>>

I'm able to exit with Ctrl+Alt+Backspace but only after four or five attempts - reason?

<<You should get a X server with cross cursor and a 80x24 xterm window (but no window frames etc.).>>

PLease try from the console window:
which kde
if it does not return a full path to kde, please search for kde as follows:
find /usr -type f -name kde -ls
find /opt -type f -name kde -ls
and post the results.

>> do you have a cache file?
>>Can you be more specific, within KDE or what?
dammn, I meant core, sorry
kdeinit terminated abnormaly, sometimes it will produce a file named core for further debuggimg purpose.
Traditionally this file was named core, so try:
find . -name core -ls
unfortunatelly, Linux developers sometimes decide to use other names:
find . -name \*core -ls
find . -name core\* -ls

This file is only created if the shell allows it, check with:
ulimit -a|grep -i core # for ash,bash,ksh,sh
or:
limiz|grep -i core # for csh, tcsh
(value must not be 0)

Further developments. Within a console window in xterm I can now boot into a KDE desktop using "startkde" sometimes as mentioned, but more than this if I save the KDE desktop by logging out, it's possible to boot in everytime after that, but NOT from KDM. If I Ctrl-Alt-Backspace and start a new xterm session it then becomes pot luck whether I boot into KDE.

Back shortly with the other requests.

MAC

0

cliffhanger121599Author Commented: 2002-07-14

>Why is kdeinit then complaining? Can you please post:
> grep null /opt/kde/bin/startkde

All in all it will be hard to identify the problem now. Posting all the involved scripts is not a good solution.
Kan you please edit (temporarily) startkde, add a
set -x
at the beginning (second line or so), then start it
startkde > kde.log 2>&1
check the log file (you'll get a lot of line with + as very first character), post +/-5 arround the line producing the "permission denied" error, and +/-5 lines around the kdeinit call.

Silly question (not really a Linux solution):
did you ever try to reinstall kde?
something in your system is corrupted ...

LD_LIBRARY_PATH=/opt/kde/lib
kdeinit: Launched DCOPServer, pid = 679 result = 0
---------------------------------
It looks like dcopserver is already running. If you are sure
that it is not already running, remove /home/cliffy/.DCOPserver_cliffhangers_:0
and start dcopserver again.
---------------------------------

LD_LIBRARY_PATH=/opt/kde/lib
kdeinit: Shutting down running client.
---------------------------------
It looks like dcopserver is already running. If you are sure
that it is not already running, remove /home/cliffy/.DCOPserver_cliffhangers_:0
and start dcopserver again.
---------------------------------