[GH-ISSUE #419] When Barrier server before PR #391 connects to a client after PR #391, horizontall mouse scroll results to Browser back button #322

New issue

Open

opened 2026-05-05 06:02:26 -06:00 by gitea-mirror · 4 comments

gitea-mirror commented

2026-05-05 06:02:26 -06:00

Owner

Originally created by @p12tic on GitHub (Aug 24, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/419

Operating Systems and Barrier Version

Server: Ubuntu Linux before https://github.com/debauchee/barrier/pull/391

Client: Ubuntu Linux after https://github.com/debauchee/barrier/pull/391

Steps to reproduce bug

Start xev on the client, move mouse over it and try to scroll horizontally. The expected buttons are button 6 and 7 whereas we're getting buttons 8 and 9.

This will be annoying for the end users so we need some kind of version check when new client connects to an old server to bring back old behavior.

Originally created by @p12tic on GitHub (Aug 24, 2019). Original GitHub issue: https://github.com/debauchee/barrier/issues/419 ### Operating Systems and Barrier Version ### Server: Ubuntu Linux before https://github.com/debauchee/barrier/pull/391 Client: Ubuntu Linux after https://github.com/debauchee/barrier/pull/391 ### Steps to reproduce bug ### Start `xev` on the client, move mouse over it and try to scroll horizontally. The expected buttons are button 6 and 7 whereas we're getting buttons 8 and 9. This will be annoying for the end users so we need some kind of version check when new client connects to an old server to bring back old behavior.

gitea-mirror added the

bug

label 2026-05-05 06:02:26 -06:00

gitea-mirror commented

2026-05-05 06:02:30 -06:00

Author

Owner

@EbonJaeger commented on GitHub (Aug 24, 2019):

If we're doing version checking, wouldn't it then be better to instead translate the bad calls from the server to the correct ones on the client? It's known that the offset is 2 from pre-PR code: 51118014b1/src/lib/platform/XWindowsScreen.cpp (L1873-L1877)

The next question is then where should this check and correction be done?

@EbonJaeger commented on GitHub (Aug 24, 2019): If we're doing version checking, wouldn't it then be better to instead translate the bad calls from the server to the correct ones on the client? It's known that the offset is 2 from pre-PR code: https://github.com/debauchee/barrier/blob/51118014b14d59f5897b65e338f6f335462f4c06/src/lib/platform/XWindowsScreen.cpp#L1873-L1877 The next question is then *where* should this check and correction be done?

gitea-mirror commented

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

Author

Owner

@quintinm-dev commented on GitHub (Apr 26, 2020):

If anyone else is having issues with the back/forward buttons not working on the client, this ended up being the cause for me. Also, maybe this is obvious from the code, but the issue also happens with Windows/Linux in both client/server configurations.

@quintinm-dev commented on GitHub (Apr 26, 2020): If anyone else is having issues with the back/forward buttons not working on the client, this ended up being the cause for me. Also, maybe this is obvious from the code, but the issue also happens with Windows/Linux in both client/server configurations.

gitea-mirror commented

2026-05-05 06:02:34 -06:00

Author

Owner

@Ayanmullick commented on GitHub (Jul 1, 2020):

I'm using the latest version on Win10 client and server. The horizontal scroll thru the wheel on a Microsoft Sculpt Comfort mouse doesn't work. Horizontal scrolling works on the server but not on the client.

@Ayanmullick commented on GitHub (Jul 1, 2020): I'm using the latest version on Win10 client and server. The horizontal scroll thru the wheel on a [Microsoft Sculpt Comfort mouse](https://www.amazon.com/Microsoft-Sculpt-Comfort-Bluetooth-H3S-00001/dp/B00BZC31WQ) doesn't work. Horizontal scrolling works on the server but not on the client.

gitea-mirror commented

2026-05-05 06:02:36 -06:00

Author

Owner

@Ayanmullick commented on GitHub (Sep 20, 2020):

Upgrading to the latest version resolved the issue for me.

@Ayanmullick commented on GitHub (Sep 20, 2020): Upgrading to the latest version resolved the issue for me.