This forum has been archived. All content is frozen. Please use KDE Discuss instead.

KDED not running - how do I activate it?

Tags: None
(comma "," separated)
von_shtupp
Registered Member
Posts
7
Karma
0
OS
I'm running Suse 11.1 with KDE 4.2.3 release 116

When I go on System Settings -> Service Manage I get an error message
unable to contact KDED


The Service Manager Window is greyed out telling me that all the KDED services are not running.

KDED Cookie Jar Module
KSSL Daemon Module
KDED Desktop Folder Notifier
KDED-module for screen Management
KDED Password Module
KDED Konqueror Preloader Module
Solid User Interface Server
KDED Global Shortcuts Server
Sound Policy Server
KDED Flavicon Module
Proxy Scout
KHotkeys
Network Status Daemon
PowerDevil
KDED Remote Base URL Notifier
KDE Write Daemon
KDE Time Zone Daemon
DNS-SD Services Watcher

Any ideas how I activate KDED? Thank you.
Reply With Quote
User avatar
Hans
Administrator
Posts
3304
Karma
24
OS
What do you get if you try to run kded4 from a terminal?


Problem solved? Please click on "Accept this answer" below the post with the best answer to mark your topic as solved.

10 things you might want to do in KDE | Open menu with Super key | Mouse shortcuts
von_shtupp
Registered Member
Posts
7
Karma
0
OS
Hans wrote:What do you get if you try to run kded4 from a terminal?


I get the following messages:

Invalid D-BUS member name 'idle-hint' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection
Invalid D-BUS member name 'is-local' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection
Invalid D-BUS member name 'x11-display-device' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection
Invalid D-BUS member name 'x11-display' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection
Invalid D-BUS member name 'display-device' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection
Invalid D-BUS member name 'remote-host-name' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection
Invalid D-BUS member name 'session-type' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection
Invalid D-BUS member name 'unix-user' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection
kded(4916): Communication problem with "kded" , it probably crashed.
Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." "

I don't know what they mean.

Last edited by von_shtupp on Sun May 10, 2009 9:12 am, edited 1 time in total.
von_shtupp
Registered Member
Posts
7
Karma
0
OS
PS: apart from kdelibs4 I have also kdelibs3 installed. Is that correct or could there be a conflict?
User avatar
RGB
Registered Member
Posts
346
Karma
0
OS
Are you sure you have the right packages installed? Sometimes, by using factory repos there is a possibility of regressions (packages installed from kde 4.1.3, for example). You may try setting a different priority for kde repo than the priority for "update" and then update your system (remember that a lower number means a higher priority).
I'm using kde 4.2.3 on openSUSE 11.1 from kde42 repo without a problem: kded4 is running and healthy.


RGB, proud to be a member of KDE forums since 2008-Nov.
And proud to be a kde user since 1.1.2
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
You may also want to remove KDE Daemon's configuration file:
Code: Select all
rm $(kde4-config --localprefix)/share/config/kdedrc


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
von_shtupp
Registered Member
Posts
7
Karma
0
OS
Thanks for your answers, but because I had a hard drive failure last night, I had to re-install my system on a different drive. This time I stuck with KDE 4.1.3 though and everything runs fine (so far).

I'm not sure if I'll upgrade to 4.2 anytime soon, but then again I'm dying to find out, if I have the same problem again or not ;-)

Are you sure you have the right packages installed? Sometimes, by using factory repos there is a possibility of regressions (packages installed from kde 4.1.3, for example). You may try setting a different priority for kde repo than the priority for "update" and then update your system (remember that a lower number means a higher priority).


I did at the time update all files and libraries containing KDE in their names to the factory repo and to the correct/latest version.

Last edited by von_shtupp on Mon May 11, 2009 8:09 am, edited 1 time in total.


Bookmarks



Who is online

Registered users: bancha, Bing [Bot], Evergrowing, Google [Bot], lockheed, mesutakcan, mickae, Sogou [Bot]