Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wayland support for Linux client and server #4090

Open
nbolton opened this issue Oct 13, 2014 · 126 comments
Open

Wayland support for Linux client and server #4090

nbolton opened this issue Oct 13, 2014 · 126 comments
Labels

Comments

@nbolton
Copy link
Member

@nbolton nbolton commented Oct 13, 2014

Problem: We do not support Wayland on Linux. Wayland is intended as a simpler replacement for X, easier to develop and maintain.

Solution: Add Wayland support for both the client and server.

From Wikipedia:

In general, out of the box support for a full desktop running Wayland in major Linux distributions is still in early stages. Most Linux distributions that ship version 3.20 or newer of the Gnome desktop environment do support manually installing a Wayland session, and in case of Gnome 3.22 or newer might default to Wayland. Notable early adopters that provide Wayland out of the box are:

Fedora starting with version 25 uses Wayland for the default GNOME 3.22 desktop session, with X.Org as a fallback if the graphics driver cannot support Wayland.[65] Fedora 25 carries patches that make the Wayland session work with NVidia drivers as well.[66]
...

@circuit-breaker
Copy link

@circuit-breaker circuit-breaker commented Oct 18, 2014

Agreed, Wayland is coming fast. Nvidia has been busy parting out the bulk of their drivers.. And the design means a lot more walls between applications and not touching each other's resources unchecked. It is the future

@Pajinek
Copy link

@Pajinek Pajinek commented Feb 16, 2015

When do you plan to support wayland? Is it question of far future? I tried it and synergy doesn't work correct.

@lig
Copy link

@lig lig commented Apr 1, 2015

I'm switched to Gnome 3.16 and will use Wayland from now on as it work pretty stable for me unlike Gnome on Xorg. Thus I will not be able to use Synergy until this will be resolved.

@neilmayhew
Copy link

@neilmayhew neilmayhew commented May 19, 2015

I'd like to vote for this too.

@neilmayhew
Copy link

@neilmayhew neilmayhew commented May 19, 2015

I did some quick experimentation with using synergy through xwayland (which happens automatically) and it starts to go wrong when trying to grab the pointer on leaving the screen. I commented out the lines in XWindowsScreen.cpp and was able to get a bit further, actually controlling the mouse on the other screen, but the movement wasn't positioned correctly.

I'm using a Debian Jessie system, and Wayland has been a login option for some time. I don't even need to use weston, because gnome-shell (and almost all other gtk3 apps) can use wayland directly. So Debian would make a good testbed.

@Kami-no
Copy link

@Kami-no Kami-no commented Oct 22, 2015

+1 vote to support Wayland.

@gregsheremeta
Copy link

@gregsheremeta gregsheremeta commented Nov 17, 2015

+1 gonna need this soon!

@skoslowski
Copy link

@skoslowski skoslowski commented Nov 30, 2015

+1

2 similar comments
@dotted
Copy link

@dotted dotted commented Dec 14, 2015

+1

@hertzg
Copy link

@hertzg hertzg commented Feb 1, 2016

+1

@acdingman
Copy link

@acdingman acdingman commented Feb 5, 2016

I don't care about the "pro" features, but will commit to buying "pro" anway if Synergy works in Wayland when Fedora 24 comes out. Anyone else?

@lig
Copy link

@lig lig commented Feb 8, 2016

@acd-rht I already have "pro":) And I feel lack of wayland support and lack of the several other features…

@Djhg2000
Copy link

@Djhg2000 Djhg2000 commented Apr 19, 2016

I'm using Synergy as a system critical component on my gaming rig. Windows 7 runs in a VM and has no physical mouse or keyboard. Up until now I've used Xorg on the host system but now that I'm running Wayland the only way to control my Windows 7 VM is through a virtual desktop connection (local access is not possible due to the forwarded graphics card).

When I run "synergys -f" and try to cross the screen border I just get "WARNING: can't leave screen".

Since it turns out Wayland runs much smoother than Xorg on my machine and enables a lot of new functionality I'm very reluctant to switch back to Xorg. With Fedora 24 set to release in 48 days I think it's time we consider this an urgent issue.

@thegass
Copy link

@thegass thegass commented Apr 22, 2016

+1
wayland is pretty stable on my machines (fedora 23,24) but i cannot use it because of synergy.

@bcdonadio
Copy link

@bcdonadio bcdonadio commented May 15, 2016

+1
Wayland is working flawlessly on my machines with Fedora 24, and the only application that's holding me back from switching to it is Synergy. The mouse actually seems to work, however there's no cursor showing. The keyboard, however, doesn't work.

@rboati
Copy link

@rboati rboati commented Jul 5, 2016

+1

@preactive
Copy link

@preactive preactive commented Aug 1, 2016

