Note: This bug came with obarun, I just haven't had time to investigate it, until now.
Note 2: I dislike dbus... but can't find alternatives to programs that depend on it at this time...
I found out that this (zombie) dbus socket directory...
taco@ zen ~ % sudo netstat -lp | grep /tmp/dbus
unix 2 [ ACC ] STREAM LISTENING 9877 388/dbus-daemon @ /home/obarun/tmp/dbus-UBMbfnQpKr
...Doesn't exist
taco@ zen ~ % ls -la /home
total 12K
drwxr-xr-x 3 root root 4.0K Jan 24 12:10 ./
drwxr-xr-x 18 root root 4.0K Jan 25 13:36 ../
drwx------ 31 taco users 4.0K Mar 6 23:55 taco/
# No "obarun" directory...
Despite this the system doesn't seem to give a shit about whether it is there or not.
Where is /home/obarun/tmp defined exactly? Here.
taco@ zen ~ % cat /home/taco/.dbus/session-bus/13903b3e006b9cba24cc683456a6705b-0
# This file allows processes on the machine with id 13903b3e006b9cba24cc683456a6705b using
# display :0 to find the D-Bus session bus with the below address.
# If the DBUS_SESSION_BUS_ADDRESS environment variable is set, it will
# be used rather than this file.
# See "man dbus-launch" for more details.
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/home/obarun/tmp/dbus-UBMbfnQpKr,guid=ea0ebb90e44b9752aa585f4756dc8a01
DBUS_SESSION_BUS_PID=388
DBUS_SESSION_BUS_WINDOWID=6291457
dbus-launch manual wrote
If DBUS_SESSION_BUS_ADDRESS is not set for a process that tries to use D-Bus, by default the
process will attempt to invoke dbus-launch with the --autolaunch option to start up a new
session bus or find the existing bus address on the X display or in a file in
~/.dbus/session-bus/
Update: After digging, I found where dbus-daemon might be defining the tmp directory (which should be /tmp btw, not /home!!)
taco@ zen ~ % cat /usr/share/dbus-1/session.conf | grep obarun
<listen>unix:tmpdir=/home/obarun/tmp</listen>