Hello all! Since nobody in the world knows how to diagnose kde-apps (judging by quantity of answers on my post for week), I've made some tests during last week trying to solve thos problem.
I've checked: in /etc/rc.conf i /etc/hosts in my system everything is OK, resolving works, firewall_type="OPEN", ping `hostname` work, ping localhost works, removing .kde directories doesn't help. How I've tryed to "catch" the problem. The first thing ossurs: gdb konsole run In my case this method 100% rebooting system in 80 seconds (the same mysterious network wait). On konsole appears this message: -------------------- [EMAIL PROTECTED]:~> gdb konsole GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"...(no debugging symbols found)... (gdb) run Starting program: /usr/local/bin/konsole (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...warning: Unable to get location for thread creation breakpoint: generic error [New LWP 100082] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New Thread 0x50c000 (LWP 100082)] (no debugging symbols found)...(no debugging symbols found)...kbuildsycoca running... -------------------- Then after 80 seconds: [New Thread 0x50c400 (LWP 100128)] and system reboots. Easy and efficiently, isn't it? The most interesting that there's no hether any intelligible messages on console nor logs. It's like kde ignorrs file's presence or options in it ~/.kde/share/config/kdebugrc I've inserted in this file options like this: InfoOutput=0 InfoFilename=~/kde_debug.log KDE-guru, hackers and just good people, is it really everything in a sad state, and old like kde itself problem "KDE slow startup" is blivet? -- WBR Android Andrew [:] _______________________________________________ kde-freebsd mailing list [email protected] http://freebsd.kde.org/mailman/listinfo/kde-freebsd
