[Solved] DBus not running properly

farhaven · Tux's lil' helper Joined: 17 Feb 2008 Posts: 127

Hi people,

I'm having a bit of a problem with DBus here. It looks like most programs can't find the session message bus, which I start from my .xinitrc via

pappy_mcfae · Posted: Thu Jul 09, 2009 6:07 am Post subject:

Why do it this way? You can setup hal and dbus to start at boot time. To do otherwise would require some fancy footwork with a script. Just enter the command rc-update add dbus default && rc-update add hald default, reboot, and be done with it.

Blessed be!
Pappy
_________________
This space left intentionally blank, except for these ASCII symbols.

farhaven · Tux's lil' helper Joined: 17 Feb 2008 Posts: 127

The system messagebus is already running. Previously, I used a bit of code in my .xinitrc which wrote the session bus address to a file in /tmp, so I could access that bus from other sessions as well (i.e. to restart awesome from a VT). dbus-launch does the same, but without writing the bus address to /tmp/dbus-0. If I don't run awesome via dbus-launch, it still starts up fine, creating its own session bus (as it should, because there's no session bus running), but my problem persists. notify-send for example still crashes with the error message I pasted instead of opening its own session bus as it doesn't seem to be abled to find the already running bus (which should be accessible, as the $DBUS_SESSION_BUS_ADDRESS is the same awesome uses).

Edit: I forgot to mention: hald fails to start with the same error message on a cleanly booted system with the DBus system messagebus running. I even removed /etc/dbus-1 and reinstalled DBus, just to see if it was a broken config, but the problem persists.

pappy_mcfae · Posted: Thu Jul 09, 2009 7:39 pm Post subject:

I still don't get why you need to do all those extra steps. It seems to me you're making things more complex than they need to be.

Blessed be!
Pappy
_________________
This space left intentionally blank, except for these ASCII symbols.

farhaven · Tux's lil' helper Joined: 17 Feb 2008 Posts: 127

Well, if I do it your way (i.e. just start the system message bus), Awesome is still the only program using DBus that doesn't crash on startup with the pasted message. Hal doesn't start either, and if I manually try to start it via

pappy_mcfae · Posted: Thu Jul 09, 2009 10:04 pm Post subject:

Then try this:

1) emerge -C hal dbus
2) remove any remnants, such as /etc/dbus-1, /etc/hal, /var/run/hald.pid, /var/run/dbus.pid, /var/run/dbus and /var/run/hald.
3) emerge hal dbus
4) /etc/init.d/dbus restart

If the problem remains, it could be an X issue. See what the above yields, and we can go from there.

BB!
P

PS. Next time, it would be helpful if you gave really important info as, "as it worked that way before the update that broke about everything DBus related," at the beginning of the process, not near the middle.
_________________
This space left intentionally blank, except for these ASCII symbols.

farhaven · Tux's lil' helper Joined: 17 Feb 2008 Posts: 127

Okay, that brought me one step further. Hald now starts without problems, though the DBus issue in X remains. I just opened dbus-monitor in one xterm and used notify-send in another, which produced some interesting output in the monitor window:

pappy_mcfae · Posted: Fri Jul 10, 2009 12:42 am Post subject:

It's no thing. What does your /var/log/Xorg.0.log look like?

Blessed be!
Pappy
_________________
This space left intentionally blank, except for these ASCII symbols.

farhaven · Tux's lil' helper Joined: 17 Feb 2008 Posts: 127

This is my Xorg.0.log. I grepped it for EE and WW, but there were only a few warnings about missing font paths and about my graphics driver. I'm completely lost here

Thanks for your help btw

pappy_mcfae · Posted: Sat Jul 11, 2009 6:36 am Post subject:

My first thought would be to drop dri2, and go for a much more conventional setup with the intel GPU. I haven't used dri2, so I don't know if it would cause an issue, but one of the errors was directly affecting dri2. Try running without /etc/X11/xorg.conf and see what happens at that point.

Blessed be!
Pappy
_________________
This space left intentionally blank, except for these ASCII symbols.

farhaven · Tux's lil' helper Joined: 17 Feb 2008 Posts: 127

It ran flawless with DRI2 before the upgrade that killed it all, and to be honest, I'm not entirely sure on how the X server itself could affect DBus, especially in the manner described (only awesome and dbus-send work, everything else crashes). At the moment, I've unmerged dbus and hal and I'm running revdep-rebuild right now to see whether there were some linking issues.

farhaven · Tux's lil' helper Joined: 17 Feb 2008 Posts: 127

Whoohoo, removing dbus and hal and letting revdep-rebuild handle all reinstalling and remerging of broken libs did the trick. Thanks a lot for your time and effort

pappy_mcfae · Posted: Mon Jul 13, 2009 8:55 pm Post subject:

You are most welcome.

Blessed be!
Pappy
_________________
This space left intentionally blank, except for these ASCII symbols.