Hi all,

My first time here.

I've installed Slackware64 14.2 on a newer AMD machine with the built-in video chip. Got the network going great, and everything patched.

X just will not start. The best clue I get is when I try to start up KDE:

"Could not start D-Bus. Can you call qdbus?" - in an X-style bubble window, and an "Okay" button.

I've never had problems with fresh slack installs like this.

Does anybody have an idea?

Thanks,
CJ

Welcome to the forum.

Have you changed /etc/inittab to start the X server? The line to edit looks like this -

On a new install it is set to 3, change it to 4.

If that is already done, we need more information to help.

From the command line, run the command as root 'lspci | grep VGA' without the quotes, and post the results.

Have a look at /var/log/Xorg.0.log with a text editor like nano.

Look for lines near the bottom of the log marked with EE . Copy and paste thoes lines here, and we can give you more advice.

Hope this helps.

I figured it out, it's a real forehead slapper.

I set inittab to 4, it made no difference. X would initially start with a user/pass, but after login, I'd get the same dbus message. So, changed it back to 3 just to get my bash back.

On a whim, I decided I'd try a grep for "dbus" from /etc...

find /etc -type f -exec grep -Hni 'dbus' {} \;

- and I got a hit on /etc/rc.d/rc.messagebus -

I marked it executable, restarted it, and now it works. :|

This seems like an odd case to me. I must have unmarked it when I was installing it somehow? I'm migrating off an old Core2 with an Nvidia GeForce, running 14.1, and /etc/rc.d/rc.messagebus is not executable. Works okay with nouveau. ???

Architecturally, the machine in question is an AMD "APU" built-in-VGA processor... something I've not built before, but I wouldn't think it would be a drastic change from my old 14.1 and Intel/Nvidia.

Old 14.1 machine
$ /sbin/lspci | grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation GF116 [GeForce GTX 550 Ti] (rev a1)

New 14.2 machine
$ /sbin/lspci | grep VGA
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R5 Graphics]

So, what exactly is rc.messagebus?

I seriously appreciate your input, thank you.

If you look at the file rc.messagebus, you will see these words:

And from Wikipedia, see this link.

https://en.wikipedia.org/wiki/Messag...ted_middleware

In short, this daemon allows communication between components of your system as it runs. Not usre how it got turned off though, its executable on all my systems.

Hope this helps, and glad you got things working again.

Hi Guys,
I'm having this problem (KDE4 not starting and the message "Could not start D-Bus. Can you call qdbus?" is displayed) in two machines that I run Slackware64 14.2.
On my systems, the /etc/rc.d/rc.messagebus script is marked as executable (this condition never changed).

Strangely, I can start a kde4 session from terminal if I run startx (no matters the runlevel I'm on - 1, 3 or 4), but not if I try to start it from KDM.
I didn't tried to use xdm yet (I'll give a try on it at home).

Someone have any idea about what can be happening?

Thanks in advance.

Update 20181001:
Using xdm the kde session starts fine.
This leads me to believe, by exclusion, that this is a problem related to kdm. But the question remains:
Someone have any idea about what can be happening?

Note: all alternatives were testes as normal user and as root too.

Update 20181002:
By using sddm instead of xdm the problem persists. So, kdm is not the guilty...

I'm very confused now!!