/usr/bin/startkde:
88 # Laurent kde2.2-30mdk scan-nsplugins
89 #if [ -x /usr/bin/nspluginscan ]; then
90 # /usr/bin/nspluginscan
91 #fi
Hummm. kde2.2-30 is about when it started. I comment out these lines
(as I've stated in several emails on this topic), and all works. This
addition to startkde is obviously not correct, or at least in the wrong
place. This is because nspluginscan starts dcopserver. It even says it
is starting it right in .xsession-errors. Then kdeinit dies due to
dcopserver already being started. Well, of course it's already started,
nspluginscan said that it started it, right before kdeinit tried to.
My guess is that on a really fast machine, dcopserver shuts down again
before kdeinit tries to restart it. Otherwise it would happen to
EVERYONE, because it happens EVERY TIME on my P2-233. No matter how
many .DCOP*, .MCOP* and /tmp/blah files I delete.
Lonnie
=========
kdecore (KLibLoader): WARNING:
library=/usr/lib/netscape/plugins/ShockwaveFlash.class:
file=/usr/lib/netscape/plugins/ShockwaveFlash.class:
/usr/lib/netscape/plugins/ShockwaveFlash.class: invalid ELF header
DCOPServer up and running. <<<<< FIRST START BY NSPLUGINSCAN
kdeinit: Shutting down running client.
kio (KLauncher): ERROR: KLauncher: KDEInit communication error Commiting
suicide
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 <<<< I'M SURE IT _IS_ RUNNING!
/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.
On Tue, 2001-09-25 at 23:55, Borsenkow Andrej wrote:
> On Tuesday 25 September 2001 12:36, you wrote:
> > It was already reported today and it happened to me @home. I started
KDE
> > via startx, up came splash screen, the last thing displayed were
these
> > KDE gears, then splash screen went away and there was nothing more.
In
> > ps I could see seberal kdeinit's, the last two (father and child)
> > waiting on read(5,...) and read(7,...) (from memory, sorry). There
were
> > noting useful in .xsession-errors just usual crap about DCOP server
> > already running, not ELF etc.
> >
> > BTW it took some time. I typed startx and went to make tea. As I
came
> > back I exactly saw splash screen disappearing.
> >
> > As usual, I ask myself why this should start to happen just before
> > release ...
> >
> > -andrej
>
> I don't know if you saw yesterdays mail, someone had the same proble
abd
> is
> really easy to fix.
>
> Just 'rm' .DCOPserver_whatever and
> .DCOPserver_whatever:0 Plus .MCOP-random-seed
>
> and try to login again... enjoy!
Pardon me, but
- it is no fix. Fix is when you know *why* it hangs
- I simply killed all kdeinit's, started again and it worked. So your
"easy fix" has nothing to do with it and is pure coincidence. That is
exactly what is irritating.
- are you going to explain it to every future Mandrake 8.1 user? :-)
-andrej
--
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
