[GH-ISSUE #1105] Can only use client if on the left side #884

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

Originally created by @LazyHatGuy on GitHub (Mar 19, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1105

Describe the bug
My host machine (Windows) and my client (Pop-OS 20.04) will only allow me to move my mouse between the two if I configure the client to be on the left side of the host. As soon as I put it on the right, it no longer works.

I have two monitors on my host machine and if I go the whole way left on my second monitor it works but when I try to go right on my main monitor it doesn't work.

To Reproduce

Steps to reproduce the behaviour:

  1. Configure the client to be on the left side of the host
  2. Move mouse all the way left
  3. Client get's mouse and keyboard input
  4. Move the client to the right side of the host
  5. Reload host
  6. Move mouse all the way right
  7. Mouse never leaves the screen

Host
OS: Windows 10 64-bit
Barrier: 2.3.3

Client
OS: Pop-OS 20.04 LTS
Barrier: 2.3.3

Originally created by @LazyHatGuy on GitHub (Mar 19, 2021). Original GitHub issue: https://github.com/debauchee/barrier/issues/1105 **Describe the bug** My host machine (Windows) and my client (Pop-OS 20.04) will only allow me to move my mouse between the two if I configure the client to be on the left side of the host. As soon as I put it on the right, it no longer works. I have two monitors on my host machine and if I go the whole way left on my second monitor it works but when I try to go right on my main monitor it doesn't work. **To Reproduce** Steps to reproduce the behaviour: 1. Configure the client to be on the left side of the host 2. Move mouse all the way left 3. Client get's mouse and keyboard input 4. Move the client to the right side of the host 5. Reload host 6. Move mouse all the way right 7. Mouse never leaves the screen **Host** OS: Windows 10 64-bit Barrier: 2.3.3 **Client** OS: Pop-OS 20.04 LTS Barrier: 2.3.3
Author
Owner

@xmassx commented on GitHub (Mar 23, 2021):

Same issue here, i've found out that this problem arise when i use "Scaling factor" for main display in windows configuration. When i removed 150% scaling factor, issue dissapeared. You can check debug level logs, when you change display positions in windows, virtual display in barrier changed as if the real monitor area are multiplied by scaling factor. Have no idea how to fix it tho, probably it is all because barrier doesn't handle dpi settings at all

<!-- gh-comment-id:804796262 --> @xmassx commented on GitHub (Mar 23, 2021): Same issue here, i've found out that this problem arise when i use "Scaling factor" for main display in windows configuration. When i removed 150% scaling factor, issue dissapeared. You can check debug level logs, when you change display positions in windows, virtual display in barrier changed as if the real monitor area are multiplied by scaling factor. Have no idea how to fix it tho, probably it is all because barrier doesn't handle dpi settings at all
Author
Owner

@mjflower commented on GitHub (Apr 5, 2021):

Same issue here, only works when client to the left side. Scaling also used on my clients.

<!-- gh-comment-id:813201570 --> @mjflower commented on GitHub (Apr 5, 2021): Same issue here, only works when client to the left side. Scaling also used on my clients.
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#884
No description provided.