<br>Thanks. I am using the system bus so<br>
I should do this instead:<br>
<br>
dbus-daemon --system --print-address >/tmp/output 2>&1 &<br>
<br>
Is that correct?<br>
<br>
<br>
mark<br>
<br>
<br>
<div><span class="gmail_quote">On 6/28/06, <b class="gmail_sendername">Havoc Pennington</b> <<a href="mailto:hp@redhat.com">hp@redhat.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Mark S. Townsley wrote:<br>><br>> Can someone suggest a good way to debug this send problem? I tried<br>> various things but running out of ideas.<br><br>Here are the steps to verbose-debug something:<br><br><br>
$ dbus-daemon --session --print-address >/tmp/output 2>&1 &<br>$ head -1 /tmp/output<br>[should print the address of the bus just launched]<br>$ DBUS_SESSION_BUS_ADDRESS=[above address] bash<br>[launches a new shell using the bus that verbose logs to /tmp/output]
<br>$ myapp<br><br>maybe this should be a dbus-launch feature, like<br>$ dbus-launch --verbose-output-file=/tmp/output bash<br><br>which would then let you run stuff from the bash, while looking at<br>verbose log spew in /tmp/output
<br><br>But at least the steps to do it manually might be nice to add to the man<br>page, assuming I got them right ... I didn't test it.<br><br>Havoc<br></blockquote></div><br>