I think I found the solution (maybe not all of the problem, but enough).
nspluginscan is started before KDE is running, but is a KDE application,
therefore it starts a dcopserver process (among others).
Just after that, startkde deletes the file $HOME/.ICEauthority, which
really should not happen.
The next KDE program that is started causes the fork loop. I can
reproduce the bug by running
dcopserver
rm ~/.ICEauthority
kdeinit
while removing the 'rm $HOME/.ICEauthority' line from /usr/bin/startkde
solves the startup problem.
AFAICS, it should not be necessary to delete .ICEauthority in
KDE 2.2, because dcopserver automatically does this on startup.
Arnd <><
On Mon, 14 May 2001, Udo Weber wrote:
> Daouda LO wrote:
>
> > Shalrath <[EMAIL PROTECTED]> writes:
> >
> > > partially anyways. In the latest cooker, kdebase-2.2-0.alpha1.5mdk, and
> > > gnome-core-1.4.0.3-1mdk, both environments exhibit problems on startup.
> > >
> > > KDE gets caught in a loop where it starts a new kdeinit process about once
> > > per second.
> >
> > Do you have this issues from a fresh install of cooker or from upgraded 8.0?
> > Could you give me clearer way to reproduce as i have kdebase-nsplugins installed
> > and can't run into this problems :-(
>
> I have 2 different system-types first one is a long-time updated cooker-system and
> the other one is a fresh installed MDK 8.0.
> I can reproduce this problem on both systems each time.
> I don't tryed this with a fresh installed cooker - it's too much time (and not
> efficent) for only this package (kdebase-nsplugin).
> I hope this will help - I think there is a bug in a installscript probably ?
>
