Remote Desktop: Difference between revisions
imported>Kavika13 Mention polkit policies that may fix the blackscreeen on reboot in XRDP |
imported>MichaelCTS Add information about starting desktop sessions |
||
| Line 1: | Line 1: | ||
== Clients == | |||
* Tiger VNC | * Tiger VNC | ||
* Guacamole | * Guacamole | ||
| Line 5: | Line 5: | ||
* x2go | * x2go | ||
== Servers == | |||
* XRDP | * XRDP | ||
=== Configuration === | |||
Most servers provide a <code>vncserver</code> command. | |||
Various servers provide different configuration options either by CLI or by configuration file. | |||
==== Desktop session ==== | |||
To start a desktop session or window manager, one currently has to do this manually there is a bug where servers still have hard-coded paths to <code>/usr/share/xsessions</code> to look for <code>.desktop</code> files. That means one has to write a script that starts the desktop session, window manager, or any other X application. | |||
Some servers will automatically run <code>$HOME/.vnc/xstartup</code> but the more secure options is to be explicit. | |||
Write an executable script and run <code>vncserver -xstartup $pathToScript</code> | |||
An example script can be | |||
<source lang="bash"> | |||
#!/usr/bin/env bash | |||
# set some env variables | |||
# start window manager | |||
exec icewm | |||
</source> | |||
<code>pathToScript</code> can also be a path to an executable like <code>${pkgs.icewm}/bin/icewm</code> | |||
---- | ---- | ||