Server: Fedora 25 64bit
Client: Windows 10 64bit
1.8.5 (synergy-master-stable-6a7703f-Linux-x86_64.rpm)
But I tried different versions: 1.8.3, 1.8.6-rc1
Start the server on Fedora 25 and move the mouse to a client.
Fedora 25 uses Xorg 1.19 (xorg-x11-server-Xwayland-1.19.0-1.fc25.x86_64). I guess the problem is related to the use of wayland. The client connects without problems to the server. Once you move the mouse over to the client, the client says that the server is dead. The mouse cursor is now only visible in the console window, where the server was started, until you kill the server. The debug trace is not very useful, but can be provided if necessary.
Put anything else you can think of here.
Just a heads up, this is a duplicate of #4090 which has been largely ignored by the developers since around 2014.
Initially when I found it I excused it as 'Oh, 2014 Wayland wasn't too common then'. As I read and saw the date jumping nearer and nearer to the present I got less optimistic. Wayland is becoming fairly popular at this point and on some systems it's a requirement; not having proper Wayland support when 2017 is around the corner doesn't give me good feelings about future support for this app.
Is there a way to work around it? No/Yes, you can...
I haven't found one yet.
FWIW, you can disable Wayland by setting WaylandEnable=false in /etc/gdm/custom.conf This worked for me in F25 64bit.
Would still love to have Wayland supported in Synergy though.
It should be noted that this is not a workaround. This is turning off
Wayland and as I mentioned that is NOT an option for certain users.
On Dec 9, 2016 10:51 AM, "Scott Sturdivant" notifications@github.com
wrote:
Is there a way to work around it? No/Yes, you can...
I haven't found one yet.FWIW, you can disable Wayland by setting WaylandEnable=false in
/etc/gdm/custom.conf This worked for me in F25 64bit.Would still love to have Wayland supported in Synergy though.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/symless/synergy/issues/5763#issuecomment-266046953,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAl1ooKark3GJXkCoLtA6k-WPUB4qGUNks5rGXkFgaJpZM4LESdx
.
Paid user here if that makes any difference. I'd like to start using Wayland in 2017, hope this gets some attention and someone responds with a status update on the other issue @mallardduck . With Gnome having switched Wayland on as default(I get that you can change it), newer releases(and I assume rolling distro's already) will be very common in hitting this problem.
Unfortunately turning off wayland does not work for me (this is another story - and another bug report). Nevertheless... it looks like Xorg is going to be fully replaced in all systems and therefore this project has to fix this, or remove the debian and ubuntu signs from their page.
@d3acon and Fedora, they've been using wayland as default for more as a month now.
Which will soon be in RHEL and CentOS. (end 2017 at the soonest)
paid user really looking forward to the wayland update
Although there is no response on these issues I've contacted support and have some good news:
Synergy will indeed support Wayland in 2017, as we're working hard on this!
Duplicate of #4090
Most helpful comment
It should be noted that this is not a workaround. This is turning off
Wayland and as I mentioned that is NOT an option for certain users.
On Dec 9, 2016 10:51 AM, "Scott Sturdivant" notifications@github.com
wrote: