Em Terça-feira 21 Setembro 2010, às 10:46:24, Pertti Kellomäki escreveu: > On 09/21/2010 10:27 AM, Kellomaki Pertti (Nokia-MS/Tampere) wrote: > > How can I connect to the session dbus daemon? I first tried just > > starting dbus-monitor, but I get: > > > > "Failed to open connection to session bus: /bin/dbus-launch terminated > > abnormally with the following error: Autolaunch error: X11 > > initialization failed." > > > > Looking at uxlaunch.log, variables XDG_SESSION_COOKIE, > > DBUS_SESSION_BUS_PID, and DBUS_SESSION_BUS_ADDRESS seemed relevant, and > > after setting them to the values listed in the log, I get the following > > when trying to start dbus-monitor: > > > > "Failed to open connection to session bus: Did not receive a reply. > > Possible causes include: the remote application did not send a reply, > > the message bus security policy blocked the reply, the reply timeout > > expired, or the network connection was broken." > > > > I have not worked with dbus before, so any advice is welcome. > > It seems that if I launch an xterm from the application grid, then > dbus-monitor works, but not if I ssh into the device and grab a screen > session which has been launched from the app grid.
If you ssh into the device, you are not part of the D-Bus session. So you
don't get access to it.
If you connect to a running screen session, you get the environment that
screen had when it started. In my opinion, screen should be considered a
separate session from D-Bus. That means you don't get access to it either.
In other words: you're not part of the session if you ssh in.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Senior Product Manager - Nokia, Qt Development Frameworks
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
Qt Developer Days 2010 - Munich Oct 11-13 - San Francisco Nov 1-3
For more information and to register: http://qt.nokia.com/qtdevdays2010
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
