How to *completely* remove tigervnc server from Ubuntu 22.04?

[Bo Berglund]

As can be seen by another thread I am having BIG problems making TigerVNC server
work on my Ubuntu system. It runs the mate desktop.

It was upgraded from 20.04 to 22.04 using the "do-release-upgrade" command via
SSH and most things seemed to work, except for the tigervnc server.

Using ssh I can interact with it on the command line and if I use the display on
the laptop itself I can run my GUI programs (mostly a software dev IDE).

TigerVNC server was installed in 20.04 using the apt command and its current
status now is:

$ apt policy tigervnc-standalone-server
tigervnc-standalone-server:
  Installed: 1.12.0+dfsg-4
  Candidate: 1.12.0+dfsg-4
  Version table:
 *** 1.12.0+dfsg-4 500
        500 http://se.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
        100 /var/lib/dpkg/status

Since I have tried everything I can think of to make it run but it still fails
every time, I need to totally purge it from my system so I can re-install it
clean afterwards and hopefully it will work better then.

The installation was done once upon a time using this (according to my notes):

sudo apt install tigervnc-standalone-server

After that a number of config files were created/edited as follows:
/etc/vnc.conf
~/.vnc/xstartup
/etc/systemd/system/vncserver at .service

The logon password was set by running this command:
vncserver :1

which shows a dialog to enter the connection password.

Then the service was enabled and started like this:

sudo systemctl enable vncserver at 1
sudo systemctl start vncserver at 1

And this is now *not* working, the service exits immediately upon start...

So I have the following potential commands to get rid of tigervnc:

sudo systemctl disable vncserver at 1

sudo apt remove tigervnc-standalone-server

sudo apt purge tigervnc-standalone-server

sudo apt autoremove

sudo reboot

But will this also handle all of the config files or do I have to manually find
and delete them before I make an attempt at installing it all over from scratch?

Or is there some other method to get it going again?

Grateful for advice since this is a show-stopper for me...


-- 
Bo Berglund
Developer in Sweden