Arch Linux

dave.computer

Member

Registered: 2012-10-23

Posts: 15

vncserver@:1.service starts and then stops immediately

Hi Everyone,

When I run:

sudo systemctl start vncserver@:1.service

I expect a vnc server to be listening on port 5901. This isn't happening.

When I run:

sudo systemctl status vncserver@:1.service

the output is:

○ vncserver@:1.service - Remote desktop service (VNC)
     Loaded: loaded (/usr/lib/systemd/system/vncserver@.service; enabled; vendor preset: disabled)
     Active: inactive (dead) since Sun 2022-01-02 23:48:29 PST; 2min 51s ago
    Process: 3608 ExecStart=/usr/bin/vncsession-start :1 (code=exited, status=0/SUCCESS)
   Main PID: 3615 (code=exited, status=0/SUCCESS)
        CPU: 22ms

Jan 02 23:48:29 Mossy systemd[1]: Starting Remote desktop service (VNC)...
Jan 02 23:48:29 Mossy systemd[1]: Started Remote desktop service (VNC).
Jan 02 23:48:29 Mossy systemd[1]: vncserver@:1.service: Deactivated successfully.

Lacking any error messages to work with, where should I look for clues?

Thanks for your help,
Dave

hiho

Member

Registered: 2016-10-03

Posts: 1

Re: vncserver@:1.service starts and then stops immediately

~/.vnc/*.log

There should be a file named '<hostname>:1.log'.

dave.computer

Member

Registered: 2012-10-23

Posts: 15

Re: vncserver@:1.service starts and then stops immediately

There is a log:

[dave@Mossy ~]$ cat .vnc/Mossy\:1.log 
VNC authentication enabled, but no password file created.

I'm trying to vnc through ssh, as described in the wiki for TigerVNC. I have not been able to make a vnc connection because I can't get the vnc server to stay running.

marneylc

Member

Registered: 2025-01-21

Posts: 1

Re: vncserver@:1.service starts and then stops immediately

Don't want to necrobump this thread, but for me I just had to run the following WITHOUT sudo

systemctl start vncserver@:1

I get the error if I run with sudo.