Gua Chung Lim <[email protected]> writes: >> So this time it ran fine and did not crash? Interesting. >> How about `kdeinit4 --no-fork'? > gua@bsdhost:~% kdeinit4 --no-fork > Connecting to deprecated signal > QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) > kded(1543)/kdeui (KIconLoader): Unable to find an appropriate lock to > guard the shared cache. This *should* be essentially impossible. :( > kded(1543)/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 > kded4: Fatal IO error: client killed > kdeinit4: sending SIGHUP to children. > klauncher: Exiting on signal 1 > kdeinit4: sending SIGTERM to children. > kdeinit4: Exit. > > I don't actually know what kdeinit4 does. > Both options render the rest of xterm unresponsive. > I have to press <Alt><Ctrl><F?>. > Then press <Ctrl>C to stop xterm.
What an interesting problem :) So Xorg doesn't really crash, as xterm is still up? If you don't have debug symbols for kdelibs, can you install them and then run `gdb --args kdeinit4 --no-fork', then type 'run' and get a backtrace with 'bt' when it crashes? _______________________________________________ kde-freebsd mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
