Bug 363819

Summary: Can't move mouse cursor to the other screen when used with Synergy
Product: [Applications] kdeconnect Reporter: Michal <panaut0lordv>
Component: commonAssignee: Albert Vaca Cintora <albertvaka>
Status: RESOLVED WORKSFORME    
Severity: minor CC: justin.zobel
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Michal 2016-06-01 23:13:00 UTC 
Version 0.9

I use Synergy for managing my PC, Win10 VM with PCI passthrough and the laptop. When i move mouse I switch between the screens.
When tried to do so with KDE Connect remote input instead of mouse it stops and the border. When coming back from VM screen it works fine.

Reproducible: Always

Steps to Reproduce:
1.Run Synergy on server
2.Run Synergy on client
3.Run KDE Connect on Server
4.Try to mouse cursor between the screens using mouse
5.Try to mouse cursor between the screens using KDE Connect remote input

Actual Results:  
It stays at the screen edge

Expected Results:  
Mouse cursor should go to the other screen

Probably some validity check is in place that prohibits from moving the cursor "outside" of screen, but breaks the Synergy in the same time.

I suspect KDE Connect as a culprit because everything works fine with mouse input.
Comment 1 Justin Zobel 2020-11-12 08:46:23 UTC 
It appears synergyt is no longer available in the Ubuntu repositories. The website that is linked from the Ubuntu article goes to some non tech related website.

Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I'm setting status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.
Comment 2 Michal 2020-11-13 00:29:00 UTC 
Hello Justin,
it's been quite some time. Now I'm using MacOS with KDEConnect (some nightly build from ~2wks ago) as a server and corporate laptop with Windows as a client, but instead of Synergy I have fork: Barrier v2.3.2.

With that setup it's fine. Cannot really confirm on Arch + KDE so maybe if anyone else stumbles on that issue they can reopen, from my perspective it's solved.