[GH-ISSUE #1443] Cursor unable to fully move around monitor on client due to scaling #1110

Open
opened 2026-05-05 07:29:37 -06:00 by gitea-mirror · 2 comments
Owner

Originally created by @XeonKode on GitHub (Nov 20, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1443

What happened?

Having a client side with multi monitors, main monitor being 100% scaling and the secondary 150% scaling, makes it unable to fully move the cursor across the whole screen on the 150% scaled monitor. Only is broken when the scaling is not 100%.

Version

v2.4.0

Git commit hash (if applicable)

No response

If applicable, where did you install Barrier from?

No response

What OSes are you seeing the problem on? (Check all that apply)

Windows

What OS versions are you using?

Windows 10

Relevant log output

No response

Any other information

No response

Originally created by @XeonKode on GitHub (Nov 20, 2021). Original GitHub issue: https://github.com/debauchee/barrier/issues/1443 ### What happened? Having a client side with multi monitors, main monitor being 100% scaling and the secondary 150% scaling, makes it unable to fully move the cursor across the whole screen on the 150% scaled monitor. Only is broken when the scaling is not 100%. ### Version v2.4.0 ### Git commit hash (if applicable) _No response_ ### If applicable, where did you install Barrier from? _No response_ ### What OSes are you seeing the problem on? (Check all that apply) Windows ### What OS versions are you using? Windows 10 ### Relevant log output _No response_ ### Any other information _No response_
Author
Owner

@thewavelength commented on GitHub (Nov 30, 2021):

Same issue here. A fix would be great 👍

<!-- gh-comment-id:982615297 --> @thewavelength commented on GitHub (Nov 30, 2021): Same issue here. A fix would be great 👍
Author
Owner

@anthroid commented on GitHub (Jan 11, 2022):

Same issue here Win10 -> Win10 with server at 175%. Downgrading back to the previous version 2.3.4 fixes the issue for now.

<!-- gh-comment-id:1010423083 --> @anthroid commented on GitHub (Jan 11, 2022): Same issue here Win10 -> Win10 with server at 175%. Downgrading back to the previous version [2.3.4](https://github.com/debauchee/barrier/releases/tag/v2.3.4) fixes the issue for now.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/barrier#1110
No description provided.