Logitech MX Master

From ArchWiki
Jump to navigation Jump to search

Logitech MX Master


The mouse should work with no special configuration if using the unified receiver USB dongle. Plug in the dongle, then press the connect button on the mouse.

To use Bluetooth, change the channel on the bottom of the mouse, and click the connect button. Now, search for the mouse with a bluetooth manager of your choice and pair. In future it should connect as soon as you switch to that channel when your bluetooth is active. If you have problems with the mouse not showing when scanning, see Bluetooth LE device does not show up in scan

List of events sent by mouse

Physical action detected as
Left button button 1
Press to wheel button 2
Right button button 3
Scroll wheel up button 4
Scroll wheel down button 5
Press "i" button under wheel undetectable in linux
Scroll hor_wheel right (up) button 6
Scroll hor_wheel left (down) button 7
Side-bottom button button 8
Side-top button button 9
Thumb button Ctrl+Alt+Tab


  • It is impossible to move mouse cursor while thumb button is pressed, but possible to use any other actions (pressing buttons and scrolling wheels). Ctrl+Alt+Tab event is sent only after releasing thumb button.
  • If you wish, you can get experience of thumb button like in Windows or Mac. In kde go to System settings → Shortcuts → Global Shortcuts → KWin → Show all windows from all desktops. It is set to ctrl+f10 by default. Set ctrl+alt+tab for this action and apply settings.
  • "I" button under wheel is undetectable in linux, but works as switching wheel between free and rattle mode
  • Logitech gestures (moving mouse up/down/left/right while thumb pressed) are not detected in linux.

Mappings for extra buttons

The vertical wheel and the two buttons near it should work right away, however the thumb button requires some special treatment, and you might want to remap the rest.

To remap the buttons of the mouse you can use the packages xbindkeys and xautomation.

xbindkeys will redirect the buttons and xte (which is included in xautomation) will execute the custom key presses. To do so, create a config file named .xbindkeysrc in your home directory.

Here is a sample configuration for the vertical scroll wheel and the two buttons near it:

# thumb wheel up => increase volume and unmute      
"amixer -D pulse set Master 4000+ unmute"
# thumb wheel down => lower volume       
"amixer -D pulse set Master 4000-"       
# backward button => previous song       
"xte 'key XF86AudioPrev'"                
# forward button => next song            
"xte 'key XF86AudioNext'"                

If using PulseAudio (more info here):

# thumb wheel up => increase volume
"pactl set-sink-volume @DEFAULT_SINK@ +2%"

# thumb wheel down => lower volume
"pactl set-sink-volume @DEFAULT_SINK@ -2%"

If you prefer to get a visual feedback on how the volume level changes you could use the following lines instead (Tested in GNOME and KDE)

# thumb wheel up => increase volume
"xte 'key XF86AudioRaiseVolume'"

# thumb wheel down => lower volume
"xte 'key XF86AudioLowerVolume'"

Now start xbindkeys, preferably add that to the autostart list of your desktop environment.

The thumb button is special. With the Logitech software available for Windows and Mac, you would be able to map up to 5 actions to it: by pressing the button or by pressing the button and moving the mouse in one of four directions. As of November 2015, there is no way to enable the direction feature using Arch.

If you look at the keys the button triggers you will notice that it sends a series of keys, confusing xbindkeys. You need to add a short sleep here so xbindkeys will only react on the first keys send so we can at least map one action to it:

# thumb button => play/pause music         
# Credit to gregmuellegger https://bbs.archlinux.org/viewtopic.php?pid=1551271#p1551271                               
# We need a sleep here since the button triggers a few more key codes. 
# It also triggers Control+Mod2+Control_L and Alt+Mod2+Alt_L. The sleep       
# prevents that X receives those keypresses simultaniously. Therefore they    
# might interfere and trigger unwanted actions. By the sleep we make sure that
# the Alt+Left is receive as distinct event.                                  
"sleep 0.1 && xte 'key XF86AudioPlay'"                                        
   m:0xc + c:23

Remember that all changes to ~/.xbindkeysrc require a restart of the xbindkeys process:

$ pkill xbindkeys && xbindkeys


Battery status can be read as described on Logitech Unifying Receiver. e.g. Solaar (solaar) has a system tray utility.

Smart shift

In order to change the sensitivity of changing the mouse wheel mode (between hyperfast and click-to-click), install solaar. A slider appears that can be set somewhere between 0 and 50 (inclusive). 0 means always in hyperfast mode, 50 means always in click-to-click mode.

To change the sensitivity, change this value somewhere between 0 and 50.

Laggy mouse movements in Bluetooth mode

Try this solution: Bluetooth#Bluetooth mouse laggy movements