github-starred/barrier

Fork 0

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

[GH-ISSUE #1213] Logitech G203 mouse on Linux Server can't move move to Windows client #976

New issue

Open

opened 2026-05-05 07:20:53 -06:00 by gitea-mirror · 5 comments

gitea-mirror commented

2026-05-05 07:20:53 -06:00

Owner

Originally created by @dmascord on GitHub (Jun 25, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1213

Describe the bug
My setup between a Linux (Debian Buster) and Windows (10) has been working for a long time, recently I switched mice to a Logitech G203, and then for some reason it was not possible to move control over to the Windows machine. Control would briefly go into the left side of the Windows screen, and then jump back a long way to the right of the Linux screen.
This only happens with the G203. I have tested with the trackpad, as well as Logitech MX mouse, both of which work with no configuration changes.

To Reproduce

Setup Linux Barrier Server, and Windows Barrier Client, with server on left, client on right.
Attempt to exit the right side of the linux screen by moving the move cursor

Expected behavior
Mouse and keyboard control stays in the Windows Client, until moving back to the left side of the Windows screen.

Screenshots
N/A

Desktop (please complete the following information):

OS: Linux Debian Buster and Windows 10
Barrier version 2.3.3

Additional context

The G203 has an adjustable DPI sensitivity option button, so perhaps we are running into DPI issues ?

Originally created by @dmascord on GitHub (Jun 25, 2021). Original GitHub issue: https://github.com/debauchee/barrier/issues/1213 **Describe the bug** My setup between a Linux (Debian Buster) and Windows (10) has been working for a long time, recently I switched mice to a Logitech G203, and then for some reason it was not possible to move control over to the Windows machine. Control would briefly go into the left side of the Windows screen, and then jump back a long way to the right of the Linux screen. This only happens with the G203. I have tested with the trackpad, as well as Logitech MX mouse, both of which work with no configuration changes. **To Reproduce** Setup Linux Barrier Server, and Windows Barrier Client, with server on left, client on right. Attempt to exit the right side of the linux screen by moving the move cursor **Expected behavior** Mouse and keyboard control stays in the Windows Client, until moving back to the left side of the Windows screen. **Screenshots** N/A **Desktop (please complete the following information):** - OS: Linux Debian Buster and Windows 10 - Barrier version 2.3.3 **Additional context** The G203 has an adjustable DPI sensitivity option button, so perhaps we are running into DPI issues ?

gitea-mirror commented

2026-05-05 07:20:55 -06:00

Author

Owner

@dmascord commented on GitHub (Jun 25, 2021):

After switching mice from the G203 to the Redragon Lite 2000dpi (which worked), and then back to the G203, it then worked again.
I will keep diagnosing and try to isolate what could be causing the issue.

@dmascord commented on GitHub (Jun 25, 2021): After switching mice from the G203 to the Redragon Lite 2000dpi (which worked), and then back to the G203, it then worked again. I will keep diagnosing and try to isolate what could be causing the issue.

gitea-mirror commented

2026-05-05 07:20:57 -06:00

Author

Owner

@dmascord commented on GitHub (Jun 28, 2021):

This happened again today:

barrier.conf

# sample barrier configuration file
#
# comments begin with the # character and continue to the end of
# line.  comments may appear anywhere the syntax permits.

section: screens
	# three hosts named:  moe, larry, and curly
	n550jv:
	SYDLT5CG0209DNP:
	#tests-MBP.lan:
end

section: links
	# larry is to the right of moe and curly is above moe
	n550jv:
	        right = SYDLT5CG0209DNP
	        #left  = tests-MBP.lan

	# moe is to the left of larry and curly is above larry.
	# note that curly is above both moe and larry and moe
	# and larry have a symmetric connection (they're in
	# opposite directions of each other).
	SYDLT5CG0209DNP:
	        left  = n550jv
	        #up    = tests-MBP.lan

	# larry is below curly.  if you move up from moe and then
	# down, you'll end up on larry.
	#tests-MBP.lan:
	        #down  = SYDLT5CG0209DNP
	        #right = n550jv
end

Normal logging

$ barriers -f -a :: --enable-crypto -c /home/tusker/.local/share/barrier/barrier.conf
started server (IPv4/IPv6), waiting for clients
[2021-06-29T09:49:46] INFO: OpenSSL 1.1.1d 10 Sep 2019
[2021-06-29T09:49:46] INFO: accepted secure socket
[2021-06-29T09:49:46] INFO: ECDHE-RSA-AES256-GCM-SHA384 TLSv1.2 Kx=ECDH Au=RSA Enc=AESGCM(256) Mac=AEAD

[2021-06-29T09:49:46] NOTE: accepted client connection
[2021-06-29T09:49:46] NOTE: client "SYDLT5CG0209DNP" has connected
[2021-06-29T09:49:53] INFO: switch from "n550jv" to "SYDLT5CG0209DNP" at 0,848
[2021-06-29T09:49:53] INFO: leaving screen
[2021-06-29T09:49:53] INFO: screen "n550jv" updated clipboard 0
[2021-06-29T09:49:53] INFO: screen "n550jv" updated clipboard 1
[2021-06-29T09:49:53] INFO: switch from "SYDLT5CG0209DNP" to "n550jv" at 2729,807
[2021-06-29T09:49:53] INFO: entering screen
[2021-06-29T09:50:00] INFO: switch from "n550jv" to "SYDLT5CG0209DNP" at 0,749
[2021-06-29T09:50:00] INFO: leaving screen
[2021-06-29T09:50:00] INFO: switch from "SYDLT5CG0209DNP" to "n550jv" at 2447,736
[2021-06-29T09:50:00] INFO: entering screen

@dmascord commented on GitHub (Jun 28, 2021): This happened again today: barrier.conf ``` # sample barrier configuration file # # comments begin with the # character and continue to the end of # line. comments may appear anywhere the syntax permits. section: screens # three hosts named: moe, larry, and curly n550jv: SYDLT5CG0209DNP: #tests-MBP.lan: end section: links # larry is to the right of moe and curly is above moe n550jv: right = SYDLT5CG0209DNP #left = tests-MBP.lan # moe is to the left of larry and curly is above larry. # note that curly is above both moe and larry and moe # and larry have a symmetric connection (they're in # opposite directions of each other). SYDLT5CG0209DNP: left = n550jv #up = tests-MBP.lan # larry is below curly. if you move up from moe and then # down, you'll end up on larry. #tests-MBP.lan: #down = SYDLT5CG0209DNP #right = n550jv end ``` Normal logging $ barriers -f -a :: --enable-crypto -c /home/tusker/.local/share/barrier/barrier.conf started server (IPv4/IPv6), waiting for clients [2021-06-29T09:49:46] INFO: OpenSSL 1.1.1d 10 Sep 2019 [2021-06-29T09:49:46] INFO: accepted secure socket [2021-06-29T09:49:46] INFO: ECDHE-RSA-AES256-GCM-SHA384 TLSv1.2 Kx=ECDH Au=RSA Enc=AESGCM(256) Mac=AEAD ``` [2021-06-29T09:49:46] NOTE: accepted client connection [2021-06-29T09:49:46] NOTE: client "SYDLT5CG0209DNP" has connected [2021-06-29T09:49:53] INFO: switch from "n550jv" to "SYDLT5CG0209DNP" at 0,848 [2021-06-29T09:49:53] INFO: leaving screen [2021-06-29T09:49:53] INFO: screen "n550jv" updated clipboard 0 [2021-06-29T09:49:53] INFO: screen "n550jv" updated clipboard 1 [2021-06-29T09:49:53] INFO: switch from "SYDLT5CG0209DNP" to "n550jv" at 2729,807 [2021-06-29T09:49:53] INFO: entering screen [2021-06-29T09:50:00] INFO: switch from "n550jv" to "SYDLT5CG0209DNP" at 0,749 [2021-06-29T09:50:00] INFO: leaving screen [2021-06-29T09:50:00] INFO: switch from "SYDLT5CG0209DNP" to "n550jv" at 2447,736 [2021-06-29T09:50:00] INFO: entering screen ```

gitea-mirror commented

2026-05-05 07:20:58 -06:00

Author

Owner

@dmascord commented on GitHub (Jun 28, 2021):

barrier.debug.log
This is the log generated at DEBUG2 on the server side

@dmascord commented on GitHub (Jun 28, 2021): [barrier.debug.log](https://github.com/debauchee/barrier/files/6729726/barrier.debug.log) This is the log generated at DEBUG2 on the server side

gitea-mirror commented

2026-05-05 07:20:59 -06:00

Author

Owner

@dmascord commented on GitHub (Jun 29, 2021):

barrier.log
Windows log

@dmascord commented on GitHub (Jun 29, 2021): [barrier.log](https://github.com/debauchee/barrier/files/6729748/barrier.log) Windows log

gitea-mirror commented

2026-05-05 07:21:01 -06:00

Author

Owner

@dmascord commented on GitHub (Jun 29, 2021):

Trackpad works, reddragon works, g203 doesn't work (all 3 connected to USB bus)
Disconnect g203, and plug back in g203, the g203 works now and transitions between server and client no problem...

@dmascord commented on GitHub (Jun 29, 2021): Trackpad works, reddragon works, g203 doesn't work (all 3 connected to USB bus) Disconnect g203, and plug back in g203, the g203 works now and transitions between server and client no problem...