First, my master mouse does work with NixOS. But, enabling the mouse requires turning it off and on twice. After turning it on the second time, the mouse works perfectly.
Any settings I can tweak?
That’s a pretty strange behavior, mice usually just work. Anything relevant in journalctl? Is it the same behavior on any USB port? Do you use a USB hub?
I left out one detail. The Master MX mouse is a bluetooth mouse. USB port is not relevant unless I charge the mouse. Yes, I did try having the MX physically connected. It did not change the behavior I described.
Looking in journalctl, I did find something. It is in reverse order.
ESCOD
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Logitech Wireless Mouse MX Master 3: Applying InputClass "libinput mouse configurati>
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Logitech Wireless Mouse MX Master 3: Applying InputClass “libinput keyboard catchall”
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Logitech Wireless Mouse MX Master 3: Applying InputClass “libinput pointer catchall”
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Logitech Wireless Mouse MX Master 3: Applying InputClass “evdev keyboard catchall”
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Logitech Wireless Mouse MX Master 3: Applying InputClass “evdev pointer catchall”
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Logitech Wireless Mouse MX Master 3: Applying InputClass “Keyboard catchall”
Apr 25 18:43:44 nixos xserver-wrapper[967]: (EE) libinput: Logitech Wireless Mouse MX Master 3: Failed to set scroll to twofinger
Apr 25 18:43:44 nixos xserver-wrapper[967]: (II) event12 - Logitech Wireless Mouse MX Master 3: device is a keyboard
Apr 25 18:43:44 nixos xserver-wrapper[967]: (II) event12 - Logitech Wireless Mouse MX Master 3: device is a pointer
Apr 25 18:43:44 nixos xserver-wrapper[967]: (II) event12 - Logitech Wireless Mouse MX Master 3: is tagged by udev as: Keyboard Mouse
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Logitech Wireless Mouse MX Master 3: (accel) acceleration threshold: 4
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Logitech Wireless Mouse MX Master 3: (accel) acceleration factor: 2.000
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Logitech Wireless Mouse MX Master 3: (accel) selected scheme none/0
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Option “AccelerationScheme” “none”
Apr 25 18:43:44 nixos xserver-wrapper[967]: (EE) libinput: Logitech Wireless Mouse MX Master 3: Failed to set scroll to twofingerApr 25 18:43:44 nixos xserver-wrapper[967]: (II) XINPUT: Adding extended input device “Logitech Wireless Mouse MX Master 3” (type: MO>
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Option “config_info” "udev:/sys/devices/virtual/misc/uhid/0005:046D:B023.0002/input/>
Apr 25 18:43:44 nixos xserver-wrapper[967]: (II) libinput: Logitech Wireless Mouse MX Master 3: needs a virtual subdevice
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Option “HorizontalScrolling” “on”
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Option “MiddleEmulation” “on”
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Option “ScrollMethod” “twofinger”
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Option “LeftHanded” “off”
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Option “SendEventsMode” “enabled”
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Option “NaturalScrolling” “off”
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Option “AccelProfile” “adaptive”
Apr 25 18:43:44 nixos systemd-logind[780]: Watching system buttons on /dev/input/event12 (Logitech Wireless Mouse MX Master 3)
Apr 25 18:43:44 nixos xserver-wrapper[967]: (II) event12 - Logitech Wireless Mouse MX Master 3: device removed
Apr 25 18:43:44 nixos xserver-wrapper[967]: (II) event12 - Logitech Wireless Mouse MX Master 3: device is a keyboard
Apr 25 18:43:44 nixos xserver-wrapper[967]: (II) event12 - Logitech Wireless Mouse MX Master 3: device is a pointer
Apr 25 18:43:44 nixos xserver-wrapper[967]: (II) event12 - Logitech Wireless Mouse MX Master 3: is tagged by udev as: Keyboard Mouse
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Option “_source” “server/udev”
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Option “Device” “/dev/input/event12”
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Logitech Wireless Mouse MX Master 3: always reports core events
Apr 25 18:43:44 nixos xserver-wrapper[967]: (II) Using input driver ‘libinput’ for ‘Logitech Wireless Mouse MX Master 3’
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Logitech Wireless Mouse MX Master 3: Applying InputClass "libinput mouse configurati>
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Logitech Wireless Mouse MX Master 3: Applying InputClass “libinput keyboard catchall”
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Logitech Wireless Mouse MX Master 3: Applying InputClass “libinput pointer catchall”
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Logitech Wireless Mouse MX Master 3: Applying InputClass “evdev keyboard catchall”
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Logitech Wireless Mouse MX Master 3: Applying InputClass “evdev pointer catchall”
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Logitech Wireless Mouse MX Master 3: Applying InputClass “Keyboard catchall”
Apr 25 18:43:44 nixos xserver-wrapper[967]: (II) config/udev: Adding input device Logitech Wireless Mouse MX Master 3 (/dev/input/eve>
Apr 25 18:43:44 nixos xserver-wrapper[967]: (II) This device may have been added with another device file.
Apr 25 18:43:44 nixos xserver-wrapper[967]: (II) No input driver specified, ignoring this device.
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Logitech Wireless Mouse MX Master 3: Applying InputClass “Keyboard catchall”
Apr 25 18:43:44 nixos xserver-wrapper[967]: (II) config/udev: Adding input device Logitech Wireless Mouse MX Master 3 (/dev/input/mou>
Apr 25 18:43:44 nixos kernel: logitech-hidpp-device 0005:046D:B023.0002: input,hidraw0: BLUETOOTH HID v0.15 Keyboard [Logitech Wirele>
Apr 25 18:43:44 nixos kernel: input: Logitech Wireless Mouse MX Master 3 as /devices/virtual/misc/uhid/0005:046D:B023.0002/input/inpu>
Apr 25 18:43:44 nixos upowerd[1045]: treating change event as add on /sys/devices/virtual/misc/uhid/0005:046D:B023.0002/power_supply/>
Apr 25 18:43:43 nixos kernel: logitech-hidpp-device 0005:046D:B023.0002: HID++ 4.5 device connected.
Apr 25 18:43:35 nixos kernel: logitech-hidpp-device 0005:046D:B023.0001: Device not connected
Apr 25 18:43:35 nixos bluetoothd[727]: profiles/input/hog-lib.c:set_report_cb() Error setting Report value: Unexpected error code
Apr 25 18:43:35 nixos kernel: hid-generic 0005:046D:B023.0001: input,hidraw0: BLUETOOTH HID v0.15 Keyboard [MX Master 3] on 80:c5:f2:>
Apr 25 18:43:35 nixos kernel: input: MX Master 3 Mouse as /devices/virtual/misc/uhid/0005:046D:B023.0001/input/input14
Apr 25 18:43:35 nixos kernel: input: MX Master 3 Keyboard as /devices/virtual/misc/uhid/0005:046D:B023.0001/input/input13
Apr 25 18:43:34 nixos kernel: hid: raw HID events driver (C) Jiri Kosina
Apr 25 18:43:34 nixos systemd[1012]: Reached target Bluetooth.
I left out one detail. The Master MX mouse is a bluetooth mouse. USB port is not relevant unless I charge the mouse. Yes, I did try having the MX physically connected. It did not change the behavior I described.
Looking in journalctl, I did find something. It is in reverse order.
ESCOD
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Logitech Wireless Mouse MX Master 3: Applying InputClass "libinput mouse configurati>
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Logitech Wireless Mouse MX Master 3: Applying InputClass “libinput keyboard catchall”
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Logitech Wireless Mouse MX Master 3: Applying InputClass “libinput pointer catchall”
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Logitech Wireless Mouse MX Master 3: Applying InputClass “evdev keyboard catchall”
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Logitech Wireless Mouse MX Master 3: Applying InputClass “evdev pointer catchall”
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Logitech Wireless Mouse MX Master 3: Applying InputClass “Keyboard catchall”
Apr 25 18:43:44 nixos xserver-wrapper[967]: (EE) libinput: Logitech Wireless Mouse MX Master 3: Failed to set scroll to twofinger
Apr 25 18:43:44 nixos xserver-wrapper[967]: (II) event12 - Logitech Wireless Mouse MX Master 3: device is a keyboard
Apr 25 18:43:44 nixos xserver-wrapper[967]: (II) event12 - Logitech Wireless Mouse MX Master 3: device is a pointer
Apr 25 18:43:44 nixos xserver-wrapper[967]: (II) event12 - Logitech Wireless Mouse MX Master 3: is tagged by udev as: Keyboard Mouse
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Logitech Wireless Mouse MX Master 3: (accel) acceleration threshold: 4
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Logitech Wireless Mouse MX Master 3: (accel) acceleration factor: 2.000
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Logitech Wireless Mouse MX Master 3: (accel) selected scheme none/0
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Option “AccelerationScheme” “none”
Apr 25 18:43:44 nixos xserver-wrapper[967]: (EE) libinput: Logitech Wireless Mouse MX Master 3: Failed to set scroll to twofingerApr 25 18:43:44 nixos xserver-wrapper[967]: (II) XINPUT: Adding extended input device “Logitech Wireless Mouse MX Master 3” (type: MO>
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Option “config_info” "udev:/sys/devices/virtual/misc/uhid/0005:046D:B023.0002/input/>
Apr 25 18:43:44 nixos xserver-wrapper[967]: (II) libinput: Logitech Wireless Mouse MX Master 3: needs a virtual subdevice
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Option “HorizontalScrolling” “on”
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Option “MiddleEmulation” “on”
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Option “ScrollMethod” “twofinger”
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Option “LeftHanded” “off”
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Option “SendEventsMode” “enabled”
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Option “NaturalScrolling” “off”
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Option “AccelProfile” “adaptive”
Apr 25 18:43:44 nixos systemd-logind[780]: Watching system buttons on /dev/input/event12 (Logitech Wireless Mouse MX Master 3)
Apr 25 18:43:44 nixos xserver-wrapper[967]: (II) event12 - Logitech Wireless Mouse MX Master 3: device removed
Apr 25 18:43:44 nixos xserver-wrapper[967]: (II) event12 - Logitech Wireless Mouse MX Master 3: device is a keyboard
Apr 25 18:43:44 nixos xserver-wrapper[967]: (II) event12 - Logitech Wireless Mouse MX Master 3: device is a pointer
Apr 25 18:43:44 nixos xserver-wrapper[967]: (II) event12 - Logitech Wireless Mouse MX Master 3: is tagged by udev as: Keyboard Mouse
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Option “_source” “server/udev”
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Option “Device” “/dev/input/event12”
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Logitech Wireless Mouse MX Master 3: always reports core events
Apr 25 18:43:44 nixos xserver-wrapper[967]: (II) Using input driver ‘libinput’ for ‘Logitech Wireless Mouse MX Master 3’
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Logitech Wireless Mouse MX Master 3: Applying InputClass "libinput mouse configurati>
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Logitech Wireless Mouse MX Master 3: Applying InputClass “libinput keyboard catchall”
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Logitech Wireless Mouse MX Master 3: Applying InputClass “libinput pointer catchall”
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Logitech Wireless Mouse MX Master 3: Applying InputClass “evdev keyboard catchall”
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Logitech Wireless Mouse MX Master 3: Applying InputClass “evdev pointer catchall”
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Logitech Wireless Mouse MX Master 3: Applying InputClass “Keyboard catchall”
Apr 25 18:43:44 nixos xserver-wrapper[967]: (II) config/udev: Adding input device Logitech Wireless Mouse MX Master 3 (/dev/input/eve>
Apr 25 18:43:44 nixos xserver-wrapper[967]: (II) This device may have been added with another device file.
Apr 25 18:43:44 nixos xserver-wrapper[967]: (II) No input driver specified, ignoring this device.
Apr 25 18:43:44 nixos xserver-wrapper[967]: () Logitech Wireless Mouse MX Master 3: Applying InputClass “Keyboard catchall”
Apr 25 18:43:44 nixos xserver-wrapper[967]: (II) config/udev: Adding input device Logitech Wireless Mouse MX Master 3 (/dev/input/mou>
Apr 25 18:43:44 nixos kernel: logitech-hidpp-device 0005:046D:B023.0002: input,hidraw0: BLUETOOTH HID v0.15 Keyboard [Logitech Wirele>
Apr 25 18:43:44 nixos kernel: input: Logitech Wireless Mouse MX Master 3 as /devices/virtual/misc/uhid/0005:046D:B023.0002/input/inpu>
Apr 25 18:43:44 nixos upowerd[1045]: treating change event as add on /sys/devices/virtual/misc/uhid/0005:046D:B023.0002/power_supply/>
Apr 25 18:43:43 nixos kernel: logitech-hidpp-device 0005:046D:B023.0002: HID++ 4.5 device connected.
Apr 25 18:43:35 nixos kernel: logitech-hidpp-device 0005:046D:B023.0001: Device not connected
Apr 25 18:43:35 nixos bluetoothd[727]: profiles/input/hog-lib.c:set_report_cb() Error setting Report value: Unexpected error code
Apr 25 18:43:35 nixos kernel: hid-generic 0005:046D:B023.0001: input,hidraw0: BLUETOOTH HID v0.15 Keyboard [MX Master 3] on 80:c5:f2:>
Apr 25 18:43:35 nixos kernel: input: MX Master 3 Mouse as /devices/virtual/misc/uhid/0005:046D:B023.0001/input/input14
Apr 25 18:43:35 nixos kernel: input: MX Master 3 Keyboard as /devices/virtual/misc/uhid/0005:046D:B023.0001/input/input13
Apr 25 18:43:34 nixos kernel: hid: raw HID events driver (C) Jiri Kosina
Apr 25 18:43:34 nixos systemd[1012]: Reached target Bluetooth.
Ports can still be relevant even with Bluetooth if the BT receiver isn’t built-in to your motherboard.
Which portion of those logs are from before you turned the mouse off then back on?
If this is the issue I think it is, it was fixed in hog: Fix read order of attributes · bluez/bluez@7fe38a1 · GitHub, which is a part of BlueZ 5.64 that is now in nixos-unstable as of a few days ago.
The BT receiver is integrated with the motherboard. The portion of the logs is just after boot up but prior to logon - approximately. I tested the mouse connection while the computer was at the log on screen.
Thanks for the update. I will watch for the bluez update and see if it does make a difference.
Try in all usb ports, go for the 2.0 ports, 3.1 ports can cause issues sometimes.