Remote Pi is headless RPi4 with stock 64 bit Bookworm Desktop set to auto boot to Desktop with no pw - up to date and using current firmware with rpi-connect v 1.2.1 [arm64]. Not lite version. The Remote shell option to connect shows on the local web browser but Screen sharing option is not showing as available. Works fine with remote shell.
Tried so far ...
$ systemctl —user status rpi-connect-wayvnc
× rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect
Loaded: loaded (/usr/lib/systemd/user/rpi-connect-wayvnc.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Wed 2024-06-26 10:02:29 CST; 16h ago
Process: 1110 ExecStartPre=/usr/bin/test -S /run/user/1000/wayland-0 -o -S /run/user/1000/wayland-1 (code=exited, status=1/FAILURE)
Process: 1112 ExecStopPost=/usr/bin/rm -f /run/user/1000/rpi-connect-wayvnc-ctl.sock /run/user/1000/rpi-connect-wayvnc.sock (code=exited, status=0/SUCCESS)
CPU: 8ms
pi@MonitorPi:~ $ journalctl --user --follow --unit rpi-connect-wayvncJun 26 10:02:29 MonitorPi
systemd[855]: rpi-connect-wayvnc.service: Scheduled restart job, restart counter is at 5.
Jun 26 10:02:29 MonitorPi systemd[855]: Stopped rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect.
Jun 26 10:02:29 MonitorPi systemd[855]: rpi-connect-wayvnc.service: Start request repeated too quickly.
Jun 26 10:02:29 MonitorPi systemd[855]: rpi-connect-wayvnc.service: Failed with result 'exit-code'.
Jun 26 10:02:29 MonitorPi systemd[855]: Failed to start rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect.
The systemctl ExecStartPre=/usr/bin/test should return SUCCESS but is reporting FAILURE.
Have purged rpi-connect and re installed it but same result.
Only error I can find on this system is a problem with libc which is reported when I run dpkg for failures and also shows when apt upgrading and install --fix-missing.
pi@MonitorPi:/ $ sudo dpkg --configure -a
Setting up libc-bin (2.36-9+rpt2+deb12u7) ...
Segmentation fault
Segmentation fault
dpkg: error processing package libc-bin (--configure):
installed libc-bin package post-installation script subprocess returned error exit status 139
Errors were encountered while processing:
libc-bin
Not sure how to fix this or if it is related to this issue but mentioned here for completeness.
Tried so far ...
$ systemctl —user status rpi-connect-wayvnc
× rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect
Loaded: loaded (/usr/lib/systemd/user/rpi-connect-wayvnc.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Wed 2024-06-26 10:02:29 CST; 16h ago
Process: 1110 ExecStartPre=/usr/bin/test -S /run/user/1000/wayland-0 -o -S /run/user/1000/wayland-1 (code=exited, status=1/FAILURE)
Process: 1112 ExecStopPost=/usr/bin/rm -f /run/user/1000/rpi-connect-wayvnc-ctl.sock /run/user/1000/rpi-connect-wayvnc.sock (code=exited, status=0/SUCCESS)
CPU: 8ms
pi@MonitorPi:~ $ journalctl --user --follow --unit rpi-connect-wayvncJun 26 10:02:29 MonitorPi
systemd[855]: rpi-connect-wayvnc.service: Scheduled restart job, restart counter is at 5.
Jun 26 10:02:29 MonitorPi systemd[855]: Stopped rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect.
Jun 26 10:02:29 MonitorPi systemd[855]: rpi-connect-wayvnc.service: Start request repeated too quickly.
Jun 26 10:02:29 MonitorPi systemd[855]: rpi-connect-wayvnc.service: Failed with result 'exit-code'.
Jun 26 10:02:29 MonitorPi systemd[855]: Failed to start rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect.
The systemctl ExecStartPre=/usr/bin/test should return SUCCESS but is reporting FAILURE.
Have purged rpi-connect and re installed it but same result.
Only error I can find on this system is a problem with libc which is reported when I run dpkg for failures and also shows when apt upgrading and install --fix-missing.
pi@MonitorPi:/ $ sudo dpkg --configure -a
Setting up libc-bin (2.36-9+rpt2+deb12u7) ...
Segmentation fault
Segmentation fault
dpkg: error processing package libc-bin (--configure):
installed libc-bin package post-installation script subprocess returned error exit status 139
Errors were encountered while processing:
libc-bin
Not sure how to fix this or if it is related to this issue but mentioned here for completeness.
Statistics: Posted by peter.arq — Thu Jun 27, 2024 10:57 am