github-starred/barrier

Fork 0

mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 14:16:02 -06:00

[GH-ISSUE #623] using windows TS 2016 and buster mouse don't go to debian #492

New issue

Open

opened 2026-05-05 06:32:01 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 06:32:01 -06:00

Owner

Originally created by @pierremouvet on GitHub (Apr 14, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/623

Operating Systems

Server: Windows 2016 terminal server 1607

Client: debian buster

Barrier Version

2.3.2

Steps to reproduce bug

install on windows
install on debian
configure windows server
configure debian client
connect client to server => OK

mouse stick in the dual screen windows and don't go to linux screen

Other info

When did the problem start to occur? at first start
Is there a way to work around it? No
Does this bug prevent you from using Barrier entirely? Yes

I switch server and client.
in the log file I see mouse leaving scrren
mouse entering remote screen
BUT no pointer on the client screen

Originally created by @pierremouvet on GitHub (Apr 14, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/623 ### Operating Systems ### Server: Windows 2016 terminal server 1607 Client: debian buster ### Barrier Version ### 2.3.2 ### Steps to reproduce bug ### install on windows install on debian configure windows server configure debian client connect client to server => OK 1. mouse stick in the dual screen windows and don't go to linux screen ### Other info ### * When did the problem start to occur? at first start * Is there a way to work around it? No * Does this bug prevent you from using Barrier entirely? Yes I switch server and client. in the log file I see mouse leaving scrren mouse entering remote screen BUT no pointer on the client screen

gitea-mirror commented

2026-05-05 06:32:05 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 24, 2020):

This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions[bot] commented on GitHub (Sep 24, 2020): This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

No labels

Rows
Columns