Thank you for answer! > Experience shows that your problem is very likely not actually > located in KDE - slow startup issues are just a symptom of a misconfiguration > elsewhere (usually network related).
Yes, I agree with you. It is not only KDE problem, other tested desktop environments (except twm and windowmaker) have problems with startup. Because of lack of experience I can't diagnose the place where misconfiguration appears. I know, KDE is set of many interacting services and programms, but I have no ideas about how each of them works or interacts with OS. > Your system rebooting when running konsole in gdb is interesting, > but, by principle, a FreeBSD bug - or a symptom of hardware failure. It is possible, but unlikely, I've thoroghly selected my hardware and tested it with other operating systems. > Actually I do have one idea of something else to try: Set KDE_NO_IPV6=1 > in .xsession/.xinitrc to disable KDE's IPv6 support. If that helps, it's > an indication you have some misconfiguration on your system related > to IPv6. Thanks for idea, I've checked it, but it does not take any effect. I tested some things ralated with IPv6 support: options ipv6_enable="NO" in /etc/rc.conf, kernel with and without IPv6 support - all with the same result. Could someone explane me KDE startup sequence, so I could understand what for example means this message: DCOPClient::attachInternal. Attach failed Could not open network socket --- WBR Android Andrew [:] _______________________________________________ kde-freebsd mailing list [email protected] http://freebsd.kde.org/mailman/listinfo/kde-freebsd
