Remote X11 application starting

Rémi Audebert reporter

I think of at least three issues once we are on the remote machine:

We want to connect to the X server as the target user, and from the few tests I made the xhack.py script should not be required anymore
We want to know the display's name, it's usually :0 but we should avoid guessing it
We want to access the dbus session of the user, that is the content of the DBUS_SESSION_BUS_ADDRESS env variable

So, 1. somehow solved itself in the past year, for 2. DISPLAY is stored in the systemd user process and is inherited by processes started by it and for 3. we can use machinectl shell.

Here are a few working examples:

# machinectl shell USERNAME@ /usr/bin/systemd-run --user /usr/bin/quake3 # Gets DISPLAY from systemd-run
# machinectl shell USERNAME@ /usr/bin/notify-send 'Pour jouer à quake, cliquez ici' # Gets DBUS_SESSION_BUS_ADDRESS from machinectl shell

The next step is to validate theses commands and then write them into docs/source/cookbook.rst.

2017-03-05T22:01:22+00:00

Comments (3)

Théophile Bastian
Isn't that simply a DISPLAY=:0 some_command?
- 2017-03-02T13:42:29+00:00
Antoine Pietri
No. https://bitbucket.org/prologin/sadm/src/ddd84a37f9d3cc6100aaf43024f173e3cbc17cfb/python-lib/prologin/xhack.py?at=master&fileviewer=file-view-default

But this is an ugly hack, we should be able to do way better using xauth creds.
- 2017-03-02T13:43:38+00:00
Rémi Audebert reporter
I think of at least three issues once we are on the remote machine:
1. We want to connect to the X server as the target user, and from the few tests I made the xhack.py script should not be required anymore
2. We want to know the display's name, it's usually :0 but we should avoid guessing it
3. We want to access the dbus session of the user, that is the content of the DBUS_SESSION_BUS_ADDRESS env variable
So, 1. somehow solved itself in the past year, for 2. DISPLAY is stored in the systemd user process and is inherited by processes started by it and for 3. we can use machinectl shell.

Here are a few working examples:
```
# machinectl shell USERNAME@ /usr/bin/systemd-run --user /usr/bin/quake3 # Gets DISPLAY from systemd-run
# machinectl shell USERNAME@ /usr/bin/notify-send 'Pour jouer à quake, cliquez ici' # Gets DBUS_SESSION_BUS_ADDRESS from machinectl shell
```
The next step is to validate theses commands and then write them into docs/source/cookbook.rst.
- 2017-03-05T22:01:22+00:00
Log in to comment