Support for xwayland

Avatar
  • updated
  • Closed

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.

Pinned replies
Avatar
0
Sean White Team Member
  • Answer
  • Closed

We did extensive research and unfortunately will not be able to provide support for machines running Wayland protocol; please see our supportability statement here:
Blank screens on Linux machines with Wayland enabled - ConnectWise


Avatar
0
Sean White Team Member
  • Answer
  • Closed

We did extensive research and unfortunately will not be able to provide support for machines running Wayland protocol; please see our supportability statement here:
Blank screens on Linux machines with Wayland enabled - ConnectWise


Avatar
0
cbray

So something I found by accident seems to work. I installed default-jre on my test environment, which now lets me connect to machines. Have to set the file it downloads as executable, then it will run. Haven't done any testing for client machines at this time, but at least there's a way to connect from wayland.

Avatar
0
cbray
Quote from Mark Coelho

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.

Avatar
1
Mark Coelho

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. 

Avatar
0
cbray

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. 

Avatar
0
Samb31

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.

Avatar
0
waldek

Exactly, this should addressed as soon as possible.

Avatar
1
Allen Crist

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

Avatar
1
Jesse Hargis

bump bump bump

Avatar
1
Ashton Southall

Bumping this.

 Commenting is disabled

Top contributors

Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar