Troubleshooting • Help Needed: rpi-connect Service Fails to Start on Raspberry Pi

Hello everyone,

I am encountering a persistent issue with the `rpi-connect` service on my Raspberry Pi, and I’m hoping to get some insights or solutions from the community. Here’s a detailed breakdown of what’s happening:

Problem Description:
After installing the `rpi-connect` package, I attempted to start the service. However, it fails to start, repeatedly exiting with an error code. I’ve tried restarting the service multiple times but to no avail.

Steps Taken:
1. Installed `rpi-connect` using the command:2. Tried to start the service with: This resulted in an error indicating the service could not be started.

3. Checked the status of the service: The output shows that the service is in "activating (auto-restart)" state with a result of "exit-code".

4. Inspected the journal logs: The logs indicate that there is a repeating issue with the service failing to start and then being scheduled for a restart.

Additional Details:
- System Environment: The Raspberry Pi is running Debian.
- Session Type: `$XDG_SESSION_TYPE` returns `tty`, which suggests that I am not in a Wayland session.
- Wayland Socket: Trying to locate the Wayland socket with `ls -l /run/user/1000/wayland-0` returned "No such file or directory".

It appears that the `rpi-connect` service might be failing due to a missing Wayland session, but I’m not entirely sure how to proceed, especially because my session type is `tty` and not `wayland`.

Requests for Assistance:
- Has anyone faced a similar issue with `rpi-connect` on their Raspberry Pi?
- Any suggestions on how to resolve the missing Wayland session or how to get the `rpi-connect` service running successfully?

Any help or guidance would be greatly appreciated as I’m quite stuck at this point.

Thank you in advance!

Statistics: Posted by 52hyg — Wed May 08, 2024 1:05 am — Replies 2 — Views 47

---