Unable to launch Tiger VNC Viewer

[sanchit relan]

Hi,

I recently rebooted my machine after which I am unable to start VNC viewer service. Below I have attached the error :-

● vncserver@:1.service - Remote desktop service (VNC)
   Loaded: loaded (/etc/systemd/system/vncserver@:1.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Mon 2022-01-17 01:35:15 EST; 4min 45s ago
  Process: 24405 ExecStart=/sbin/runuser -l root -c /usr/bin/vncserver %i -geometry 1280x1024 (code=exited, status=255)
  Process: 24402 ExecStartPre=/bin/sh -c /usr/bin/vncserver -kill %i > /dev/null 2>&1 || : (code=exited, status=0/SUCCESS)
 Main PID: 3848 (code=exited, status=2)

Jan 17 01:35:15 osboxes runuser[24405]: must supply to access the server (default=)
Jan 17 01:35:15 osboxes runuser[24405]: rfbauth        - Alias for PasswordFile
Jan 17 01:35:15 osboxes runuser[24405]: PasswordFile   - Password file for VNC authentication (default=)
Jan 17 01:35:15 osboxes runuser[24405]: SecurityTypes  - Specify which security scheme to use (None, VncAuth, Plain,
Jan 17 01:35:15 osboxes runuser[24405]: TLSNone, TLSVnc, TLSPlain, X509None, X509Vnc, X509Plain)
Jan 17 01:35:15 osboxes runuser[24405]: (default=TLSVnc,VncAuth)
Jan 17 01:35:15 osboxes runuser[24405]: (EE)
Jan 17 01:35:15 osboxes runuser[24405]: Fatal server error:
Jan 17 01:35:15 osboxes runuser[24405]: (EE) Unrecognized option: -session
Jan 17 01:35:15 osboxes runuser[24405]: (EE)

Thanks and Regards

Sanchit

[Pierre Ossman]

On 17/01/2022 07:42, sanchit relan wrote:
> Jan 17 01:35:15 osboxes runuser[24405]: Fatal server error:
> Jan 17 01:35:15 osboxes runuser[24405]: (EE) Unrecognized option: -session
> Jan 17 01:35:15 osboxes runuser[24405]: (EE)
>

It looks like there is some mixup between an old and new version of
TigerVNC here.

What version of TigerVNC is used here? And how was it set up?

Regards
--
Pierre Ossman Software Development
Cendio AB https://cendio.com
Teknikringen 8 https://twitter.com/ThinLinc
583 30 Linköping https://facebook.com/ThinLinc
Phone: +46-13-214600

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

[sanchit relan]

I have tigervnc-server-1.8.0-22.el7.x86_64 installed on my machine. other related packages are :-

tigervnc-icons-1.8.0-22.el7.noarch
tigervnc-license-1.8.0-13.el7.noarch
tigervnc-server-minimal-1.8.0-22.el7.x86_64

[Pierre Ossman]

On 17/01/2022 12:29, sanchit relan wrote:
> I have tigervnc-server-1.8.0-22.el7.x86_64 installed on my machine. other
> related packages are :-
> tigervnc-icons-1.8.0-22.el7.noarch
> tigervnc-license-1.8.0-13.el7.noarch
> tigervnc-server-minimal-1.8.0-22.el7.x86_64

That's an older version of TigerVNC. You should not include a "session"
option for that version. If you remove that then it should be able to
start correctly.

[sanchit relan]

I updated the TigerVNC to 1.12. I am still facing the issue :-

[root@osboxes package-setups]# systemctl start vncserver@:2
[root@osboxes package-setups]# systemctl status vncserver@:2
● vncserver@:2.service - Remote desktop service (VNC)
   Loaded: loaded (/etc/systemd/system/vncserver@:2.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Tue 2022-01-18 02:49:25 EST; 7s ago
  Process: 25662 ExecStop=/bin/sh -c /usr/bin/vncserver -kill %i > /dev/null 2>&1 || : (code=exited, status=0/SUCCESS)
  Process: 25658 ExecStart=/usr/bin/vncserver_wrapper root %i (code=exited, status=203/EXEC)
  Process: 25655 ExecStartPre=/bin/sh -c /usr/bin/vncserver -kill %i > /dev/null 2>&1 || : (code=exited, status=0/SUCCESS)
 Main PID: 25658 (code=exited, status=203/EXEC)

Jan 18 02:49:24 osboxes systemd[1]: Starting Remote desktop service (VNC)...
Jan 18 02:49:24 osboxes systemd[1]: Started Remote desktop service (VNC).
Jan 18 02:49:24 osboxes systemd[1]: vncserver@:2.service: main process exited, code=exited, status=203/EXEC
Jan 18 02:49:25 osboxes systemd[1]: Unit vncserver@:2.service entered failed state.
Jan 18 02:49:25 osboxes systemd[1]: vncserver@:2.service failed.

[Pierre Ossman]

On 18/01/2022 09:19, sanchit relan wrote:
> I updated the TigerVNC to 1.12. I am still facing the issue :-
>
> [root@osboxes package-setups]# systemctl start vncserver@:2
> [root@osboxes package-setups]# systemctl status vncserver@:2
> ● vncserver@:2.service - Remote desktop service (VNC)
> Loaded: loaded (/etc/systemd/system/vncserver@:2.service; enabled;
> vendor preset: disabled)
> Active: failed (Result: exit-code) since Tue 2022-01-18 02:49:25 EST; 7s
> ago
> Process: 25662 ExecStop=/bin/sh -c /usr/bin/vncserver -kill %i >
> /dev/null 2>&1 || : (code=exited, status=0/SUCCESS)
> Process: 25658 ExecStart=/usr/bin/vncserver_wrapper root %i (code=exited,
> status=203/EXEC)
> Process: 25655 ExecStartPre=/bin/sh -c /usr/bin/vncserver -kill %i >
> /dev/null 2>&1 || : (code=exited, status=0/SUCCESS)
> Main PID: 25658 (code=exited, status=203/EXEC)
>

The mixup is now the other way around. This service file is an old
service file and not the one included with TigerVNC 1.12. I'm not sure
how the previous one got installed, but please make sure it gets
replaced with the one included with TigerVNC.