Hi.
I've been a kde fan for more than 2 years. Recently I've discovered wmii window manager, liked it very much and decided to use as wm in kde. However, seamless wmii/plasma integration is not feasible, so I decided instead to enrich wmii session with kde features.

Almost all features, I'd like to use are provided by kded4 daemon.
For example to allow kde to manage my keyboard I do

Code: Select all

$ kded4
$ qdbus org.kde.kded /kded loadModule keyboard


The issue with this approach, is that kded4 won't start correctly for the first time. It prints a series of messages to stdout and hangs

Code: Select all

QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.

Outcome is 4 processes of kded4 running, however none of them responds to dbus calls.
Killing all of the kded4 and running it again solves this problem (the same message as above is printed, though).

On the other hand, any attempt to run systemsettings to configure something results in kded4 being started implicitly and behaving correctly. Thus, I know, that correct startup is possible.

So my questions are

• What are the prerequisites for correct kded4 startup?
• What would be the best way to run kded4 outside of kde session?

Thanks in advance for any help.

So, I finally managed things to work.

I have no idea, what I've done, but this worked for me

Systemd units are available on github
https://github.com/edio/systemd-kdemodules

As others in the community may find these *.unit files interesting, you may want to inform kde-devel@kde.org of them.