Skip to content

Remote graphics

Important

The OpenOndemand portal also allows you to get full desktop session, with all applications, directly on a compute node where you can carry out heavy interactive workloads.

We need to reboot the login machines occasionally, killing all sessions, so make sure to always save your work frequently. Remote desktops on the login nodes are intended only for lightweight interactive work.

You can get remote desktop with 3D accelerated graphics on compute nodes via OpenOndemand and on login nodes shown below.

Example of desktop

RDP support

We support the Remote Desktop Protocol, or RDP on alvis1, alvis2, vera1 and vera2. RDP has widespread support within most modern operating systems. Examples of desktop client applications include:

  • Remote Desktop application for Windows
  • Windows App for Mac OS
  • Clients like Remmina and krdp for Linux.

The xrdp server on can be connected to directly using a desktop client (using address vera1.c3se.chalmers.se, vera2.c3se.chalmers.se, alvis1.c3se.chalmers.se or alvis2.c3se.chalmers.se and port 3389, the default for RDP), supplying your username and password when connecting. Note that for technical reasons, you must make sure that you have no running Thinlinc sessions before trying to connect:

$ loginctl | grep thinlinc | grep YOUR_CID_HERE
65891 YOUR_UID YOUR_CID_HERE         thinlinc active  no

The easiest way to make sure to end your ThinLinc sessions is to kill all of your processes on the node (save any important work first!):

$ pkill -9 -u YOUR_CID_HERE
Shared connection to vera1 closed.

Web client

We are running an in-house developed web client based on Apache Guacamole at

After connecting and waiting for a few seconds, a remote desktop should appear. Clicking the arrow on the right-hand side of the screen reveals the clipboard:

Web-based RDP clipboard

The remote clipboard automatically reflects the remote desktop clipboard, whereas the local clipboard is manual. This is because there is no reliable way to automatically synchronize your local clipboard contents with the remote desktop, for security reasons enforced by your browser. When you copy things in the remote desktop, the test should automatically appear in the "Remote clipboard" area. You can click the "Fetch" button to copy it into the "Local clipboard" area, from which you can manually copy- and paste it.

Similarly, you can type or paste things that you want to push to the server clipboard into the "Local clipboard", and click the "Push" button to push it to the remote server. The text will then immediately be pasteable on the remote desktop. If you want a more natural clipboard experience, we recommend using a desktop application rather than the webapp.

After you disconnect, your session should be saved for 3 days before it is cleaned up, although sometimes your session may not be properly restored and a new one will be started.

If you want to switch to thinlinc, killing all of your processes is the most sure-fire method. This is also a recommended step in case you have trouble connecting at all:

$ pkill -9 -u YOUR_CID_HERE
Shared connection to vera1 closed.

Windows Remote Desktop (mstsc.exe)

Updated 2025-05-27

The built-in Windows Remote desktop client, or mstsc.exe (originally short for Microsoft Terminal Services Client), can offer very good performance, but can be tricky to connect with. Generally, using a .rdp file to connect to a non-Microsoft RDP server which you have not previously connected to will not work. The following procedure, however, should work for both personal, self-administered, and Chalmers-administered Windows machines (for the Windows machines of other organizations, this service might be blocked by policy - talk to your IT department.) The necessary steps as of this writing are slightly unintuitive and may require some trial and error.

The Windows Remote Desktop client with important options highlighted

In brief:

  • Start mstsc.exe (Remote Desktop Connection) and click "Show options" to get the view shown in the image.
  • Type in the server you want to connect to in the "Computer" field (e.g., vera2.c3se.chalmers.se)
  • If there is a checked box Always ask for credentials, uncheck it. This box is not visible in the image.
  • Type in your CID in the "User name" box.
  • Check the box Allow me to save credentials
  • Click Connect.
  • If you get a warning about the publisher being unknown, you can ignore it as this appears to refer to Microsoft's Network level authentication scheme, which is largely undocumented and not supported on non-Windows servers. The Vera and Alvis servers have valid f certificates issued by Letsencrypt.
  • You will get a propmt to enter your credentials. This may be pre-filled with a Microsoft ID, and you may need to click More Choices and Use a different account. You can then enter your CID (again) along with your password.
  • You should now be able to connect by clicking OK.
  • You should be able to reconnect to this server without trouble, but you will need to repeat these steps for each of the servers.

Mac OS Windows App

For connecting from Mac OS, you can use the Windows App, available via Apple Store. Select "Devices" and "Add PC". In the "PC Name" field, enter the hostname (e.g., vera1.c3se.chalmers.se). Then enter your CID and your password in the credentials section, and click Add. Once the device is added, you can double-click it to connect to the remote desktop session.

FreeRDP 3.0+ clients (Remmina, krdc, etc.)

If you do not have a preferred RDP client for Linux, we suggest Remmina. For FreeRDP-based clients you should be able to download the connect.rdp file from each server and open it with the client, and then supply your CID and password into the prompt to log in directly:

If you do not have at least FreeRDP 3.0, the CID/password prompt does not work properly, and you instead need to import the .rdp file or create a new connection, and then enter the server name (e.g., vera1.c3se.chalmers.se) as well as your CID and password.

Thinlinc

In addition to terminal and RDP access, one can use ThinLinc. ThinLinc uses the VNC protocol to provide a remote desktop.

Connecting with ThinLinc desktop client

You can download the ThinLinc client software from: https://www.cendio.com/thinlinc/download/ for best performance. Install the client software and launch it.

  • Server: vera1.c3se.chalmers.se, vera2.c3se.chalmers.se, alvis1.c3se.chalmers.se, alvis2.c3se.chalmers.se
  • Name: <your CID>
  • Password: <your password>

You can also use ssh keys to authenticate, instead of password.

Disconnect by click your user name in top-right corner and choose Quit.

ThinLinc normally starts full-screen, but you can change this default option to windowed mode, and you can access the ThinLinc menu using the F8 key.

Connecting through browser

Thinlinc also has a web client, if you do not want to use the desktop client software. You can log in with username and password via

Running 3D applications - VirtualGL

You can use VirtualGL to run run OpenGL software with hardware acceleration. This is often required as many applications are too buggy in software rendering to be usable. Most graphical softwares are available through the application menu. If you need to launch the applications yourself via the terminal, you need to run

vglrun some_application

Some applications circumvent VirtualGL, and requires additional setup. Matlab requires running

vglrun matlab -nosoftwareopengl

Known errors

Pre-loading modules in .bashrc will most likely cause remote desktop sessions to break. You should use an alias for loading them instead and run that after logging in.