Michael Nottebrock wrote: > othermark schrieb: >> Michael Nottebrock wrote: >> >> >>> othermark schrieb: >>> >>>> Hi, >>>> >>>> I get this after the 345 upgrade when visiting secure, password >>>> protected sites: >>>> >>>> kio_http_debug: WARNING: (11517) Can't communicate with >>>> kded_kcookiejar! kio (kioslave): WARNING: Can't communicate with >>>> kded_kpasswdserver! kio_http_debug: WARNING: (11515) Can't communicate >>>> with kded_kcookiejar! kio (kioslave): WARNING: Can't communicate with >>>> kded_kpasswdserver! >>>> >>>> >>> Are you running 7-CURRENT? >>> >>> >>> Cheers, >>> >> >> Yes. FreeBSD 7.0-CURRENT #20: Thu Aug 31 07. >> > You are probably seeing fallout from the recent openssl upgrade in > 7-CURRENT and resulting mixed linkage, see > http://lists.freebsd.org/pipermail/freebsd-current/2006-September/065944.html > and subsequent replies. > > You might have to go through your filesystem, delete old versions of > libssl and libcrypto in /lib (the current versions are libcrypto.so.5 > and libssl.so.5), deinstall any openssl ports you have installed and > then recompile any ports that link to openssl (sysutils/libchk and > pkg_which from sysutils/portupgrade come in handy for determining those). >
Actually the problem seems to be very simple. The 'kded' process is not running at all. Either it's exiting early or not being properly started by startkde. Starting kded manually fixes the above problem. -- othermark atkin901 at nospam dot yahoo dot com (!wired)?(coffee++):(wired); _______________________________________________ kde-freebsd mailing list [email protected] http://kf.liquidneon.com/mailman/listinfo/kde-freebsd
