github-starred/barrier

Fork 0

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

[GH-ISSUE #1080] Logitech MX Ergo back and forward buttons register as middle clicks on Barrier client #861

New issue

Open

opened 2026-05-05 07:13:37 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 07:13:37 -06:00

Owner

Originally created by @BenBergman on GitHub (Feb 26, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1080

Describe the bug
I have a Logitech MX Ergo and a Logitech M570 mouse. Both have back and forward buttons that register as buttons 8 and 9 respectively when checked with xev on my Arch Linux Barrier server machine. On my macOS client, the back and forward buttons both show up as mouse button 2 (middle click) in xev when using barrier to control the cursor on there. If I connect the MX Ergo directly to the macOS machine, I noticed no events are registered in xev, but backward and forward actions work in Firefox and Finder.

The Logitech Options configuration software on macOS shows that the forward and backward buttons are mapped to "Forward" and "Back". Perhaps the macOS API has a specific way it requires mouse drivers to send those back and forward events?

I'd be happy to do some sort of remap in my config (though I couldn't find information on that), but this feels like something that should ideally be more automatic for new users.

To Reproduce

Steps to reproduce the behavior:

Connect a macOS client to a Linux (or possibly other) server that has a mouse with back/forward buttons
Move the mouse to the macOS client to a browser window with back or forward history
Press the back or forward button
Cursor scroll circle thing comes up instead of navigating through window history

Expected behavior
Pressing back and forward mouse buttons on a macOS client should move backwards and forwards through an application's history

Desktop (please complete the following information):

Server OS: Arch Linux 5.10.17
Server Barrier version: 2.3.3
Client OS: macOS Catalina 10.15.7
Client Barrier version: 2.3.3

Originally created by @BenBergman on GitHub (Feb 26, 2021). Original GitHub issue: https://github.com/debauchee/barrier/issues/1080 **Describe the bug** I have a Logitech MX Ergo and a Logitech M570 mouse. Both have back and forward buttons that register as buttons 8 and 9 respectively when checked with xev on my Arch Linux Barrier server machine. On my macOS client, the back and forward buttons both show up as mouse button 2 (middle click) in xev when using barrier to control the cursor on there. If I connect the MX Ergo directly to the macOS machine, I noticed no events are registered in xev, but backward and forward actions work in Firefox and Finder. The Logitech Options configuration software on macOS shows that the forward and backward buttons are mapped to "Forward" and "Back". Perhaps the macOS API has a specific way it requires mouse drivers to send those back and forward events? I'd be happy to do some sort of remap in my config (though I couldn't find information on that), but this feels like something that should ideally be more automatic for new users. **To Reproduce** Steps to reproduce the behavior: 1. Connect a macOS client to a Linux (or possibly other) server that has a mouse with back/forward buttons 2. Move the mouse to the macOS client to a browser window with back or forward history 3. Press the back or forward button 4. Cursor scroll circle thing comes up instead of navigating through window history **Expected behavior** Pressing back and forward mouse buttons on a macOS client should move backwards and forwards through an application's history **Desktop (please complete the following information):** - Server OS: Arch Linux 5.10.17 - Server Barrier version: 2.3.3 - Client OS: macOS Catalina 10.15.7 - Client Barrier version: 2.3.3

gitea-mirror commented

2026-05-05 07:13:39 -06:00

Author

Owner

@BenBergman commented on GitHub (Feb 26, 2021):

After a bit more searching, I found this other open source app that seems to indicate extra buttons acting as middle click is a macOS bug and their app aims to fix it.

https://sensible-side-buttons.archagon.net/

Sensible Side Buttons fixes the issue for me. Based on the description on the page, macOS ignores back/forward mouse buttons, but some mouse drivers run a 3-finger swipe gesture to trigger a back/forward action. SSB enables this for other mice, apparently including Barrier.

I still think it would be great to have this integrated in Barrier, but this is definitely a macOS bug and SSB seems to be a solid work around for now.

@BenBergman commented on GitHub (Feb 26, 2021): After a bit more searching, I found this other open source app that seems to indicate extra buttons acting as middle click is a macOS bug and their app aims to fix it. https://sensible-side-buttons.archagon.net/ Sensible Side Buttons fixes the issue for me. Based on the description on the page, macOS ignores back/forward mouse buttons, but some mouse drivers run a 3-finger swipe gesture to trigger a back/forward action. SSB enables this for other mice, apparently including Barrier. I still think it would be great to have this integrated in Barrier, but this is definitely a macOS bug and SSB seems to be a solid work around for now.

No labels

Rows
Columns