[kde-freebsd] Re: start kde fails after reboot

Raphael Kubo da Costa kubito at gmail.com
Sun Apr 17 19:19:03 CEST 2011


Gua Chung Lim <gua.chunglim at gmail.com> writes:

> In xterm (bare startx)...
>
> gua at bsdhost:~% kdeinit4
> Connecting to deprecated signal
> QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
> kded(1579)/kdeui (KIconLoader): Unable to find an appropriate lock to
> guard the shared cache.  This *should* be essentially impossible. :(
> kded(1579)/kdeui (KIconLoader): Unable to perform initial setup, this
> system probably does not really support process-shared pthreads or
> semaphores, even though it claims otherwise.
> kbuildsycoca4 running...
> kdeinit4: Fatal IO error: client killed
> kdeinit4: sending SIGHUP to children.
> klauncher: Exiting on signal 1
> kded4: Fatal IO error: client killed
> kdeinit4: sending SIGTERM to children.
> kdeinit4: Exit.

This is really weird.

How about `kdeinit4 --no-forok --no-kded'? Something right in the
beginning of KDE's startup process is crashing, so it'd be nice to be
able to run gdb on the first misbehaving application we see.


More information about the kde-freebsd mailing list