Cannot Start Remote Control Session -- Manjaro KDE

[tedtms]

Describe the bug
When launching a screen control session to a Manjaro KDE desktop installation, the session cannot be started and an error appears.

To Reproduce
Steps to reproduce the behavior:

1. Install the Remotely Agent on a Manjaro KDE client using the Deployment Script under /deploy.
2. Confirm the client connects to the Remotely Server and appears as an online client.
3. Click [client] > Actions > Remote Control.
4. Remotely will say "Starting Remote Control" and then wait.
5. After about 10-15 seconds, the above "Session failed to start" error will appear and the session will not start.

Remotely Version
Server (can be found on about page): 2024.07.16.1109
Agent (can be found in device card): 2024.07.16.1109

Expected Behavior
The remote control session should launch properly.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Manjaro KDE 24.0.4 "Wynsdey"
• Browser: Firefox 128.0

Additional Context

• All other (Windows) clients work without issue. I have not tried on any other Linux installations, but can.
• I know Remotely stores client logs in /var/log/remotely but I'm uncertain which ones should be included or what content of them should be redacted for security. Can provide on request.

Thank you! And thanks again for all of your hard work on this incredible application!
Ted

[bitbound]

Are you using Wayland? Wayland isn't supported.

Furthermore, the "Linux" remote control was only ever tested on Ubuntu. Even then, it was always in rough shape and needed some rework. At this point, with X11 being phased out everywhere, it wouldn't really be worth it.

Creating the p/invoke code for X11 was a massive headache. Last I checked, there's even less documentation on Wayland. And from my understanding, it might require multiple implementations based on what compositor is being used.

Personally, I've given up on ever writing remote control for "Linux". It requires separate implementations of each service for every distro, each windowing system, etc. And you can't depend on native APIs being present like you can on Windows.

At one point in my other project (ControlR), I was experimenting with just proxying VNC and RDP connections through websockets, allowing you to connect with either of those without exposing any ports. It was working well, and I even submitted a PR to noVNC to improve the controls.

The process was taking too long, though, and I realized I wanted to have more control over these kinds of things. So I moved on to implementing my own remote control again.

Anyway. for Remotely on Wayland, I'm afraid someone from the community will have to carry the torch on that one.

[tedtms]

I'm using X11, not Wayland.

Understood -- I was actually the person who originally requested the Manjaro client and was surprised to see it made it all the way to the current version. I know Ubuntu was the only official supported distro, but since the Manjaro client was ported over into the list of installer scripts and is still around, I thought I would call it to your attention anyway.

If you no longer want to support that version of the client, I understand; however, it would be very sad to see support for Linux get dropped as whole. This is one of the only projects aside from maybe MeshCentral that has support for browser-based Linux remote control in a mixed-OS client environment, which is one of the reasons I came back to the project after a while of playing with some other tools. Unfortunately I'm unable to help in the development area of things though so I understand if it's too much work to maintain support for.

Cheers,
Ted