This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
howto:remote_viz [2020/11/11 15:03] ccrosby [Getting a Virtual Desktop on a compute node] |
howto:remote_viz [2021/12/09 16:42] (current) |
||
|---|---|---|---|
| Line 22: | Line 22: | ||
| There is a default VNC server installed on chpcviz. | There is a default VNC server installed on chpcviz. | ||
| - | / | + | / |
| Line 28: | Line 28: | ||
| TurboVNC by default sets up a startup file that selects the lightweight window manager Fluxbox. | TurboVNC by default sets up a startup file that selects the lightweight window manager Fluxbox. | ||
| - | Your xstartup.turbovnc file should look like this: | + | Your $HOME/.vnc/xstartup.turbovnc file should look like this. Please ensure that this file is executable. |
| < | < | ||
| #!/bin/sh | #!/bin/sh | ||
| Line 48: | Line 48: | ||
| The vncserver will continue running even after logging out. If you are no longer going to use it, please kill the server as follows: | The vncserver will continue running even after logging out. If you are no longer going to use it, please kill the server as follows: | ||
| - | / | + | / |
| where :3 should be changed to whichever display the server has been running on. | where :3 should be changed to whichever display the server has been running on. | ||
| + | |||
| + | === Troubleshooting === | ||
| + | A known problem is that the VNC server is not compatible with Python-3.7. | ||