Ran 'do-release-upgrade' and now TigerVNC won't run....

Bo Berglund bo.berglund at gmail.com
Mon Mar 13 22:11:13 UTC 2023


On Mon, 13 Mar 2023 13:20:40 -0400, Jeffrey Walton <noloader at gmail.com> wrote:

>On Mon, Mar 13, 2023 at 1:07?PM Bo Berglund <bo.berglund at gmail.com> wrote:
>> [...]
>> What exactly should be changed from what I had on Ubuntu 20.04???
>> What is the problem with the display, isn't it supposed to create a virtual
>> display when one uses argument :1???
>
>Did you take the Maintainer's copy of vncserver's config file when
>upgrading from 20.04 to 22.04? Your copy should be in /etc with the
>*.saved extension. You should be able to diff it to see the changes.

Well, I did not "take" anything, I just ran the do-release-upgrade which
continued for about an hour or so.
Loads of lines streaming past on the screen.

When I diff the two files vnc.conf.dpkg-bak and vnc.conf
they are exactly the same...

Active (non-commented) content of /etc/vnc.conf:
-----------------------
$fontPath = undef;
$vncStartup = "/etc/X11/Xvnc-session";
$geometry = "1600x900";
$localhost = "no";
$PlainUsers = "bosse";
1;
-----------------------

(I have no idea what the 1; on the last line does....)
Notice the geometry and compare to the error message below!

Also this is the service file /etc/systemd/system/vncserver at .service :
-----------------------
[Unit]
Description=Systemd TigerVNC server startup script for Ubuntu 22.04
After=syslog.target network.target

[Service]
Type=forking
User=bosse
ExecStartPre=-/usr/bin/vncserver -kill :%i &> /dev/null
ExecStart=/usr/bin/vncserver -depth 24 -localhost no -geometry 1680x1040 :%i
PIDFile=/home/bosse/.vnc/%H:%i.pid
ExecStop=/usr/bin/vncserver -kill :%i

[Install]
WantedBy=multi-user.target
-----------------------

(Again the same geometry is repeated here)

Another file:

~/.vnc/xstartup contains this:
-----------------------
#!/bin/sh
# Uncomment the following two lines for normal desktop:
unset DBUS_SESSION_BUS_ADDRESS
unset SESSION_MANAGER
# exec /etc/X11/xinit/xinitrc
[ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup
[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
xsetroot -solid grey
vncconfig -iconic &
x-terminal-emulator -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
x-window-manager &
mate-session &
-----------------------


NOTE:
VNC worked fine prior to the upgrade, earlier today.

>If you took the Maintainer's copy, or if there are no changes, then I
>would try a reinstall to see if the ship rights itself:
>
>    sudo apt-get install --reinstall <vnc packages>

I did this:
   sudo apt-get install --reinstall tigervnc-standalone-server

And I also rebooted for good measure.
Still exactly the same non-behaviour.

This is what is shown when I check the status:

-----------------------
$ sudo systemctl status vncserver at 1.service

× vncserver at 1.service - Systemd TigerVNC server startup script for Ubuntu 22.04
     Loaded: loaded (/etc/systemd/system/vncserver at .service; enabled; vendor
preset: enabled)
     Active: failed (Result: exit-code) since Mon 2023-03-13 17:40:22 CET; 23s
ago
    Process: 6202 ExecStartPre=/usr/bin/vncserver -kill :1 &> /dev/null
(code=exited, status=255/EXCEPTION)
    Process: 6206 ExecStart=/usr/bin/vncserver -depth 24 -localhost no -geometry
1680x1040 :1 (code=exited, status=255/EXCEPTION)

mar 13 17:40:22 polaris-ubuntu vncserver[6212]:
=====================================================================================
mar 13 17:40:22 polaris-ubuntu vncserver[6212]: Session startup via
'/home/bosse/.vnc/xstartup' cleanly exited too early (< 3 seconds)!
-----------------------

Hope it can be solved somehow, because I have som development stuff in there
which I occationally need to use, but via the network...


-- 
Bo Berglund
Developer in Sweden





More information about the ubuntu-users mailing list