On 09/21/2010 12:37 PM, ext Thiago Macieira wrote:
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.
Here's how I got things to work. The screen trick I lifted from the Aava
MeeGo wiki (I think). The reason why I ssh into the device as root
rather than as meego is that I already have an alias for the root ssh
and I'm lazy.
1)
$ cat /usr/share/applications/screen.desktop
[Desktop Entry]
Name=Screen
Exec=/usr/bin/screen -dmS meego
Icon=moblin-xterm
Type=Application
2)
Launch Screen from the app grid.
3)
ssh into the device as root
4)
-bash-4.0# screen -d -RR
5)
bash-4.0# grep DBUS /var/log/uxlaunch.log
[04.342834] [700] DBUS_SESSION_BUS_PID=824
[04.342926] [700]
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-BOMcgRAREA,guid=68885a0ed0ed3a255c6c596b00000017
6)
bash-4.0# export
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-BOMcgRAREA,guid=68885a0ed0ed3a255c6c596b00000017
7)
bash-4.0# su meego
8)
[me...@localhost root]$ dbus-monitor
signal sender=org.freedesktop.DBus -> dest=:1.23 serial=2
path=/org/freedesktop/DBus; interface=org.freedesktop.DBus;
member=NameAcquired
string ":1.23"
method call sender=:1.23 -> dest=org.freedesktop.DBus serial=3
path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch
string "type='method_call'"
method call sender=:1.23 -> dest=org.freedesktop.DBus serial=4
path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch
string "type='method_return'"
method call sender=:1.23 -> dest=org.freedesktop.DBus serial=5
path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch
--
Pertti
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
