Problem: dbus variables not being exported since a few days ago (~2018-07-16).

Lockywolf · 07-17-2018, 06:50 AM

Hello, everyone.

Not sure if my problem is connected to a recent '-current' update, or just is a result of the wrong curvature of my arms, but since yesterday, dbus is not working on my system.

In particular, dbus system-wide variables don't seem to be exported and all dbus-dependent applications refuse to start. However, starting them with 'dbus-launch appname' works just fine.

I actually noticed this when my xfce refused to start, complaining about not being able to connect to the dbus socket.

Code:

Failed to open connection to session bus: Failed to connect to socket /tmp/dbus-

Where may the problem hide?

UPD:
As a work-around, I switched the default runlevel back to 3 and added

Code:

export $(dbus-launch)

to .bashrc

But this clearly is the dirtiest trick on Earth, so I'm still looking for a better solution.

UPD3+4:
NetworkManager issue, which was here, is, in fact, unrelated.

orbea · 07-17-2018, 10:21 AM

What DE or WM are you using? How are you starting X?

I personally put this in ~/.xinitrc and use startx, it seems to work well.

Code:

eval `dbus-launch --sh-syntax --exit-with-session`

I would suggest against using ~/.bashrc since that is sourced every time you open a terminal.

Lockywolf · 07-17-2018, 08:12 PM

The problem with dbus in X sort of magically disappeared (hope it stays like this).

However the problem with dbus-monitor run from the console is still there.

Still, running basically any dbus-aware program from the terminal requires exporting dbus variables first.

Since we have system-wide rd.messagebus anyway, shan't we have something like /etc/profile.d/messagebus.sh ?