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

Limited cursor movement area after resolution changed on the client #7302

Open
Cryspia opened this issue Nov 1, 2023 · 2 comments
Open

Limited cursor movement area after resolution changed on the client #7302

Cryspia opened this issue Nov 1, 2023 · 2 comments
Labels
bug There is an error or the program doesn't work properly triage Awaiting repro confirmation (bug) or needs accepting (enhancement)

Comments

@Cryspia
Copy link

Cryspia commented Nov 1, 2023

Operating Systems

Server: MacOs 14.1
Client: Windows 11

Synergy Version

3.0.75.7-rc3

Steps to Reproduce

I am using my mouse and keyboard on my Mac to share to my Windows device.

I have two monitors for my Windows and frequently switch the monitors in use (only one monitor is in active at a time).

The two monitors has different resolutions, and I discovered that after I swtich from my 2K monitor to the 4K one, the movement of the cursor will be limited on the top-left area and cannot reach the bottom-right area.

This problem can be solved by restarting the Synergy daemon on the client manually.

Extra Info

I suggest you add a trigger to your program to dectect the monitor changes and auto-restart the daemon.

@Cryspia Cryspia added the bug There is an error or the program doesn't work properly label Nov 1, 2023
@jmccanta
Copy link

I encounter the same issue with a LInux master and Windows client. The Windows client on my laptop fails to detect a monitor change when I go between home and work monitors. The only solution that I have found is to manually restart the daemon.

@nbolton nbolton added the triage Awaiting repro confirmation (bug) or needs accepting (enhancement) label Jul 16, 2024
@nbolton nbolton added the unanswered Issue not yet been answered by a maintainer label Sep 6, 2024
@nbolton
Copy link
Member

nbolton commented Sep 6, 2024

Thanks for reporting this bug, we will try to reproduce it when we can.

@nbolton nbolton removed the unanswered Issue not yet been answered by a maintainer label Sep 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug There is an error or the program doesn't work properly triage Awaiting repro confirmation (bug) or needs accepting (enhancement)
Projects
None yet
Development

No branches or pull requests

3 participants