On Thu, 7 Jan 2010, Jose Luis Perez Diez wrote:
> El Thursday, 7 de January de 2010 12:07:20 Alexander Lehner va escriure: >> If I do an 'ssh remotehost' and run an application on 'remotehost' which >> does some dbus stuff, it seems that the dbus interface does not find the >> 'right' SystemBus or whatever. >> I have to use the local console (terminal on FR) to get proper results. > > If your app access the system bus it will work fine. If the app uses the > session bus yo could set DISPLAY to :0 or get the sesion dbus address from an > app using it ( I use export `grep DBUS_SESSION /proc/*/environ |tail -1 | > sed 's/^.*:DBUS/DBUS/'` to copy it to my enviroment) Thanks a lot, that helped me out! Setting the DISPLAY to :0 didn't work in my case, but the /proc trick worked. I've got a Moblin 2.1 here and the /proc seems a bit different, so I use the following code: export `strings /proc/*/environ|grep DBUS_SESSION|tail -1` Alex. > > >> I have no idea how dbus finds out that I come from a remote connection and >> how I can avoid/fix this behaviour. It is not the DISPLAY env nor any >> SSH_* envs. >> >> (As mention, the actual problem does not happen on a FR-related >> software but on a different project of my own). >> >> >> Thanks, > > > > _______________________________________________ > devel mailing list > devel@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/devel > _______________________________________________ devel mailing list devel@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/devel
