On 07/04/08 16:02 +0200, Will Stephenson wrote:
On Monday 07 April 2008, Craig Millar said:
Why does qdbus need an available X session to run? I noticed this on a remote ssh session to my home box.
It doesn't need absolutely need an X session. It first looks in DBUS_SESSION_BUS_ADDRESS. If this isn't set it will try to run dbus-launch --autostart to determine the address by querying another X window... which is session dependent.
Ok - thanks for explaining that - documentation is a little thin on the ground.
You're talking on the wrong bus. KTorrent doesn't exist on the bus in DBUS_SESSION_BUS_ADDRESS then.
You can copy the value of that from another environment then you should be talking on the right bus.
I guess you are trying to remotely control a ktorrent instance over an SSH session. The first time it didn't work because there was no bus address and no way to get one, the second time you got the address of the session bus of your local session. You could try saving the value of DBUS_SESSION_BUS_ADDRESS when you start ktorrent to a file and then setting it after you ssh in.
Ok - that makes perfect sense - but is there any way I can determine the DBUS_SESSION_BUS_ADDRESS of the existing session on the remote machine? It kind of defeats the object of being able to do stuff remotely if I have to work out what that may be before I leave the computer. ;)
Let us know how you get on, with dcop all this was easy^Waround for years and well known.
Making progress. Slowly! It seems the docs are lagging way behind - I did find a small blog entry [1] about using qdbus that got me started, other than that google results are pretty sparse. But I was encouraged by the apparent ease of use in the early stages - it's not too disimilar to dcop in terms of usage, at least as far as I can tell.
Will
Thanks again, Craig [1]. http://www.kuliniewicz.org/blog/archives/2007/12/28/qdbus/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org