D-Bus errors on KDE-apps [Solved]

[Solmyr]

I get errors when trying to start kde-apps from the terminal.
As root they fail to start at all and as a regular user they start with the following error

User starting k3b

Code: Select all

emanuel@Deepthought ~ $ k3b
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
KGlobal::locale::Warning your global KLocale is being recreated with a valid main component instead of a fake component, this usually means you tried to call i18n related functions before your main component was created. You should not do that since it most likely will not work
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
emanuel@Deepthought ~ $ K3bQProcess::QProcess(0x0)
K3bQProcess::QProcess(0x0)
k3b(10445)/kdeui (kdelibs): Attempt to use QAction "view_projects" with KXMLGUIFactory!
k3b(10445)/kdeui (kdelibs): Attempt to use QAction "view_dir_tree" with KXMLGUIFactory!
k3b(10445)/kdeui (kdelibs): Attempt to use QAction "view_contents" with KXMLGUIFactory!
k3b(10445)/kdeui (kdelibs): Attempt to use QAction "location_bar" with KXMLGUIFactory!
QCoreApplication::postEvent: Unexpected null receiver


root starting k3b (fails to start)

Code: Select all

QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
unnamed app(10613): 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(10612): KUniqueApplication: Pipe closed unexpectedly.


root starting kwrite (fails)

Code: Select all

kwrite(10329)/kdeui (kdelibs): Session bus not found
To circumvent this problem try the following command (with Linux and bash)
export $(dbus-launch)
KCrash: Application 'kwrite' crashing...
KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit
sock_file=/root/.kde4/socket-Deepthought/kdeinit4__0
Warning: connect() failed: : Filen eller katalogen finns inte
KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi directly
drkonqi(10330)/kdeui (kdelibs): Session bus not found
To circumvent this problem try the following command (with Linux and bash)
export $(dbus-launch)


Starting kwrite as a user works without errors

If i try to run

Code: Select all

export $(dbus-launch)

and then start kwrite as root I get this info when running (starting then closing) the app.

Code: Select all

Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
kbuildsycoca4 running...
kbuildsycoca4(10669) KBuildSycoca::checkTimestamps: checking file timestamps
kbuildsycoca4(10669) KBuildSycoca::checkTimestamps: timestamps check ok
kbuildsycoca4(10669) kdemain: Emitting notifyDatabaseChanged ()


[joost]

This often happens after a major KDE update.
You are always adviced to reboot your system after such update, did you do that yet?

[Solmyr]

Yes several times.

[Solmyr]

I downloaded the daily build of sabayon, a few days ago. Then I added the sabayon-weekly repositories and sabayon downgraded kde to 4.8.4 (or something) then upgraded again yesterday to 4.9. But I think that this problem existed even before the downgrade (with a fresh install).

[Fitzcarraldo]

I experience exactly the same behaviour with KDE 4.9 in Gentoo. It's a known KDE bug in all distributions: see KDE Bug Report No. 297020. You should not need to worry about it, it should not affect functionality adversely. I believe it is scheduled to be fixed in KDE Frameworks 5 sometime in the future. As far as starting the apps as root user, you should not be starting apps as root user anyway. If you want to start apps with root user priviledges, use kdesu under your own user account, and you'll be prompted to enter the root user's password. For example:

Code: Select all

$ kdesu dolphin

[Solmyr]

Thanks for the reply and the tip. =)

I'll mark this as solved for now.