Installed and running as a service:
Code:
mafoelffen@lunar-server-01:~$ sudo systemctl status vncserver@1.service
● vncserver@1.service - Start TightVNC server at startup
Loaded: loaded (/etc/systemd/system/vncserver@.service; enabled; preset: e>
Active: active (running) since Thu 2023-03-09 06:49:27 UTC; 9s ago
Process: 10199 ExecStartPre=/usr/bin/vncserver -kill :1 > /dev/null 2>&1 (c>
Process: 10203 ExecStart=/usr/bin/vncserver -depth 24 -geometry 1280x800 -l>
Main PID: 10214 (Xtightvnc)
Tasks: 3 (limit: 4555)
Memory: 12.7M
CPU: 103ms
CGroup: /system.slice/system-vncserver.slice/vncserver@1.service
├─10214 Xtightvnc :1 -desktop X -auth /home/mafoelffen/.Xauthority>
└─10222 xfce4-session
Mar 09 06:49:26 lunar-server-01 systemd[1]: Starting Start TightVNC server at s>
Mar 09 06:49:26 lunar-server-01 vncserver[10199]: Can't find file /home/mafoelf>
Mar 09 06:49:26 lunar-server-01 vncserver[10199]: You'll have to kill the Xtigh>
Mar 09 06:49:27 lunar-server-01 vncserver[10203]: New 'X' desktop is lunar-serv>
Mar 09 06:49:27 lunar-server-01 vncserver[10203]: Starting applications specifi>
Mar 09 06:49:27 lunar-server-01 vncserver[10203]: Log file is /home/mafoelffen/>
Mar 09 06:49:27 lunar-server-01 systemd[1]: Started Start TightVNC server at st>
lines 1-20/20 (END)
On connect it frags out for me... See screenshot in the attachment... That was with Remmina: localhost:59000.
Thing is I can connect via xrdp ans ssh -X. I don't understand why, but TightVNC was tweaky for me. Could be that I was doing it on Lunar 23.04.
I should say that I followed the tutorial, but couldn't really agree with the use case. That tutorial is to setup a vncviewer/vncserver on the same machine. Most use-cases are to connect to a remote computer, not to the same computer. That use case is confusing for me, on why someone would need to do that.
On doing ssh -X forwarding to start the desktop apps an a remote computer- It worked for me if you wanted to open a Grahical Terminal session on from the remote on the local desktop. There were possibilities there, but not any more than if you were doing straight ssh to it. I could not remotely start a file manager remotely through X Forwarding. I don't know what else to try with that... Just to say it was limited.
That same VM connected fine doing xrdp and x2go...
