(From a fellow speakeasy.net user :)
Go to a virtual terminal, login as the user, look at
$HOME/.xsession-errors to see what is happening. My bet is you'll see
something like:
=========================
DCOP aborting (delayed) call from 'kded' to 'klauncher'
---------------------------------
It looks like dcopserver is already running. If you are sure
that it is not already running, remove
/home/67goat/.DCOPserver_pocket_:0
and start dcopserver again.
---------------------------------
KDE Daemon (kded) already running.
kbuildsycoca already running!
kdeinit: Fatal IO error: client killed
kdeinit: sending SIGHUP to children.
kdeinit: sending SIGTERM to children.
kdeinit: Exit.
=========================
If so, go to /usr/bin as root, edit the startkde script, and comment out
lines
89 #if [ -x /usr/bin/nspluginscan ]; then
90 # /usr/bin/nspluginscan
91 #fi
This keeps nspluginscan from starting dcopserver which causes kdeinit to
choke. That's to only way I've been able get KDE to run.
On Mon, 2001-09-24 at 20:01, Chuck Lalli wrote:
I just updated all my packages from RC1 to current cooker using Mandrake
Update, except the kernel which I did manually beforehand.
Now after a reboot, I cannot get KDE started. I boot to runlevel 5 with KDM,
all is fine. After logging in, the KDE splash screen comes up, and when the
Initializing Services icon is flashing, it stops progressing. After a while,
the splash screen goes away and I am left with a blue background, and nothing
else.
I tried startx from a runlevel 3 boot and merely got the blue background.
After killing X, I saw no error messages.
I can log into Gnome just fine.
I am not sure how else to diagnose this, any help is appreciated.
Chuck
--
Count on nothing, expect little, hope for everything
--
TTFN,
Lonnie Borntreger
------ ------ ------
Our mission is to authoritatively promote timely methods of
empowerment so that we may endeavor to collaboratively supply
inexpensive opportunities to exceed customer expectations
