Hi,

I have a problem which surfaced a while back. I was hoping it would go away when I got the latest update to my distro, Slackware 14.2, but the problem persists. The error occurs in /usr/bin/startkde so that's why I think it's a KDE problem. However, I have a work-around which makes me think it's a boot issue. Here goes.

When I start up my machine to run level 4 (ie with KDE desktop) then I get the following message: "Could not start D-Bus. Can you call qdbus?" The message comes from /usr/bin/startkde where there is also a comment: # D-Bus autolaunch is broken. THAT makes me think it is KDE.

On the other hand, if I come up to run-level 3 (ie no desktop), then just log in and run startx it all works. The run-level 3 sequence is different than the run-level 4 sequence, that being what makes me think its a boot issue.

This did not used to happen. Slackware 14.1 was very happy for a while and then startup sequence started failing with that message. Any help would be appreciated.

Add qdbus to startup scripts and see if it works. In Debian, which uses plain sysvinit, runleves differ by /etc/rcX.d (where X is your runlevel) symlinks to /etc/init.d. In Slackware it's done by editing /etc/rc.d/rcX, I suppose. If in doubt, compare /etc/rc.d/rc3 and /etc/rc.d/rc4 or post them here.

Hope this helps and I am not plain wrong about Slackware init

I have the same problem, after the last kernel update I rebooted my machine and kde refused to start after loging in (kdm worked fine)

After a brief investigation, the error came from startkde trying to launch qdbus from "$(kde4-config --qt-binaries)/qdbus".

Somehow kde4-config --qt-binaries returns /usr/bin/bin which does not exist. In fact all the --qt-* paths returned by kde4-config are prefixed with /usr/bin.

I created /usr/bin/bin and symlinked qdbus in there which fixed the problem and got me going but I wonder where the problem comes from.

For a while my second computer (at work) using the same config could start kde without issues, but this morning after restarting X following an update of the nvidia driver, it did the same.

I tried looking at the slackbuilds from the kde sources but cannot find an obvious cause nor how to fix this.

What puzzles me is that this package (kdelibs I presume since it contains kde4-config) has not been updated for a long time, and my systems worked fine before that, and looking as startkde script it has behaved the same way after several reboots.

Btw it might be a good idea to move this thread to the Slackware forum.

I had the same problem, because I installed a package that erroneously included /usr/bin/qt.conf . This file changes the output of kde4-config --qt-binaries , which in my case not only caused kde not to start, but also (after manually editing startkde to let kde start) akonadi to fail. Everything started working again after I removed /usr/bin/qt.conf .