Hi there,
The other thing I'd note is that you must not use "sudo" with any rpi-connect commands as it does not run as root but runs as your regular user. If you use "sudo", it won't have access to the necessary environment to talk to the running rpi-connectd process (which is why you're seeing the error re being unable to communicate with the daemon).
This is where I would start investigating: this seems to suggest that our check to ensure you have an active Wayland compositor and a desktop session has failed (there is no available Wayland display in either of /run/user/1000/wayland-0 or /run/user/1000/wayland-1). Are you running Wayfire? You can set this via raspi-config by running "sudo raspi-config" going to "Advanced Options", "Wayland" and then choosing "Wayfire".Process: 1110 ExecStartPre=/usr/bin/test -S /run/user/1000/wayland-0 -o -S /run/user/1000/wayland-1 (code=exited, status=1/FAILURE)
The other thing I'd note is that you must not use "sudo" with any rpi-connect commands as it does not run as root but runs as your regular user. If you use "sudo", it won't have access to the necessary environment to talk to the running rpi-connectd process (which is why you're seeing the error re being unable to communicate with the daemon).
Statistics: Posted by paulmu — Thu Jun 27, 2024 1:48 pm