TigerVNC server not working after do_release_upgrade to 22.04.4 LTS

[Bo Berglund]

On Wed, 20 Mar 2024 20:35:00 -0400, Sam Varshavchik <mrsam at courier-mta.com>
wrote:

>Bo Berglund writes:
>
>> After the upgrade/reboot I can no longer access the VNC functionality!
>> The client  (RealVNC-Viewer on Windows 10) just hangs and never connects, so  
>> I
>> checked the laptop status:
>> ---------------------
>> sudo systemctl status vncserver at 1
>
>Did 22.04 install this systemd service for vncserver? I don't have this in  
>20.04, I just run vncserver manually.

The service was installed back in the 20.04 version and was transfered in the
dist-upgrade I did yesterday.
It tries to run but the vncserver exits with an error early on as can be seen in
the journal.
My problem is to understand why it fails and remedy it...

>Are you also logged in on the console, by any chance. If so try logging off  
>the console before attempting a VNC connection. Fedora has a known  
>limitation with being unable to support both a console session and a VNC  
>session for the same user at the same time, with its systemd-launched  
>vncserver.

The laptop is running headless (no attached monitor) and the lid closed, so
there is no hardware screen attached.
The VNC service is set to use screen #1 rather than #0, and that virtual screen
is suppopsed to be created by running vncserver with the argument 1 for the
screen.

I am only connected to the laptop using PuTTY (SSH connection) so I am on a
terminal but only via SSH, so not the "real" terminal...
And I am not running Fedora, this is Ubuntu 20.04 using Cinnamon upgraded to
22.04.

What happened in the upgrade I don't know, something not good for VNC seems to
have occurred.


-- 
Bo Berglund
Developer in Sweden