+20
Under Review

Support for xwayland

TylerF 7 years ago updated by cbray 1 day ago 16

The Client requirements page says that xwayland may not work due to a known bug. This, however, isn't a bug. It's a security feature of wayland, not allowing apps to run wayland backend components as root.

It would be great if the screenconnect client could be made to work with policykit, so that it works under xwayland. Wayland is the current realty of fedora, and the coming reality of RHEL. This will be an increasing need.

+1

Bumping this. It's getting to the point that I'm shopping screenconnect replacements for poor Linux client support. 

+1

Agreed, I believe Ubuntu 22.04 LTS will default to Wayland as well

+1

this is still not working 5 years later.

wayland is the industry standard now, rhel is the only one not shipping it default now because rhel runs 3-5 years behind. Connectwise is broken out of the box on most linux distros








+2

100% agree.  It is ridiculous that this hasn't been addressed. As you said, Wayland isn't even the future anymore, it is the present except for extremely conservative distros.  Ubuntu held back Wayland and defaulted to x.org for nVidia drivers for a long time, but even that now defaults to Wayland.  Support either needs to be added or connectwise should stop advertising Linux support

+2

Yeah it should say legacy linux support. You can edit /etc/gdm3/custom.conf and uncomment WaylandEnable=false to force the machine to use xorg only, but this is a workaround. Screenconnect is broken out of the box for modern linux. 

The technical reason it is broken is because Wayland does not allow root access to the display server, for security reasons. ConnectWise will have to be updated to use polkit and pam, to gain the necessary privileges to the display server instead of just running as root and assuming access to everything like it worked in xorg for the last 25 years.

They did this for Macs already. The display server restricts access until you enable it to escalate properly in the system menu.

It’s just a matter of ConnectWise updating the software to follow the proper escalation channels instead of rooting at everything . And they appear to have no intentions of doing that

+2

Agreed. Please work towards supporting XWayland.

ConnectWise Control is the only reason why we need to force our Linux machines back to X. 

+2

Redhat just updated to RHEL9, which defaults to wayland now. 

Literally every mainline distro uses wayland by default now, and SC is imcompatible with it

+1

Essentially this says that ScreenConnect is no longer a production-ready product.

Exactly, this should addressed as soon as possible.

bump, finally started getting away from windows to learn my most important app is busted out of the box. I already jumped through hoops to get it on arch and then to learn wayland isn't supported. disappointing.

It is unfortunate that we still can't use Control on Wayland, which is now the industry standard. This needs to be addressed. With a lot of things 11 has (and plans to) introduce, people are moving away from Windows, and many do not wish to purchase a Mac. 

+1

Yeah, this has become "Screenconnect doesn't work on linux" and made the sales documentation straight up false advertising. "Works on Linux, but not on Red Hat, Ubuntu, SUSE, or any other system you expect to find in business."

To the others on this thread pulling their hair out, XFCE and Cinnamon are still not wayland-ready, so are potentially an indicator of a "ScreenConnect might work" distro. Fedora spins of either, or Linux Mint, which is the project that develops Cinnamon. Even this has Wayland support in Alpha now though. Unfortunately, Connectwise appears to be willing to let the support die on the vine. 

Yes, this also means we cannot adequately support Linux systems if necessary.