Bug 48532 – Cannot contact kded

• Product: Gentoo Linux
• Status: RESOLVED WORKSFORME

[Description Nicolas Laplante 2004-04-20 21:37:04 UTC]

kded is used by various services across KDE. 

I just upgraded from kde-3.2.1 to kde-3.2.2 (well, the packages which are affected by this upgrade: kdelibs, kdebase, kdenetwork, kdepim, kdeutils, arts).

I deleted ~/.kde*.

I started the new kde and all services needing kded don't work. The device:/ IO-slave isn't usable. There is no Basic authentication in Konqueror (thus, I can't use the CUPS local web interface), I can't edit the K menu entries, among others I don't recall.

When I look at the console from where I started X, I get _lots_ of messages in the form:

kio_http_debug: WARNING! (6297) Can't communicate with kded_kpasswdserver

Various programs trigger this, Konqueror being the most obvious.

I tried to start kded manually, but it died as soon as a client application wanted to communicate with it.

What's up with that?

Reproducible: Always
Steps to Reproduce:
1. Start Konqueror
2. Go to http://localhost:631 (if you run Cups)
3. Try to use administrative features (to no avail, no http-basic authentication dialog comes up)

-- or --

1. Start KMenuEdit
2. Edit/add/delete entries
3. Save & exit: the menu isn't updated
Actual Results:  
Can't use http-basic authentication
Can't update KMenu

Expected Results:  
A dialog asking for username/passwd would have come up;
The KMenu would have been updated

Don't know if it matters, but I compiled the new KDE with xorg-x11's X headers,
not XFree's.

[Comment 1 Caleb Tennis (RETIRED) 2004-04-26 18:57:55 UTC]

try re-emerging kdelibs, and see if that fixes it.

[Comment 2 Nicolas Laplante 2004-05-17 14:49:06 UTC]

I re-emerged my whole system due to a drive failure. I used gcc-3.4.0 for all the packages, and now KDE 3.2.2 works great!!!

:D