wayland support

[UnixOutlaw 1]

Despite my empty threats earlier - despite me opting for the "latest" Apple Bluetooth peripherals (Magic Keyboard 2 with fingerprint thingie and Magic Trackpad 2), despite me singing the praises of Universal Control - Synergy is still about 10,000x more reliable... I can't quantify the amount of times I've had to do "unix-y" stuff to kill "ensemble" [the name of Universal Control daemon in MacOS] - but it was so often - I needed a shell script...   anecdotally, everytime I NEEDED Universal Control to do something on the other Mac, IT DIDN'T WORK!

And - gaming on MacOS is still like utter garbage compared to Linux and SteamPlay with Proton - so - My WFH (and play) setup is now :

Left - MacBook Pro M1 Monterey 12.6.1 on 32" QHD 144 Hz monitor plus MacBook Pro M1 retina display (my personal device - 8 GB RAM 256 GB SSD)

Middle - Ubuntu 22.04 : Ryzen 7 with 32 GB of DDR4 3200 Mhz RAM and AMD GPU [Radeon RX 6600/6600 XT/6600M], TOP: 32" 75 Hz, BOTTOM, 32" 144 Hz (curved gaming)

Right - MacBook Pro M1 Monterey 12.6.1 on 32" QHD 144 Hz monitor plus MacBook Pro M1 retina display (my work device 16 Gb RAM 512 GB SSD) + iPad Pro 12.9 as Sidecar display

Not gonna lie - WAYLAND support would be f--king KICKARSE - but I can live without it.  If I had to buy my Synergy Pro license over again - I'd happily pay that reasonable sum, to get Wayland support.

One thing Mac does have over Linux (in my experience) is audio quality... 

 

Edited November 11, 2022 by UnixOutlaw

[Bill Burdick 7]

3 hours ago, UnixOutlaw said:

If I had to buy my Synergy Pro license over again - I'd happily pay that reasonable sum, to get Wayland support.

I'd be more than happy if Symless came out with a separate "enhanced edition" that includes Wayland support and I would happily auy another license for it. I bought the previous license quite long ago and I got more than my money's worth from it.

[arch 1]

On 11/11/2022 at 7:03 AM, Bill Burdick said:

My mistake -- I think the Steam Deck does not use Wayland in desktop mode, only in game mode so this is probably just X <-> X.

Maybe someone else can confirm whether Wayland <-> X works.

No, it does not work.

The only working thing I know of on Wayland, is if you have a Xwayland window open, then it can work on the server side.  If you have a fullscreeen Xwayland window open, then it works until you close that window or minimize it.

I had always hoped someone could just spawn a fullscreen, transparent, clickthrough, Xwayland 'window' as a temporary workaround, but it's been years.  There's probably some technical reason it's not that simple.

[WhiteMud 4]

Why is the thread locked on github?  How do we get some momentum on getting wayland supported/working?

[KristijanZic 2]

What is the state of Wayland support? It was promised in 2017. now it'll be 2023. next month. This is an essential feature! What is going on?

[m34nbunny 1]

J

28 minutes ago, KristijanZic said:

What is the state of Wayland support? It was promised in 2017. now it'll be 2023. next month. This is an essential feature! What is going on?

Just give up and go back to X if you rely on it. They aren't going to provide support for it

[arch 1]

https://github.com/input-leap/input-leap/pull/1524

 

Not Synergy, but initial support is being drafted for input-leap, which is a fork of Synergy. I imagine since it's open source Synergy will get it eventually to.

If I had to estimate I'd say we're still months away from an initial release just due to the sheer number of projects that are touched by these changes.

The really tech savvy could hypothetically build all of these components with the patches and run it today on Wayland, in theory, but I do not recommend it at all. There's plenty of bugs, and glitches, but it's coming.

[WhiteMud 4]

This is bullshit, obviously there is no moderators here either what a fucking joke.

[arch 1]

8 hours ago, WhiteMud said:

This is bullshit, obviously there is no moderators here either what a fucking joke.

I honestly don't blame anyone at Symless for not replying, most comments I've seen on the matter are seriously toxic.

In the end it has taken active development by Peter Hutterer (one of the most seasoned input developers in Linux) and a new protocol to get it working.

[jwilkes 3]

And I do blame them. For many years, the comments were polite requests and encouragements.

But after 60 Months of a valid, important request getting ignored, it's the users who feel a "toxic" treatment, and respond accordingly.

[Jake Harr 0]

I know it's not an option for everyone, but for what it's worth, disabling Wayland makes everything work perfectly for me.

[jwilkes 3]

45 minutes ago, jwilkes said:

And I do blame them. For many years, the comments were polite requests and encouragements.

But after 60 Months of a valid, important request getting ignored, it's the users who feel a "toxic" treatment, and respond accordingly.

I checked the talk Peter Hutterer gave on libinput back then - it is from 2014.

libei is pretty fresh¹, agreed - but I don't see how "waiting for someone to do magic" is the right approach, without any communication to at least *why* you are waiting.

 

¹ August 2020. That's two years back now.

Edited December 16, 2022 by jwilkes

[Alexboss 4]

On 12/16/2022 at 2:51 PM, arch said:

I honestly don't blame anyone at Symless for not replying, most comments I've seen on the matter are seriously toxic.

Toxic? no. Bittered ? maybe? But why ?

This feature has been long waited by many people, and it was even promised by Symless.

And all of a sudden, no news, no feedback, closing ,the github issue, parking the users in a no-exit dead end, not replying to the support opened, or even preventing submitting feedback about that.

If they don't want to do it for whatever reasons, fine, but then they should be responsible and have a clear statement about it.

And clearly spot to Linux users at purchase their product does not supporting Wayland, thus not working on modern Linux DEs.

I bought it to actually realize AFTERWARDS I couldn't use it and the refund period was over; if this was clearly indicated at the time of purchase I wouldn't have bought it.

Thanks.

[smeggysmeg 5]

I look at comments like, "if you want Synergy, you need to switch to Xorg" to being equivalent to, "you must run the program in Windows XP compatibility mode".

The new product has been out for nearly a decade, is widely adopted, and has become the default for a number of popular distributions. I understand there are engineering challenges, but it also helps to actually work on the problem instead of shipping new commercial features.

The audience for Synergy are primarily power users, many of whom use Linux. If you won't support Wayland, it's almost as like Linux support is itself becoming deprecated.

The moment anyone solves this problem for Wayland on Linux, I expect Synergy to become obsolete. I know some forks are trying to, and I expect the Synergy team will try to backport their innovations, but it's a bad look.

[jwilkes 3]

Once you've switched to one of the free forks that get the job done -

why would you go back to Synergy and "fork over" money for it?

[xsist10 1]

Finally pushed up from Ubuntu 20.04 LTS to 22.04 LTS and ran into this. Have to say I'm somewhat disappointed that this is a 9 year issue without very erratic communication from Symless.

[ccoenen 2]

On 12/16/2022 at 2:18 AM, arch said:

https://github.com/input-leap/input-leap/pull/1524

Input-Leap just merged those changes. That does not mean one can use it right away, but it does mean they are confident enough in their solution. Now we just need to wait for the wayland side of things to also release stable versions of the required new apis. So, yes, it could still be a while before it starts working again, but at least now there seems to be an agreed-upon way to how things should be done between the different involved components.