[SOLVED] Various D-bus errors with KDE

briancs · 2012-07-13 22:59:45

I've just put on a fresh Arch install with btrfs and kde, and I am running into several errors which all seem to relate back to Dbus.

The first thing I noticed was that Ubuntu One filesync wasn't working -- it left me with a freedesktop.org error, among several other things -- which led me to attempt to change my network manager from Network & Wicd to networkmanager and the kde interface to networkmanager. However, this never worked - my applet gave an error message to the effect "Network Manager is not running" when in fact it was, and everything seemed to break along with that. So I went back to wicd, but at startup it can't figure out how to run properly, so I had to throw together a script which removes the pid and starts the daemon and client again (I have to run this script manually after startup and after wicd fails the first time.) Since then I have had countless applications fail on me, exiting with Dbus errors. Eventually this led me to conclude that Dbus was somehow at the center of it all (I recognize that this may not be the case, after all Dbus is pretty ubiquitous in the system and pretty much everything will show a Dbus error at some point); I did a reinstall of Dbus: just pacman -S dbus then let it reinstall, though there might be other steps needed to clean it out.

Anyone have any clues as to what might be going on? I'm not particularly discouraged at this point, but I'm at the end of my knowledge so if anyone with more knowhow than me, or anyone that's been in a similar situation, could help, that would be awesome.

Last edited by briancs (2012-07-14 14:17:39)

Trilby · 2012-07-13 23:03:46

I suspect that either a) dbus isn't in your daemons array or b) you don't have a dbus-session running for your user's x session.

But no one will be able to offer anything beyond (un)educated guesses unless you show us the actual error messages.

briancs · 2012-07-13 23:38:54

I do have Dbus in rc.conf, its the first daemon.

And I'm guessing dbus is running, because things are actually running (things which would require dbus).

As for logs, when I get back to my computer I will try to compile a list of them and post them.

Trilby · 2012-07-13 23:48:01

The dbus daemon can be running, but you may not have a dbus-session for your user. If you look in (h)top you should see two "dbus-daemon" processes, one owned by dbus and one by your user, then you should also see a third process called "dbus-launch" owned by your user. The entry in rc.conf only starts one of these three. The others are generally supposed to be started with your window manager.

briancs · 2012-07-14 02:44:20

Hmm.. I definitely see only one, and starting the second session dbus-daemon and dbus-launch made ubuntu 1 connect after I restarted it. So now the question is, why isn't KDM/KDE starting the two processes at login?

Trilby · 2012-07-14 03:04:59

I've never used either. I don't know how KDM works, but in general, whatever launches your WM/DE (xinitrc?) should include

dbus-launch --exit-with-session <window manager>

This is not needed if you are using console-kit, as console-kit starts a dbus session (I think ... I don't use console kit either). Some display managers start console-kit.

I suspect there are settings for KDM somewhere for this - hopefully someone else will point you in the right direction for that.

Last edited by Trilby (2012-07-14 03:05:37)

briancs · 2012-07-14 14:17:11

I am using inittab actually, though I've tried xinitrc and kdm-daemon in an attempt to make things work.

Here's what did work: I started dbus-daemon manually with

sudo dbus-daemon --session

Then started dbus-launch in another terminal with

sudo dbus-launch

.

After a reboot, the settings stuck and the two daemons started up automatically.

I am going to mark this solved.

cfr · 2012-07-15 15:14:58

I use KDE and start KDM via inittab:

$ ps ax | grep dbus
  529 ?        Ss     0:24 dbus-daemon --system
 1800 ?        S      0:00 /usr/bin/dbus-launch --sh-syntax --exit-with-session
 1801 ?        Ss     0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
 1817 ?        S      0:00 /usr/bin/dbus-launch --sh-syntax --exit-with-session
 1818 ?        Ss     0:01 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session

The last four are all owned by my user so far as I can tell from htop. I'm not sure why I would have double the daemons while you had none by default...

Arch Linux

#1 2012-07-13 22:59:45

[SOLVED] Various D-bus errors with KDE

#2 2012-07-13 23:03:46

Re: [SOLVED] Various D-bus errors with KDE

#3 2012-07-13 23:38:54

Re: [SOLVED] Various D-bus errors with KDE

#4 2012-07-13 23:48:01

Re: [SOLVED] Various D-bus errors with KDE

#5 2012-07-14 02:44:20

Re: [SOLVED] Various D-bus errors with KDE

#6 2012-07-14 03:04:59

Re: [SOLVED] Various D-bus errors with KDE

#7 2012-07-14 14:17:11

Re: [SOLVED] Various D-bus errors with KDE

#8 2012-07-15 15:14:58

Re: [SOLVED] Various D-bus errors with KDE

Board footer