Progress summary: systemd launch of vncserver fails on reboot, but not after manual launch
My original configuration used init.d to launch vncserver on boot. I switched that out for systemd, shamelessly copying
from https://pimylifeup.com/raspberry-pi-vnc-server/ .
On reboot, it does automatically launch vncserver, but as with init.d, no applications can be run in the GUI. My configuration uses "user method" autostart (see excellent: viewtopic.php?t=294014) to run some python scripts in lxterminal windows. Those scripts open and start, but crash soon after. I also usually get "No session for pid=xxxx" alerts.
If I relaunch vncserver manually or with systemd, vncserver works fine and I can run applications from it. The python scripts also run as expected.
I suspect that, on boot, systemd is running vncserver before a prerequisite is ready - but I don't know, and this is well beyond my understanding. Ideas?
My original configuration used init.d to launch vncserver on boot. I switched that out for systemd, shamelessly copying
from https://pimylifeup.com/raspberry-pi-vnc-server/ .
Code:
[Unit]Description=TightVNC remote desktop serverAfter=network.target [Service]User=piType=forkingExecStart=/usr/bin/vncserver -geometry 1920x1200 -depth 24 :1ExecStop=/usr/bin/vncserver -kill :1 [Install]WantedBy=multi-user.targetIf I relaunch vncserver manually or with systemd, vncserver works fine and I can run applications from it. The python scripts also run as expected.
I suspect that, on boot, systemd is running vncserver before a prerequisite is ready - but I don't know, and this is well beyond my understanding. Ideas?
Statistics: Posted by rpi5 — Sun Apr 07, 2024 6:38 pm