> I'm just about out of ideas. Are you using NVIDIA's driver? > What happens when you kldunload nvidia and try it after rebooting? No, I am using Radeon. The following info was excerpted from Windows7 on the other partition/slice.
Display: SME1920 Screen: 1360*768 Chip Type: ATI display adapter 0x9498 DAC Type: Internal DAC (400MHz) Adapter Str:ATI Radeon HD 4600 Series Bios Info: 113-AC08501-102-MI Total Mem: 1791MB Video Mem: 1024MB Shared Mem: 767MB Refresh: 60Hz root@bsdhost:~# kldunload nvidia kldunload: can't find file nvidia > > gua@bsdhost:~% kdeinit4 --no-fork --no-kded > > Connecting to deprecated signal > > QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) > > 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. Thank you. -- Gua Chung Lim _______________________________________________ kde-freebsd mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
