UNIX for Advanced & Expert Users

So reading the man page , looks like the only reason why it won't try to create the ~/.dbus directory is if it attaches to an already existing session. So if "DBUS_SESSION_BUS_ADDRESS" is set, it will just attach itself to it, without invoking a new session, seems like a good way to prevent unnecessary calls.

If you are on redhat, try installing strace, which basically helps you trace the process. Atleast it will confirm if the below is true. Other than that, I have no more ideas on how to debug this. Maybe someone else on the forum has more experience with dbus and can pitch in.

Ok thanks for the help, $DBUS_SESSION_BUS_ADDRESS is not set

Code:

echo $DBUS_SESSION_BUS_ADDRESS
DBUS_SESSION_BUS_ADDRESS: Undefined variable

throwing it out to anyone else then

dude2cool thanks for the help

It sounds like your daemon is creating its own D-Bus message bus (channel), correct? Or is you daemon simply sending messages to the system message bus?

Are you able to see messages on this message bus using dbus-monitor?

D-Bus is a publish/subscribe mechanism. How are users subscribing to the message bus?

to be honest my knowledge is very limited, i am not 100% what it is doing

How could i use dbus-monitor with the application to see what it is doing?>>

thanks