Hi again. Sorry about the silence - I didn't notice the reply

I now verified that right you were, there were multiple instances of kleopatra running (hung on importing my certificate). I killed them with -9, but Kleopatra won't still start: "Cannot find the D-Bus session server ... Pipe closed unexpectedly."

But if I look at the Konqueror's messages - doesn't the message Solid::Backends::Hal::HalManager::findDeviceByDeviceInterface(const Solid::DeviceInterface::Type&) error: "org.freedesktop.DBus.Error.Disconnected" mean that Hal fails to communicate with D-Bus (as does Kleopatra)? So maybe there still is smth wrong with my D-Bus?

The Konqueror issue, according to the QDBusError class documentation from Qt Labs ( Trolltech ) means

The call/process/message was sent after QDBusConnection disconnected (org.freedesktop.DBus.Error.Disconnected)

This is a bug, and if you are not running trunk I would file a bug with your distribution so they can fix their packages. the message emitted by Konqueror has nothing to do with HAL, apart from the fact that was who Konqueror was trying to communicate with.

Try running Kleopatra like this as well: dbus-launch kleopatra.

I've now upgraded my KDE to 4.1.3, but anything hasn't changed in this matter.

I made a bug report for the Konqueror issue: https://bugs.kde.org/show_bug.cgi?id=175108

Kleopatra doesn't start while executing it with dbus-launch either. Well, I think I'll just not use my Korganizer4 if I can't stop it prompting the certificate question all the time

BTW, there's a way to get root-certificates into KDE system by hand: http://bugs.kde.org/show_bug.cgi?id=162485#c26. So no more prompts and I can use my Korganizer

Glad to hear you managed to find a work around for your problem. If this problems is indeed solved, could you please add [SOLVED] to the beginning of the subject? Thanks.

Well.. the problem itself is not solved.. I just managed to find a workaround to my original goal, but the topic ain't actually about that..

Hello. I just got that error message, "KUniqueApplication: Cannot find the D-Bus session server", when I tried to start up muon-updater as root:

root@lucy:/home/terry/Documents# muon-updater
unnamed app(6660): KUniqueApplication: Cannot find the D-Bus session server: "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."

unnamed app(6658): KUniqueApplication: Pipe closed unexpectedly.


When I tried it under my own user account, it worked.
Just a suggestion.
Have a good day.

When trying to run graphical applications (like the Muon Updater) as another user, it is crucial that you change user using "su -" to ensure your environment is setup properly. In particular, when switching to root, if I use "su -" then I can start graphical applications without a problem.