+1

Same as bcdonadio.

Switched back from wayland to standard gnome and worked like normal.

@tbporter
Copy link

@tbporter tbporter commented Aug 21, 2016

To add to this, Fedora 25 is going to use Wayland by default.
https://fedorahosted.org/fesco/ticket/1615

@trejjam
Copy link

@trejjam trejjam commented Oct 13, 2016

Today my Gnome by default switch to Wayland (ArchLinux), and also Synergy not work correctly

@ghost
Copy link

@ghost ghost commented Oct 21, 2016

Switched from Ubuntu (Unity 7) to Arch (Gnome 3) and got the same problems.
Synergy just crashes when i try to leave the screen.

@cekstam
Copy link

@cekstam cekstam commented Oct 28, 2016

+1

@pierrre
Copy link

@pierrre pierrre commented Oct 28, 2016

@cekstam please don't post a useless "+1"
You notify EVERYONE on this issue by email !
Just add a "thumbs up" emoji on the first message.

@nlyan @nbolton I suggest you lock the conversation because:

  • Synergy doesn't support Wayland yet
  • More and more distributions are migrating to Wayland
  • I don't think we will receive any interesting feedback until Synergy supports Wayland.
  • All the previous comments are useless "+1"
  • I'm bored to receive useless notifications

Thank you.

@michaelwheatland
Copy link

@michaelwheatland michaelwheatland commented Oct 27, 2017

I just purchased Synergy which advertises compatability with Ubuntu.
Very disappointed that this program doesn't work with the default Ubuntu Desktop Manager. Is support for Weyland coming soon?

@ppaalanen
Copy link

@ppaalanen ppaalanen commented Nov 10, 2017

As far as I understand what Synergy does (sorry, never used it myself), there are two very different sides to the Wayland story.

I can certainly confirm that there is no standard Wayland interface at this time for injecting input events into a Wayland display server. We have not seen such proposals in Wayland upstream either. The major problem is how to authenticate and authorize a Wayland client that wants to do this. Right now I can imagine two ways to inject input into a Wayland display server: use root privileges and /dev/uinput, or some server specific method (I assume e.g. GNOME has some for remote control).

OTOH, reading input events from a Wayland display server might not be a big deal depending on how you want to do it, it is already necessary for virtual machine frontends etc. and that has seen some development in upstream Wayland. But if you want to do it without a normal application window, you cannot for now in a generic way.

If Synergy runs through Xwayland instead of being a Wayland application, I would assume it is able to inject input events to the Xwayland X server, but those events will not be forwarded to the Wayland display server. I guess this has two consequences:

  • Wayland applications cannot receive the injected input
  • the injected input cannot affect the input devices, e.g. they cannot move (or create) the real pointer cursor
@wirecat
Copy link

@wirecat wirecat commented Nov 17, 2017

