mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #1986] Mouse freeze in client side #1455
Labels
No labels
HiDPI
bounty
bsd/freebsd
bsd/openbsd
bug
bug
build-infra
cantfix
critical
doc
duplicate
enhancement
fix-available
from git
from release
good first issue
help wanted
installer/package
invalid
linux
macOS
meta
needs testing
pull-request
query
question
regression
regression
v2.4.0
windows
wontfix
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/barrier#1455
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @laithshams on GitHub (Oct 29, 2023).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1986
What happened?
I'm running barrier in Windows 11 as server and Linux Ubuntu; once the connection starts the mouse immediately moves to the client side and stops. trying to move the mouse using the server mouse doesn't work, knowing that right and left clicks are working fine so is the keyboard. I also created a hotkey to toggle the mouse, but once the mouse enters the server it leaves again and stays freeze
Version
v2.4.0
Git commit hash (if applicable)
No response
If applicable, where did you install Barrier from?
windows from GitHub release
ubuntu flathab
What OSes are you seeing the problem on? (Check all that apply)
Linux, Windows
What OS versions are you using?
windows 11
ubuntu 23.10
Relevant log output
No response
Any other information
No response
@anasfik commented on GitHub (Oct 30, 2023):
I can confirm this behavior with Windows 10 as server and Kali Linux as client.
@vc-mike commented on GitHub (Oct 30, 2023):
This issue likely appeared after 2023-10 Cumulative Update for Windows 11 for x64-based Systems (KB5031358) on Win11, not sure what it might have been on Win10.
The behavior is same as described here:
https://github.com/debauchee/barrier/issues/1713
Apparently this has been an issue in the past, and a fix for it made:
https://github.com/debauchee/barrier/pull/1506