brl/mutter
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs/building-and-running: Be more clear about remote desktop

Browse Source 
Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3943>
This commit is contained in:
Sebastian Wick 2024-08-12 23:45:14 +02:00 committed by Marge Bot
parent 7a4a2ebd36
commit 11ef52639f
1 changed files with 10 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
doc/building-and-running.md
View File

@ -155,17 +155,24 @@ This will create a D-Bus session, and attach to it. To attach to the same sessio
There are limitations to the nested instance, such as keyboard shortcuts usually not getting to the nested compositor. The remote-desktop feature can help working around this. There are limitations to the nested instance, such as keyboard shortcuts usually not getting to the nested compositor. The remote-desktop feature can help working around this.
First create a [nested D-Bus session](#d-bus-session). In this, run gnome-shell in headless mode with a virtual monitor. E.g. First create a [nested D-Bus session](#d-bus-session). In this, run gnome-shell in headless mode. E.g.
```sh ```sh
⬢ dbus-session.sh new ⬢ dbus-session.sh new
⬢ gnome-shell --headless --virtual-monitor 1280x720 ⬢ gnome-shell --headless
``` ```
Build `gnome-remote-desktop` and run:
```sh ```sh
⬢ dbus-session.sh attach ⬢ dbus-session.sh attach
⬢ ./build/src/gnome-remote-desktop-daemon ⬢ ./build/src/grdctl rdp set-credentials test test
⬢ ./build/src/grdctl rdp enable
⬢ ./build/src/gnome-remote-desktop-daemon --headless --rdp-port 12345
``` ```
Warning: This turns on rdp access for the entire system with weak credentials! For quick testing, `GNOME_REMOTE_DESKTOP_TEST_RDP_USERNAME` and `GNOME_REMOTE_DESKTOP_TEST_RDP_PASSWORD` might be useful.
Finally, connect to `localhost:12345` with username and password `test` using an RDP client, like xfreerdp or Remmina.
## Native ## Native
Sometimes it's necessary to run the "native backend", on real display hardware. The easiest way is to switch to a tty and run (in your Toolbx container if this is where it was installed): Sometimes it's necessary to run the "native backend", on real display hardware. The easiest way is to switch to a tty and run (in your Toolbx container if this is where it was installed):