@skela I think there are some kinks(#6196), but it is mostly functional. Version 1.8.8 works reasonably well on Wayland as well.

e: I should clarify and state that I am running Arch Linux which may have a lot to do with this operating at all or any bugs I'm experiencing.

@skela
Copy link

@skela skela commented Nov 18, 2017

@wirecat thx, last time i tried synergy on wayland, it did not work at all, and I'm also using Arch (Well antergos). Arch Linux / Antergos as my server, and MacOS High Sierra as the client.

@danielheaton
Copy link

@danielheaton danielheaton commented Nov 18, 2017

@skela Just installed the newest version (1.8.8-stable-258cb2) on Fedora 27 with Gnome 3. The mouse would not show, but I could type and copy/paste. I had to disable Wayland for it to work properly.

@skela
Copy link

@skela skela commented Nov 20, 2017

Right, thx @RadiogenicHeat , I guess I will wait :D

@fenrig
Copy link

@fenrig fenrig commented Dec 12, 2017

Still not working? Using ARCH with all packages recent

@btaens
Copy link

@btaens btaens commented Dec 23, 2017

Nope, still not working. At the end of 2017.

@sgala
Copy link

@sgala sgala commented Jan 8, 2018

I'm seeing this also, I need to start ubuntu 17.10 with "wayland over xorg" to have synergy sort of working (no dock, some other problems).

@daveboutcher
Copy link

@daveboutcher daveboutcher commented Jan 14, 2018

I wonder if we could get a definitive update on Wayland support....in Synergy 1 or 2. Not having Wayland support in 2018 is kind of a deal-breaker for using Synergy with Linux. I know there is a workaround (turn off Wayland), but that's not really a viable alternative for me.

@phoenixdigital
Copy link

@phoenixdigital phoenixdigital commented Jan 17, 2018

@polarathene
Copy link

@polarathene polarathene commented Jan 19, 2018

  • I assume Wayland support is waiting on protocol or something to let Synergy do it's thing otherwise require each compositor have it's own implementation?
  • Not sure about what the issues with Wayland are, Synergy still not being transparent about barriers they've run into?

For those looking for alternatives with guest VMs(assuming they run Wayland, I'm more interested in Wayland as a host) or running Wayland as a host, you might be able to use QEMU/KVM(not a switch, but hypervisor KVM), and something like evdev with a key combination to redirect input between host and guest. It's a common way to handle input for linux host, windows guests on r/VFIO these days.

If you need it for going across several actual machines, I guess with Wayland you're out of luck? I guess Wayland users/customers are more of a minority though to Synergy and their current changes to monetize the product is working out better for them. Wayland support is likely to come eventually, but until development elsewhere has gotten to a point that it's worthwhile for Synergy devs to actually implement support for we're likely not going to see it as other features will be prioritized to cater to the wider user base needs.

It's odd though that there was some tweets/communications about the Wayland support getting in good shape some time ago and no updates since as to why progress halted?

Looked briefly at the repo, noticed a Wayland branch here no updates since March 2017. Earlier comments in this thread suggest keyboard input is working in Wayland on 1.8.8 and mouse uncertain but the mouse cursor visual just doesn't display?

@ppaalanen
Copy link

@ppaalanen ppaalanen commented Jan 19, 2018

I still don't know what exactly is Synergy's use case, but I hope the below clarifies the obstacles in general a little. I hope I didn't guess wrong what the intended use is.

There are two completely different aspects to "Wayland support":

  1. Running the UI application on a Wayland session, controlling whatever remote system.
  2. Controlling a remote system that is running a Wayland session.

The latter can further be divided into roughly two cases:
2.1. The "remote" system being a VM where you are actually controlling the virtual machine as if it had real physical input and output devices, these being actually virtual remote devices.
2.2. The remote system being a normal user session where the remote control connection just introduces new input and hijacks the output, e.g. a helpdesk connecting to a user's machine.

Cases 1 and 2.1 are perfectly implementable as is, the Wayland features already exists at least as unstable standard interfaces. 2.1. does not actually concern Wayland at all.

Case 2.2 is the one that requires explicit support from each and every Wayland display server being remote controlled. There are no standard interfaces even proposed for this case yet. Each Wayland display server is going its own way here, e.g. offering an integrated RDP or other server, or not having implemented anything yet. In other words, as far as I have seen, the support in the display servers seems to be not introducing Wayland interfaces for it but implementing a suitable server directly.

I think it would be nice if the company behind Synergy would support these remote controlling features in the various display server projects or publicly propose whatever they think would be better. One thing is almost sure: one cannot anymore write a (proprietary) application to hijack a display server, like it was possible with X11. There is no central software component like Xorg to depend on for it.

As I said before, it is probably possible to run case 2.2 through Xwayland on the remote system, but it will not be able to control any Wayland-based applications on the remote and you likely have problems with a mouse cursor.

@CapOM
Copy link

@CapOM CapOM commented Jan 19, 2018

I think a large set of users are interested in Case 1: Work station is running wayland and the remote is a mac or win laptop. This case does not even work despite being the easiest setup to support.

@cadesalaberry
Copy link

@cadesalaberry cadesalaberry commented Jan 19, 2018

Given that this feature is the most requested by far it would be great to have an actual answer from the synergy-core dev team.

@symless symless locked and limited conversation to collaborators Jan 24, 2018
@symless symless deleted a comment from chrisbliss18 Sep 17, 2019
@symless symless deleted a comment from Kirk-H Sep 17, 2019
@symless symless deleted a comment from Heimo001 Sep 17, 2019
@symless symless deleted a comment from klm46 Sep 17, 2019
@symless symless deleted a comment from cuviper Sep 17, 2019
@symless symless deleted a comment from Lerentis Sep 17, 2019
@symless symless deleted a comment from skela Sep 17, 2019
@symless symless deleted a comment from fenrig Sep 17, 2019
@symless symless deleted a comment from oxayotl Sep 17, 2019
@symless symless deleted a comment from tonylambiris Sep 17, 2019
@nbolton
Copy link
Member Author

@nbolton nbolton commented Sep 17, 2019

We do plan on adding Wayland support to the next major version.

@nbolton
Copy link
Member Author

@nbolton nbolton commented May 4, 2021

We had previously prioritised Wayland support for Synergy when Ubuntu 17.10 made it the default. We had invested development time in developing Wayland support, but a short while later Ubuntu 18 was released and Wayland was no longer the default, so we decided to lower the priority. Due to the recent release of Ubuntu 21.04 and Fedora 34 where Wayland is being used by default, we are now reconsidering the priority. Unfortunately, we cannot promise anything at this time.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet