Skip to content

Instantly share code, notes, and snippets.

@hyang0

hyang0/tigervnconubuntu.md

Created April 6, 2022 08:08
Show Gist options
  • Save hyang0/2eb3e1a192cf8a81e624a7db8548c9db to your computer and use it in GitHub Desktop.
Save hyang0/2eb3e1a192cf8a81e624a7db8548c9db to your computer and use it in GitHub Desktop.
Download ZIP

Revisions

  1. @plembo plembo revised this gist Feb 4, 2021. 1 changed file with 2 additions and 2 deletions.
    4 changes: 2 additions & 2 deletions tigervnconubuntu.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,5 +1,5 @@
    * NOTE: Given its current state, I've given up on tigervnc and now rely on "ssh -X" to execute remote gui apps. As a result
    I won't be updating this gist any more, but will leave it up as a reference for others. *
    **NOTE: Given its current state, I've given up on tigervnc and now rely on "ssh -X" to execute remote gui apps. As a result
    I won't be updating this gist any more, but will leave it up as a reference for others.**

    # Installing TigerVNC on Ubuntu 18.04 LTS
    This is for Ubuntu 18.04 LTS. [TigerVNC](https://tigervnc.org) is a remote desktop session server and viewer solution sponsored by [Red Hat](https://www.redhat.com) that is still in active development. While I recently tested under Ubuntu 19.10, I have no plans to test non-LTS versions in the future.
  2. @plembo plembo revised this gist Feb 4, 2021. 1 changed file with 2 additions and 2 deletions.
    4 changes: 2 additions & 2 deletions tigervnconubuntu.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,5 +1,5 @@
    ** NOTE: Given its current state, I've given up on tigervnc and now rely on "ssh -X" to execute remote gui apps. As a result
    I won't be updating this gist any more, but will leave it up as a reference for others. **
    * NOTE: Given its current state, I've given up on tigervnc and now rely on "ssh -X" to execute remote gui apps. As a result
    I won't be updating this gist any more, but will leave it up as a reference for others. *

    # Installing TigerVNC on Ubuntu 18.04 LTS
    This is for Ubuntu 18.04 LTS. [TigerVNC](https://tigervnc.org) is a remote desktop session server and viewer solution sponsored by [Red Hat](https://www.redhat.com) that is still in active development. While I recently tested under Ubuntu 19.10, I have no plans to test non-LTS versions in the future.
  3. @plembo plembo revised this gist Feb 4, 2021. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion tigervnconubuntu.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,5 +1,5 @@
    ** NOTE: Given its current state, I've given up on tigervnc and now rely on "ssh -X" to execute remote gui apps. As a result
    I won't be updating this gist any more, but will leave it up as a reference for others.
    I won't be updating this gist any more, but will leave it up as a reference for others. **

    # Installing TigerVNC on Ubuntu 18.04 LTS
    This is for Ubuntu 18.04 LTS. [TigerVNC](https://tigervnc.org) is a remote desktop session server and viewer solution sponsored by [Red Hat](https://www.redhat.com) that is still in active development. While I recently tested under Ubuntu 19.10, I have no plans to test non-LTS versions in the future.
  4. @plembo plembo revised this gist Feb 4, 2021. 1 changed file with 3 additions and 0 deletions.
    3 changes: 3 additions & 0 deletions tigervnconubuntu.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,3 +1,6 @@
    ** NOTE: Given its current state, I've given up on tigervnc and now rely on "ssh -X" to execute remote gui apps. As a result
    I won't be updating this gist any more, but will leave it up as a reference for others.

    # Installing TigerVNC on Ubuntu 18.04 LTS
    This is for Ubuntu 18.04 LTS. [TigerVNC](https://tigervnc.org) is a remote desktop session server and viewer solution sponsored by [Red Hat](https://www.redhat.com) that is still in active development. While I recently tested under Ubuntu 19.10, I have no plans to test non-LTS versions in the future.

  5. @plembo plembo revised this gist Dec 12, 2020. 1 changed file with 2 additions and 2 deletions.
    4 changes: 2 additions & 2 deletions tigervnconubuntu.md
    View file
    Original file line number Diff line number Diff line change
    @@ -3,7 +3,7 @@ This is for Ubuntu 18.04 LTS. [TigerVNC](https://tigervnc.org) is a remote deskt

    There are packages for TigerVNC in the repositories of the major distributions, but the latest versions for Ubuntu are broken. My workaround is to use the latest stable version from the TigerVNC project Github [release page](https://github.com/TigerVNC/tigervnc/releases), where generic binaries for 32 and 64-bit Linux are distributed as tarballs (dmg and exe installers for Mac and Windows are also available).

    NOTE: A key file is missing from the latest official binary release of TigerVNC for Linux, a perl script named ```vncserver```. Fortunately, this file is available from the git of one of its maintainers. Instructions on
    NOTE: A key file is missing from the latest official binary release of TigerVNC for Linux, a perl script named ```vncserver```. Fortunately, this file is available from a fork of the official repo. Instructions on
    how to download and install this file are provided below.

    While I continue to use the default Gnome Shell desktop on 18.04 LTS locally, it no longer works in a remote desktop session. If you really want to use Gnome remotely, you should look for a different solution like the proprietary [NoMachine](https://www.nomachine.com/) or Gnome's built-in [desktop sharing](https://help.ubuntu.com/stable/ubuntu-help/sharing-desktop.html.en) option. For remote sessions using vnc I specify [fvwm](https://fvwm.org) in my xstartup file (fvwm is slightly better than the even older twm). This has the advantage of using a lot less bandwidth and makes things more responsive over the network. Since my personal use of remote desktop sessions is to manage servers, the lack of a full desktop experience is not a drawback for me.
    @@ -63,7 +63,7 @@ $ which vncviewer
    /usr/local/bin/vncviewer
    ```

    9. The vncserver perl script is missing from the official binary release of TigerVNC for Linux beginning with v1.11.0, but is available from the git repo of one of its maintainers. This file should be downloaded and copied to /usr/local/bin.
    9. The vncserver perl script is missing from the official binary release of TigerVNC for Linux beginning with v1.11.0, but is available from a fork of the official repo. This file should be downloaded and copied to /usr/local/bin.

    ```
    $ wget https://raw.githubusercontent.com/metalefty/tigervnc/master/unix/vncserver
  6. @plembo plembo revised this gist Dec 12, 2020. 1 changed file with 2 additions and 1 deletion.
    3 changes: 2 additions & 1 deletion tigervnconubuntu.md
    View file
    Original file line number Diff line number Diff line change
    @@ -3,7 +3,8 @@ This is for Ubuntu 18.04 LTS. [TigerVNC](https://tigervnc.org) is a remote deskt

    There are packages for TigerVNC in the repositories of the major distributions, but the latest versions for Ubuntu are broken. My workaround is to use the latest stable version from the TigerVNC project Github [release page](https://github.com/TigerVNC/tigervnc/releases), where generic binaries for 32 and 64-bit Linux are distributed as tarballs (dmg and exe installers for Mac and Windows are also available).

    NOTE: A key file is missing from the latest official binary release of TigerVNC for Linux, a perl script named ```vncserver```. Fortunately, this file is available from a mirror of the official git repository here: https://raw.githubusercontent.com/metalefty/tigervnc/master/unix/vncserver .
    NOTE: A key file is missing from the latest official binary release of TigerVNC for Linux, a perl script named ```vncserver```. Fortunately, this file is available from the git of one of its maintainers. Instructions on
    how to download and install this file are provided below.

    While I continue to use the default Gnome Shell desktop on 18.04 LTS locally, it no longer works in a remote desktop session. If you really want to use Gnome remotely, you should look for a different solution like the proprietary [NoMachine](https://www.nomachine.com/) or Gnome's built-in [desktop sharing](https://help.ubuntu.com/stable/ubuntu-help/sharing-desktop.html.en) option. For remote sessions using vnc I specify [fvwm](https://fvwm.org) in my xstartup file (fvwm is slightly better than the even older twm). This has the advantage of using a lot less bandwidth and makes things more responsive over the network. Since my personal use of remote desktop sessions is to manage servers, the lack of a full desktop experience is not a drawback for me.

  7. @plembo plembo revised this gist Dec 12, 2020. 1 changed file with 14 additions and 4 deletions.
    18 changes: 14 additions & 4 deletions tigervnconubuntu.md
    View file
    Original file line number Diff line number Diff line change
    @@ -3,6 +3,8 @@ This is for Ubuntu 18.04 LTS. [TigerVNC](https://tigervnc.org) is a remote deskt

    There are packages for TigerVNC in the repositories of the major distributions, but the latest versions for Ubuntu are broken. My workaround is to use the latest stable version from the TigerVNC project Github [release page](https://github.com/TigerVNC/tigervnc/releases), where generic binaries for 32 and 64-bit Linux are distributed as tarballs (dmg and exe installers for Mac and Windows are also available).

    NOTE: A key file is missing from the latest official binary release of TigerVNC for Linux, a perl script named ```vncserver```. Fortunately, this file is available from a mirror of the official git repository here: https://raw.githubusercontent.com/metalefty/tigervnc/master/unix/vncserver .

    While I continue to use the default Gnome Shell desktop on 18.04 LTS locally, it no longer works in a remote desktop session. If you really want to use Gnome remotely, you should look for a different solution like the proprietary [NoMachine](https://www.nomachine.com/) or Gnome's built-in [desktop sharing](https://help.ubuntu.com/stable/ubuntu-help/sharing-desktop.html.en) option. For remote sessions using vnc I specify [fvwm](https://fvwm.org) in my xstartup file (fvwm is slightly better than the even older twm). This has the advantage of using a lot less bandwidth and makes things more responsive over the network. Since my personal use of remote desktop sessions is to manage servers, the lack of a full desktop experience is not a drawback for me.

    1. Install fvwm and xterm:
    @@ -60,7 +62,15 @@ $ which vncviewer
    /usr/local/bin/vncviewer
    ```

    9. Run vncserver and vncviewer as an ordinary user just to ensure they are working:
    9. The vncserver perl script is missing from the official binary release of TigerVNC for Linux beginning with v1.11.0, but is available from the git repo of one of its maintainers. This file should be downloaded and copied to /usr/local/bin.

    ```
    $ wget https://raw.githubusercontent.com/metalefty/tigervnc/master/unix/vncserver
    $ sudo cp vncserver /usr/local/bin
    $ sudo chmod ugo+x /usr/local/bin/vncserver
    ```

    10. Run vncserver and vncviewer as an ordinary user just to ensure they are working:

    ```
    $ vncserver :2
    @@ -76,13 +86,13 @@ Kill the remote session once done testing:
    ```
    $ vncserver -kill :2
    ```
    10. Update the system icon cache:
    11. Update the system icon cache:

    ```
    $ sudo update-icon-caches /usr/local/share/icons/*
    ```

    11. Create a new xstartup under .vnc (in the home directory of the user who will be launching remote sessions) to use fvwm as the remote desktop:
    12. Create a new xstartup under .vnc (in the home directory of the user who will be launching remote sessions) to use fvwm as the remote desktop:

    ```
    #!/bin/sh
    @@ -93,7 +103,7 @@ xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
    LANG=C fvwm &
    ```

    12. Now run vncserver again, and view the remote desktop with vncviewer (entering the remote password chosen previously).
    13. Now run vncserver again, and view the remote desktop with vncviewer (entering the remote password chosen previously).

    A few additional notes:

  8. @plembo plembo revised this gist Apr 22, 2020. 1 changed file with 1 addition and 0 deletions.
    1 change: 1 addition & 0 deletions tigervnconubuntu.md
    View file
    Original file line number Diff line number Diff line change
    @@ -97,6 +97,7 @@ LANG=C fvwm &

    A few additional notes:

    * The main reason I continue to use vnc after all these years is that it allows me to quickly start a remote session by connecting to the remote host over ssh and then launching vncserver in that remote console. Other solutions either require the remote service to always be up and running (a security risk), or having someone on the remote desktop consent to the connection using a gui dialog (an impossibility when dealing with 1,000s of servers in a data center).
    * You'll be invited to set a password the first time you run vncserver: do it! For the current version of TigerVNC, passwords are limited to 8 characters.Remember, the vnc server is _not_ integrated with your host's authentication system: that password is the only thing that keeps outsiders from getting into an existing session.
    * While you can certainly launch a vnc session as root, it is _not_ recommended.
    * TigerVNC does not support multiple monitors. If you're using fvwm as your remote desktop that won't be a problem: fvwm doesn't support multiple monitors either!
  9. @plembo plembo revised this gist Apr 22, 2020. 1 changed file with 2 additions and 2 deletions.
    4 changes: 2 additions & 2 deletions tigervnconubuntu.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,9 +1,9 @@
    # Installing TigerVNC on Ubuntu 18.04 LTS
    This is for Ubuntu 18.04 LTS. [TigerVNC](https://tigervnc.org) is a remote desktop session server and viewer solution sponsored by [Red Hat](https://www.redhat.com) that is still in active development. While I recently tested under Ubuntu 19.10, I have no plans to test non-LTS versions in the future.

    There are packages for tigervnc in the repositories of the major distributions, but the latest versions for Ubuntu are broken. My workaround is to use the latest stable version from the TigerVNC project Github [release page](https://github.com/TigerVNC/tigervnc/releases), where generic binaries for 32 and 64-bit Linux are distributed as tarballs (dmg and exe installers for Mac and Windows are also available).
    There are packages for TigerVNC in the repositories of the major distributions, but the latest versions for Ubuntu are broken. My workaround is to use the latest stable version from the TigerVNC project Github [release page](https://github.com/TigerVNC/tigervnc/releases), where generic binaries for 32 and 64-bit Linux are distributed as tarballs (dmg and exe installers for Mac and Windows are also available).

    While I continue to use the default Gnome Shell desktop on 18.04 LTS locally, it no longer works as a remote desktop. For remote sessions I specify [fvwm](https://fvwm.org) in my xstartup file (fvwm is slightly better than the even older twm). This has the advantage of using a lot less bandwidth and makes things more responsive over the network. Since my personal use of remote desktop sessions is to manage servers, the lack of a full desktop experience is not a drawback for me.
    While I continue to use the default Gnome Shell desktop on 18.04 LTS locally, it no longer works in a remote desktop session. If you really want to use Gnome remotely, you should look for a different solution like the proprietary [NoMachine](https://www.nomachine.com/) or Gnome's built-in [desktop sharing](https://help.ubuntu.com/stable/ubuntu-help/sharing-desktop.html.en) option. For remote sessions using vnc I specify [fvwm](https://fvwm.org) in my xstartup file (fvwm is slightly better than the even older twm). This has the advantage of using a lot less bandwidth and makes things more responsive over the network. Since my personal use of remote desktop sessions is to manage servers, the lack of a full desktop experience is not a drawback for me.

    1. Install fvwm and xterm:

  10. @plembo plembo revised this gist Apr 22, 2020. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion tigervnconubuntu.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,4 +1,4 @@
    # Installing TigerVNC on Ubuntu
    # Installing TigerVNC on Ubuntu 18.04 LTS
    This is for Ubuntu 18.04 LTS. [TigerVNC](https://tigervnc.org) is a remote desktop session server and viewer solution sponsored by [Red Hat](https://www.redhat.com) that is still in active development. While I recently tested under Ubuntu 19.10, I have no plans to test non-LTS versions in the future.

    There are packages for tigervnc in the repositories of the major distributions, but the latest versions for Ubuntu are broken. My workaround is to use the latest stable version from the TigerVNC project Github [release page](https://github.com/TigerVNC/tigervnc/releases), where generic binaries for 32 and 64-bit Linux are distributed as tarballs (dmg and exe installers for Mac and Windows are also available).
  11. @plembo plembo revised this gist Apr 22, 2020. 1 changed file with 2 additions and 2 deletions.
    4 changes: 2 additions & 2 deletions tigervnconubuntu.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,9 +1,9 @@
    # Installing TigerVNC on Ubuntu
    This is for Ubuntu 18.04 LTS. [TigerVNC](https://tigervnc.org) is a remote desktop server and viewer solution sponsored by [Red Hat](https://www.redhat.com) that is still in active development. While I recently tested under Ubuntu 19.10, I have no plans to test non-LTS versions in the future.
    This is for Ubuntu 18.04 LTS. [TigerVNC](https://tigervnc.org) is a remote desktop session server and viewer solution sponsored by [Red Hat](https://www.redhat.com) that is still in active development. While I recently tested under Ubuntu 19.10, I have no plans to test non-LTS versions in the future.

    There are packages for tigervnc in the repositories of the major distributions, but the latest versions for Ubuntu are broken. My workaround is to use the latest stable version from the TigerVNC project Github [release page](https://github.com/TigerVNC/tigervnc/releases), where generic binaries for 32 and 64-bit Linux are distributed as tarballs (dmg and exe installers for Mac and Windows are also available).

    While I continue to use the default Gnome desktop on 18.04 LTS locally, that no longer works as a remote desktop. For remote sessions I specify [fvwm](https://fvwm.org) in my xstartup file (fvwm is slightly better than twm). This has the advantage of using a lot less bandwidth and makes things more responsive over the network. Since my personal use of remote desktop is to manage servers, the lack of a full desktop experience is not a drawback for me.
    While I continue to use the default Gnome Shell desktop on 18.04 LTS locally, it no longer works as a remote desktop. For remote sessions I specify [fvwm](https://fvwm.org) in my xstartup file (fvwm is slightly better than the even older twm). This has the advantage of using a lot less bandwidth and makes things more responsive over the network. Since my personal use of remote desktop sessions is to manage servers, the lack of a full desktop experience is not a drawback for me.

    1. Install fvwm and xterm:

  12. @plembo plembo revised this gist Apr 22, 2020. 1 changed file with 33 additions and 20 deletions.
    53 changes: 33 additions & 20 deletions tigervnconubuntu.md
    View file
    Original file line number Diff line number Diff line change
    @@ -51,12 +51,7 @@ $ sudo tar czf local.tgz local
    $ sudo tar xzf local.tgz -C /usr/
    ```

    8. Update the system icon cache:

    ```
    $ sudo update-icon-caches /usr/local/share/icons/*
    ```
    9. Double check that the binaries are where they should be:
    8. In a different console, double check that the binaries are where they should be:

    ```bash
    $ which vncserver
    @@ -65,25 +60,29 @@ $ which vncviewer
    /usr/local/bin/vncviewer
    ```

    10. Run vncserver and vncviewer to ensure they are working:
    9. Run vncserver and vncviewer as an ordinary user just to ensure they are working:

    ```
    $ vncserver :2
    ...
    $ vncviewer localhost :2
    New 'test002:2 (plembo)' desktop is test002:2
    Starting applications specified in /home/plembo/.vnc/xstartup
    Log file is /home/plembo/.vnc/test002:2.log
    ```
    I now always specify a vnc port, as the default (":1") sometimes conflicts with other services. Note that the standard vnc ports start at TCP 5900, so ":2" is actually TCP 5902. In the event of a conflict, you can use [lsof](https://manpages.ubuntu.com/manpages/bionic/man8/lsof.8.html) to find what other processes may be using those ports:

    ```bash
    $ lsof -i :5902
    COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
    Xvnc 24358 plembo 6u IPv4 8362514 0t0 TCP *:5902 (LISTEN)
    Xvnc 24358 plembo 7u IPv6 8362515 0t0 TCP *:5902 (LISTEN)
    Kill the remote session once done testing:

    ```
    $ vncserver -kill :2
    ```
    10. Update the system icon cache:

    Also, you'll be invited to set a password upon starting vncserver: do it!
    ```
    $ sudo update-icon-caches /usr/local/share/icons/*
    ```

    11. Create new xstartup under .vnc to use default Gnome desktop:
    11. Create a new xstartup under .vnc (in the home directory of the user who will be launching remote sessions) to use fvwm as the remote desktop:

    ```
    #!/bin/sh
    @@ -94,6 +93,20 @@ xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
    LANG=C fvwm &
    ```

    The main problem I have with this is that tigervnc doesn't support multiple monitors. This
    becomes a problem when you launch and app and it pops up in the other monitor, preventing
    you from even seeing it is running.
    12. Now run vncserver again, and view the remote desktop with vncviewer (entering the remote password chosen previously).

    A few additional notes:

    * You'll be invited to set a password the first time you run vncserver: do it! For the current version of TigerVNC, passwords are limited to 8 characters.Remember, the vnc server is _not_ integrated with your host's authentication system: that password is the only thing that keeps outsiders from getting into an existing session.
    * While you can certainly launch a vnc session as root, it is _not_ recommended.
    * TigerVNC does not support multiple monitors. If you're using fvwm as your remote desktop that won't be a problem: fvwm doesn't support multiple monitors either!
    * Try to remember to kill your remote session when done, unless you _really_ want to have Firefox open on a server for 465 days.
    * That said, remote vnc sessions _can_ be an alternative to managing processes that you might otherwise have to launch in the background, or with services or applications that can't be controlled from the command line.
    * I now always specify a vnc port, as the default (":1") sometimes conflicts with other services. The standard vnc ports start at TCP 5900, so ":2" is actually TCP 5902. In the event of a conflict, you can use [lsof](https://manpages.ubuntu.com/manpages/bionic/man8/lsof.8.html) to find what other processes may be using those ports:

    ```bash
    $ lsof -i :5902
    COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
    Xvnc 24358 plembo 6u IPv4 8362514 0t0 TCP *:5902 (LISTEN)
    Xvnc 24358 plembo 7u IPv6 8362515 0t0 TCP *:5902 (LISTEN)
    ```
  13. @plembo plembo revised this gist Apr 22, 2020. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion tigervnconubuntu.md
    View file
    Original file line number Diff line number Diff line change
    @@ -72,7 +72,7 @@ $ vncserver :2
    ...
    $ vncviewer localhost :2
    ```
    I now always specify a vnc port, as the default (":1") sometimes conflicts with other services. Note that the standard vnc ports start at TCP 5900, so ":2" is actually TCP 5902. In the event of a conflict, you use [lsof](https://manpages.ubuntu.com/manpages/bionic/man8/lsof.8.html) to find what other processes may be using those ports:
    I now always specify a vnc port, as the default (":1") sometimes conflicts with other services. Note that the standard vnc ports start at TCP 5900, so ":2" is actually TCP 5902. In the event of a conflict, you can use [lsof](https://manpages.ubuntu.com/manpages/bionic/man8/lsof.8.html) to find what other processes may be using those ports:

    ```bash
    $ lsof -i :5902
  14. @plembo plembo revised this gist Apr 22, 2020. 1 changed file with 9 additions and 2 deletions.
    11 changes: 9 additions & 2 deletions tigervnconubuntu.md
    View file
    Original file line number Diff line number Diff line change
    @@ -72,9 +72,16 @@ $ vncserver :2
    ...
    $ vncviewer localhost :2
    ```
    I now always specify a vnc port, as the default (":1") sometimes conflicts with other services.
    I now always specify a vnc port, as the default (":1") sometimes conflicts with other services. Note that the standard vnc ports start at TCP 5900, so ":2" is actually TCP 5902. In the event of a conflict, you use [lsof](https://manpages.ubuntu.com/manpages/bionic/man8/lsof.8.html) to find what other processes may be using those ports:

    Also, you'll be invited to set a password upon starting vncserver: Do it!
    ```bash
    $ lsof -i :5902
    COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
    Xvnc 24358 plembo 6u IPv4 8362514 0t0 TCP *:5902 (LISTEN)
    Xvnc 24358 plembo 7u IPv6 8362515 0t0 TCP *:5902 (LISTEN)
    ```

    Also, you'll be invited to set a password upon starting vncserver: do it!

    11. Create new xstartup under .vnc to use default Gnome desktop:

  15. @plembo plembo revised this gist Apr 22, 2020. 1 changed file with 4 additions and 2 deletions.
    6 changes: 4 additions & 2 deletions tigervnconubuntu.md
    View file
    Original file line number Diff line number Diff line change
    @@ -68,11 +68,13 @@ $ which vncviewer
    10. Run vncserver and vncviewer to ensure they are working:

    ```
    $ vncserver
    $ vncserver :2
    ...
    $ vncviewer localhost :2
    ```
    You'll be invited to set a password upon starting vncserver: Do it!
    I now always specify a vnc port, as the default (":1") sometimes conflicts with other services.

    Also, you'll be invited to set a password upon starting vncserver: Do it!

    11. Create new xstartup under .vnc to use default Gnome desktop:

  16. @plembo plembo revised this gist Apr 22, 2020. 1 changed file with 1 addition and 0 deletions.
    1 change: 1 addition & 0 deletions tigervnconubuntu.md
    View file
    Original file line number Diff line number Diff line change
    @@ -78,6 +78,7 @@ You'll be invited to set a password upon starting vncserver: Do it!

    ```
    #!/bin/sh
    # xstartup to launch fvwm desktop session
    xsetroot -solid '#222E45'
    vncconfig -iconic &
    xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
  17. @plembo plembo revised this gist Apr 22, 2020. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion tigervnconubuntu.md
    View file
    Original file line number Diff line number Diff line change
    @@ -3,7 +3,7 @@ This is for Ubuntu 18.04 LTS. [TigerVNC](https://tigervnc.org) is a remote deskt

    There are packages for tigervnc in the repositories of the major distributions, but the latest versions for Ubuntu are broken. My workaround is to use the latest stable version from the TigerVNC project Github [release page](https://github.com/TigerVNC/tigervnc/releases), where generic binaries for 32 and 64-bit Linux are distributed as tarballs (dmg and exe installers for Mac and Windows are also available).

    While I continue to use the default Gnome desktop on 18.04 LTS locally, that no longer works as a remote desktop. For remote sessions I specify [fvwm](https://fvwm.org) in my xstartup file (fvwm is slightly better than twm). This has the advantage of using a lot less bandwidth and makes things more responsive over the network.
    While I continue to use the default Gnome desktop on 18.04 LTS locally, that no longer works as a remote desktop. For remote sessions I specify [fvwm](https://fvwm.org) in my xstartup file (fvwm is slightly better than twm). This has the advantage of using a lot less bandwidth and makes things more responsive over the network. Since my personal use of remote desktop is to manage servers, the lack of a full desktop experience is not a drawback for me.

    1. Install fvwm and xterm:

  18. @plembo plembo revised this gist Apr 22, 2020. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion tigervnconubuntu.md
    View file
    Original file line number Diff line number Diff line change
    @@ -72,7 +72,7 @@ $ vncserver
    ...
    $ vncviewer localhost :2
    ```
    You'll be invited to add a password after starting vncserver: Do it!
    You'll be invited to set a password upon starting vncserver: Do it!

    11. Create new xstartup under .vnc to use default Gnome desktop:

  19. @plembo plembo revised this gist Apr 22, 2020. 1 changed file with 2 additions and 0 deletions.
    2 changes: 2 additions & 0 deletions tigervnconubuntu.md
    View file
    Original file line number Diff line number Diff line change
    @@ -69,8 +69,10 @@ $ which vncviewer

    ```
    $ vncserver
    ...
    $ vncviewer localhost :2
    ```
    You'll be invited to add a password after starting vncserver: Do it!

    11. Create new xstartup under .vnc to use default Gnome desktop:

  20. @plembo plembo revised this gist Apr 22, 2020. 1 changed file with 0 additions and 1 deletion.
    1 change: 0 additions & 1 deletion tigervnconubuntu.md
    View file
    Original file line number Diff line number Diff line change
    @@ -61,7 +61,6 @@ $ sudo update-icon-caches /usr/local/share/icons/*
    ```bash
    $ which vncserver
    /usr/local/bin/vncserver
    $
    $ which vncviewer
    /usr/local/bin/vncviewer
    ```
  21. @plembo plembo revised this gist Apr 22, 2020. 1 changed file with 0 additions and 1 deletion.
    1 change: 0 additions & 1 deletion tigervnconubuntu.md
    View file
    Original file line number Diff line number Diff line change
    @@ -42,7 +42,6 @@ $ sudo chown -R root:root usr
    ```
    $ sudo mv usr local
    ```

    7. Then copy the binaries to their respective locations:

    NOTE: Before you do this, set perms as indicated in previous step!
  22. @plembo plembo revised this gist Apr 22, 2020. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion tigervnconubuntu.md
    View file
    Original file line number Diff line number Diff line change
    @@ -57,7 +57,7 @@ $ sudo tar xzf local.tgz -C /usr/
    ```
    $ sudo update-icon-caches /usr/local/share/icons/*
    ```
    9. Make sure the binaries are where they should be:
    9. Double check that the binaries are where they should be:

    ```bash
    $ which vncserver
  23. @plembo plembo revised this gist Apr 22, 2020. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion tigervnconubuntu.md
    View file
    Original file line number Diff line number Diff line change
    @@ -3,7 +3,7 @@ This is for Ubuntu 18.04 LTS. [TigerVNC](https://tigervnc.org) is a remote deskt

    There are packages for tigervnc in the repositories of the major distributions, but the latest versions for Ubuntu are broken. My workaround is to use the latest stable version from the TigerVNC project Github [release page](https://github.com/TigerVNC/tigervnc/releases), where generic binaries for 32 and 64-bit Linux are distributed as tarballs (dmg and exe installers for Mac and Windows are also available).

    While I continue to use the default Gnome desktop on 18.04 LTS locally, that no longer works as a remote desktop. For remote sessions I use [fvwm](https://fvwm.org) (fvwm is slightly better than twm). This has the advantage of using a lot less bandwidth and makes things more responsive over the network.
    While I continue to use the default Gnome desktop on 18.04 LTS locally, that no longer works as a remote desktop. For remote sessions I specify [fvwm](https://fvwm.org) in my xstartup file (fvwm is slightly better than twm). This has the advantage of using a lot less bandwidth and makes things more responsive over the network.

    1. Install fvwm and xterm:

  24. @plembo plembo revised this gist Apr 22, 2020. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion tigervnconubuntu.md
    View file
    Original file line number Diff line number Diff line change
    @@ -3,7 +3,7 @@ This is for Ubuntu 18.04 LTS. [TigerVNC](https://tigervnc.org) is a remote deskt

    There are packages for tigervnc in the repositories of the major distributions, but the latest versions for Ubuntu are broken. My workaround is to use the latest stable version from the TigerVNC project Github [release page](https://github.com/TigerVNC/tigervnc/releases), where generic binaries for 32 and 64-bit Linux are distributed as tarballs (dmg and exe installers for Mac and Windows are also available).

    While I continue to use the default Gnome desktop on 18.04 LTS locally, that no longer works as a virtual desktop. For remote sessions I use [fvwm](https://fvwm.org) (fvwm is slightly better than twm). This has the advantage of using a lot less bandwidth and makes things more responsive over the network.
    While I continue to use the default Gnome desktop on 18.04 LTS locally, that no longer works as a remote desktop. For remote sessions I use [fvwm](https://fvwm.org) (fvwm is slightly better than twm). This has the advantage of using a lot less bandwidth and makes things more responsive over the network.

    1. Install fvwm and xterm:

  25. @plembo plembo revised this gist Apr 22, 2020. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion tigervnconubuntu.md
    View file
    Original file line number Diff line number Diff line change
    @@ -3,7 +3,7 @@ This is for Ubuntu 18.04 LTS. [TigerVNC](https://tigervnc.org) is a remote deskt

    There are packages for tigervnc in the repositories of the major distributions, but the latest versions for Ubuntu are broken. My workaround is to use the latest stable version from the TigerVNC project Github [release page](https://github.com/TigerVNC/tigervnc/releases), where generic binaries for 32 and 64-bit Linux are distributed as tarballs (dmg and exe installers for Mac and Windows are also available).

    While I continue to use the default Gnome desktop on 18.04 LTS locally, that no longer works as the virtual desktop. For remote sessions I use [fvwm](https://fvwm.org) (fvwm is slightly better than twm). This has the advantage of using a lot less bandwidth and makes things more responsive over the network.
    While I continue to use the default Gnome desktop on 18.04 LTS locally, that no longer works as a virtual desktop. For remote sessions I use [fvwm](https://fvwm.org) (fvwm is slightly better than twm). This has the advantage of using a lot less bandwidth and makes things more responsive over the network.

    1. Install fvwm and xterm:

  26. @plembo plembo revised this gist Apr 22, 2020. 1 changed file with 1 addition and 3 deletions.
    4 changes: 1 addition & 3 deletions tigervnconubuntu.md
    View file
    Original file line number Diff line number Diff line change
    @@ -3,9 +3,7 @@ This is for Ubuntu 18.04 LTS. [TigerVNC](https://tigervnc.org) is a remote deskt

    There are packages for tigervnc in the repositories of the major distributions, but the latest versions for Ubuntu are broken. My workaround is to use the latest stable version from the TigerVNC project Github [release page](https://github.com/TigerVNC/tigervnc/releases), where generic binaries for 32 and 64-bit Linux are distributed as tarballs (dmg and exe installers for Mac and Windows are also available).

    This no longer works with the default Gnome desktop for 18.04 LTS. I use [fvwm](https://fvwm.org) and xterm instead (fvwm is slightly better than twm).

    Finally, this requires the standard X server to work. It may not work under Wayland.
    While I continue to use the default Gnome desktop on 18.04 LTS locally, that no longer works as the virtual desktop. For remote sessions I use [fvwm](https://fvwm.org) (fvwm is slightly better than twm). This has the advantage of using a lot less bandwidth and makes things more responsive over the network.

    1. Install fvwm and xterm:

  27. @plembo plembo revised this gist Apr 22, 2020. 1 changed file with 37 additions and 18 deletions.
    55 changes: 37 additions & 18 deletions tigervnconubuntu.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,41 +1,51 @@
    # Installing TigerVNC on Ubuntu
    This is for Ubuntu 18.04 LTS. [TigerVNC](https://tigervnc.org) is a remote desktop server and viewer solution sponsored by
    [Red Hat](https://www.redhat.com) that is still in active development. There are packages for it in the repositories of the
    major distributions, but the latest versions for Ubuntu are broken. My workaround is to use the latest stable version from the TigerVNC project Github [release page](https://github.com/TigerVNC/tigervnc/releases), where generic binaries for 32 and 64-bit Linux are distributed as tarballs (dmg and exe installers for Mac and Windows are also available).
    This is for Ubuntu 18.04 LTS. [TigerVNC](https://tigervnc.org) is a remote desktop server and viewer solution sponsored by [Red Hat](https://www.redhat.com) that is still in active development. While I recently tested under Ubuntu 19.10, I have no plans to test non-LTS versions in the future.

    1. Remove any pre-existing vnc software, like RealVNC 4:
    There are packages for tigervnc in the repositories of the major distributions, but the latest versions for Ubuntu are broken. My workaround is to use the latest stable version from the TigerVNC project Github [release page](https://github.com/TigerVNC/tigervnc/releases), where generic binaries for 32 and 64-bit Linux are distributed as tarballs (dmg and exe installers for Mac and Windows are also available).

    This no longer works with the default Gnome desktop for 18.04 LTS. I use [fvwm](https://fvwm.org) and xterm instead (fvwm is slightly better than twm).

    Finally, this requires the standard X server to work. It may not work under Wayland.

    1. Install fvwm and xterm:

    ```bash
    $ sudo apt install fvwm xterm
    ```

    2. Remove any pre-existing vnc software, like RealVNC 4:

    ```
    $ sudo apt remove --purge vnc4server xvnc4viewer
    $ sudo aptautoremove
    $ sudo apt autoremove
    ```

    2. Download the latest release archive:
    3. Download the latest release archive:

    ```
    $ wget https://bintray.com/tigervnc/stable/download_file?file_path=tigervnc-1.9.0.x86_64.tar.gz -O tigervnc-1.9.0.x86_64.tar.gz
    ```

    3. Unarchive the file:
    4. Unarchive the file:

    ```
    $ tar xzf tigervnc-1.9.0.x86_64.tar.gz
    ```

    4. IMPORTANT! Set permissions on usr subdirectory of extracted files:
    5. IMPORTANT! Set permissions on usr subdirectory of extracted files:

    ```
    $ cd tigervnc-1.9.0.x86_64
    $ sudo chown -R root:root usr
    ```

    5. By default everything gets installed to /usr. Change this to /usr/local (because we _never_ mess with /usr):
    6. By default everything gets installed to /usr. Change this to /usr/local (because we _never_ mess with /usr):

    ```
    $ sudo mv usr local
    ```

    6. Then copy the binaries to their respective locations:
    7. Then copy the binaries to their respective locations:

    NOTE: Before you do this, set perms as indicated in previous step!

    @@ -44,29 +54,38 @@ $ sudo tar czf local.tgz local
    $ sudo tar xzf local.tgz -C /usr/
    ```

    7 Update the system icon cache:
    8. Update the system icon cache:

    ```
    $ sudo update-icon-caches /usr/local/share/icons/*
    ```
    9. Make sure the binaries are where they should be:

    ```bash
    $ which vncserver
    /usr/local/bin/vncserver
    $
    $ which vncviewer
    /usr/local/bin/vncviewer
    ```

    8 Run vncserver and vncviewer to ensure they are working:
    10. Run vncserver and vncviewer to ensure they are working:

    ```
    $ vncserver
    $ vncviewer localhost :1
    $ vncviewer localhost :2
    ```

    9 Create new xstartup under .vnc to use standard gnome desktop:
    11. Create new xstartup under .vnc to use default Gnome desktop:

    ```
    #!/bin/sh
    # Start Gnome 3 Desktop
    [ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup
    [ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
    xsetroot -solid '#222E45'
    vncconfig -iconic &
    dbus-launch --exit-with-session gnome-session &
    xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
    LANG=C fvwm &
    ```

    The main problem I have with this is that tigervnc doesn't support multiple monitors. This
    becomes a problem when you launch and app and it pops up in the other monitor, preventing
    you from even seeing it is running.
  28. @plembo plembo revised this gist Jul 8, 2019. 1 changed file with 5 additions and 5 deletions.
    10 changes: 5 additions & 5 deletions tigervnconubuntu.md
    View file
    Original file line number Diff line number Diff line change
    @@ -35,29 +35,29 @@ $ sudo chown -R root:root usr
    $ sudo mv usr local
    ```

    Then copy the binaries to their respective locations:
    6. Then copy the binaries to their respective locations:

    NOTE: Before you do this, set perms as indicated in previous step!

    ```
    $ tar czf local.tgz local
    $ sudo tar czf local.tgz local
    $ sudo tar xzf local.tgz -C /usr/
    ```

    6. Update the system icon cache:
    7 Update the system icon cache:

    ```
    $ sudo update-icon-caches /usr/local/share/icons/*
    ```

    7. Run vncserver and vncviewer to ensure they are working:
    8 Run vncserver and vncviewer to ensure they are working:

    ```
    $ vncserver
    $ vncviewer localhost :1
    ```

    8. Create new xstartup under .vnc to use standard gnome desktop:
    9 Create new xstartup under .vnc to use standard gnome desktop:

    ```
    #!/bin/sh
  29. @plembo plembo revised this gist Jul 8, 2019. 1 changed file with 11 additions and 5 deletions.
    16 changes: 11 additions & 5 deletions tigervnconubuntu.md
    View file
    Original file line number Diff line number Diff line change
    @@ -29,19 +29,25 @@ $ cd tigervnc-1.9.0.x86_64
    $ sudo chown -R root:root usr
    ```

    5. Copy the binaries to their respective locations:
    5. By default everything gets installed to /usr. Change this to /usr/local (because we _never_ mess with /usr):

    ```
    $ sudo mv usr local
    ```

    Then copy the binaries to their respective locations:

    NOTE: Before you do this, set perms as indicated in previous step!

    ```
    $ tar czf usr.tgz usr
    $ sudo tar xzf usr.tgz -C /
    $ tar czf local.tgz local
    $ sudo tar xzf local.tgz -C /usr/
    ```

    6. Update the system icon caches:
    6. Update the system icon cache:

    ```
    $ sudo update-icon-caches /usr/share/icons/*
    $ sudo update-icon-caches /usr/local/share/icons/*
    ```

    7. Run vncserver and vncviewer to ensure they are working:
  30. @plembo plembo revised this gist May 11, 2019. 1 changed file with 12 additions and 4 deletions.
    16 changes: 12 additions & 4 deletions tigervnconubuntu.md
    View file
    Original file line number Diff line number Diff line change
    @@ -22,28 +22,36 @@ $ wget https://bintray.com/tigervnc/stable/download_file?file_path=tigervnc-1.9.
    $ tar xzf tigervnc-1.9.0.x86_64.tar.gz
    ```

    4. Copy the binaries to their respective locations:
    4. IMPORTANT! Set permissions on usr subdirectory of extracted files:

    ```
    $ cd tigervnc-1.9.0.x86_64
    $ sudo chown -R root:root usr
    ```

    5. Copy the binaries to their respective locations:

    NOTE: Before you do this, set perms as indicated in previous step!

    ```
    $ tar czf usr.tgz usr
    $ sudo tar xzf usr.tgz -C /
    ```

    5. Update the system icon caches:
    6. Update the system icon caches:

    ```
    $ sudo update-icon-caches /usr/share/icons/*
    ```

    6. Run vncserver and vncviewer to ensure they are working:
    7. Run vncserver and vncviewer to ensure they are working:

    ```
    $ vncserver
    $ vncviewer localhost :1
    ```

    7. Create new xstartup under .vnc to use standard gnome desktop:
    8. Create new xstartup under .vnc to use standard gnome desktop:

    ```
    #!/bin/sh