You are not logged in.

#1 2020-11-10 18:56:57

arthur.spooner
Member
Registered: 2020-11-10
Posts: 3

Always need to repair bluetooth mouse after reboot

I cannot connect my already paired bluetooth mouse after reboot. I always need to remove the paired mouse and pair it again and then it works until reboot. When I disconnect the mouse and reconnect without reboot, everything works just fine. I also use bluetooth headphones, but don't need to repair them.
Any ideas?

System
Mouse: Logitech MX Master 2S
System: Kernel: 5.9.6-arch1-1 x86_64 bits: 64 compiler: N/A Desktop: i3 4.18.3 info: i3bar dm: GDM 3.38.2 Distro: Arch Linux
Machine: Type: Laptop System: Dell product: Latitude 5591 v: N/A serial: <filter> Chassis: type: 10 serial: <filter> Mobo: Dell model: 0DVVG1 v: A00 serial: <filter> UEFI: Dell v: 1.3.8 date: 08/08/2018

Packages
blueman 2.1.3-1
bluez 5.55-1
bluez-hid2hci 5.55-1
bluez-libs 5.55-1
bluez-utils 5.55-1
gnome-bluetooth 3.34.3-1
pulseaudio-bluetooth 13.99.3-1
pulseaudio-bluetooth-a2dp-gdm-fix 0.1-1

Last edited by arthur.spooner (2020-11-10 18:59:22)

Offline

#2 2020-11-10 20:50:52

GaKu999
Member
From: US/Eastern
Registered: 2020-06-21
Posts: 641

Re: Always need to repair bluetooth mouse after reboot

The journal is needed, with the current information the issue is not evident.
Use a plaintest pastebin client like ix.io to post the output of the full journal of the current boot, preferably a fresh boot replicating the issue.

Hint hint:
Full journal of current boot in ix.io:

# journalctl -b | curl -F 'f:1=<-' ix.io

Then post the output link.


My reposSome snippets

Heisenberg might have been here.

Offline

#3 2020-11-11 16:59:56

arthur.spooner
Member
Registered: 2020-11-10
Posts: 3

Re: Always need to repair bluetooth mouse after reboot

http://ix.io/2DNy

The bluetooth id of the device is D6:A2:AE:7F:70:75

Offline

#4 2020-11-14 21:25:13

mister.wardrop
Member
Registered: 2013-04-11
Posts: 6

Re: Always need to repair bluetooth mouse after reboot

I also have this issue as of a few weeks ago (also with a Logitech MX Master 2S): after every mouse disconnection I have to repair. I have two laptops, a Lenovo Thinkpad T480s (which doesn't experience this issue), and a Lenovo X1 Extreme (which does). Interestingly, the MAC of the mouse keeps changing (sequentially increasing after each pair).

In terms of system logs, immediately after a pair I see:

Nov 14 13:17:38 lawrence bluetoothd[834]: src/device.c:load_gatt_db() No cache for FE:B2:DB:B0:D8:23
Nov 14 13:17:39 lawrence gnome-shell[1600]: Can't update stage views actor StWidget is on because it needs an allocation.
Nov 14 13:17:40 lawrence bluetoothd[834]: profiles/input/hog-lib.c:report_value_cb() bt_uhid_send: Invalid argument (22)
Nov 14 13:17:40 lawrence bluetoothd[834]: profiles/input/hog-lib.c:report_value_cb() bt_uhid_send: Invalid argument (22)
Nov 14 13:17:40 lawrence bluetoothd[834]: profiles/input/hog-lib.c:report_value_cb() bt_uhid_send: Invalid argument (22)
Nov 14 13:17:40 lawrence kernel: input: MX Master 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B019.000E/input/input58
Nov 14 13:17:40 lawrence kernel: input: MX Master 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B019.000E/input/input59
Nov 14 13:17:40 lawrence kernel: hid-generic 0005:046D:B019.000E: input,hidraw8: BLUETOOTH HID v0.06 Keyboard [MX Master 2S] on d4:3b:04:0b:d8:9d
Nov 14 13:17:40 lawrence /usr/lib/gdm-x-session[1532]: (II) config/udev: Adding input device MX Master 2S Mouse (/dev/input/mouse5)
Nov 14 13:17:40 lawrence /usr/lib/gdm-x-session[1532]: (II) No input driver specified, ignoring this device.
Nov 14 13:17:40 lawrence /usr/lib/gdm-x-session[1532]: (II) This device may have been added with another device file.
Nov 14 13:17:40 lawrence /usr/lib/gdm-x-session[1532]: (II) config/udev: Adding input device MX Master 2S Mouse (/dev/input/event28)
Nov 14 13:17:40 lawrence /usr/lib/gdm-x-session[1532]: (**) MX Master 2S Mouse: Applying InputClass "libinput pointer catchall"
Nov 14 13:17:40 lawrence /usr/lib/gdm-x-session[1532]: (II) Using input driver 'libinput' for 'MX Master 2S Mouse'
Nov 14 13:17:40 lawrence /usr/lib/gdm-x-session[1532]: (II) systemd-logind: got fd for /dev/input/event28 13:92 fd 110 paused 0
Nov 14 13:17:40 lawrence /usr/lib/gdm-x-session[1532]: (**) MX Master 2S Mouse: always reports core events
Nov 14 13:17:40 lawrence /usr/lib/gdm-x-session[1532]: (**) Option "Device" "/dev/input/event28"
Nov 14 13:17:40 lawrence /usr/lib/gdm-x-session[1532]: (**) Option "_source" "server/udev"
Nov 14 13:17:40 lawrence /usr/lib/gdm-x-session[1532]: (II) event28 - MX Master 2S Mouse: is tagged by udev as: Mouse
Nov 14 13:17:40 lawrence /usr/lib/gdm-x-session[1532]: (II) event28 - MX Master 2S Mouse: device set to 1000 DPI
Nov 14 13:17:40 lawrence /usr/lib/gdm-x-session[1532]: (II) event28 - MX Master 2S Mouse: device is a pointer
Nov 14 13:17:40 lawrence /usr/lib/gdm-x-session[1532]: (II) event28 - MX Master 2S Mouse: device removed
Nov 14 13:17:40 lawrence /usr/lib/gdm-x-session[1532]: (**) Option "config_info" "udev:/sys/devices/virtual/misc/uhid/0005:046D:B019.000E/input/input59/event28"
Nov 14 13:17:40 lawrence /usr/lib/gdm-x-session[1532]: (II) XINPUT: Adding extended input device "MX Master 2S Mouse" (type: MOUSE, id 23)
Nov 14 13:17:40 lawrence /usr/lib/gdm-x-session[1532]: (**) Option "AccelerationScheme" "none"
Nov 14 13:17:40 lawrence /usr/lib/gdm-x-session[1532]: (**) MX Master 2S Mouse: (accel) selected scheme none/0
Nov 14 13:17:40 lawrence /usr/lib/gdm-x-session[1532]: (**) MX Master 2S Mouse: (accel) acceleration factor: 2.000
Nov 14 13:17:40 lawrence /usr/lib/gdm-x-session[1532]: (**) MX Master 2S Mouse: (accel) acceleration threshold: 4
Nov 14 13:17:40 lawrence /usr/lib/gdm-x-session[1532]: (II) event28 - MX Master 2S Mouse: is tagged by udev as: Mouse
Nov 14 13:17:40 lawrence /usr/lib/gdm-x-session[1532]: (II) event28 - MX Master 2S Mouse: device set to 1000 DPI
Nov 14 13:17:40 lawrence /usr/lib/gdm-x-session[1532]: (II) event28 - MX Master 2S Mouse: device is a pointer
Nov 14 13:17:40 lawrence systemd-logind[840]: Watching system buttons on /dev/input/event27 (MX Master 2S Keyboard)
Nov 14 13:17:40 lawrence /usr/lib/gdm-x-session[1532]: (II) config/udev: Adding input device MX Master 2S Keyboard (/dev/input/event27)
Nov 14 13:17:40 lawrence /usr/lib/gdm-x-session[1532]: (**) MX Master 2S Keyboard: Applying InputClass "libinput keyboard catchall"
Nov 14 13:17:40 lawrence /usr/lib/gdm-x-session[1532]: (II) Using input driver 'libinput' for 'MX Master 2S Keyboard'
Nov 14 13:17:40 lawrence /usr/lib/gdm-x-session[1532]: (II) systemd-logind: got fd for /dev/input/event27 13:91 fd 121 paused 0
Nov 14 13:17:40 lawrence /usr/lib/gdm-x-session[1532]: (**) MX Master 2S Keyboard: always reports core events
Nov 14 13:17:40 lawrence /usr/lib/gdm-x-session[1532]: (**) Option "Device" "/dev/input/event27"
Nov 14 13:17:40 lawrence /usr/lib/gdm-x-session[1532]: (**) Option "_source" "server/udev"
Nov 14 13:17:40 lawrence /usr/lib/gdm-x-session[1532]: (II) event27 - MX Master 2S Keyboard: is tagged by udev as: Keyboard
Nov 14 13:17:40 lawrence /usr/lib/gdm-x-session[1532]: (II) event27 - MX Master 2S Keyboard: device is a keyboard
Nov 14 13:17:40 lawrence /usr/lib/gdm-x-session[1532]: (II) event27 - MX Master 2S Keyboard: device removed
Nov 14 13:17:40 lawrence /usr/lib/gdm-x-session[1532]: (**) Option "config_info" "udev:/sys/devices/virtual/misc/uhid/0005:046D:B019.000E/input/input58/event27"
Nov 14 13:17:40 lawrence /usr/lib/gdm-x-session[1532]: (II) XINPUT: Adding extended input device "MX Master 2S Keyboard" (type: KEYBOARD, id 24)
Nov 14 13:17:40 lawrence /usr/lib/gdm-x-session[1532]: (II) event27 - MX Master 2S Keyboard: is tagged by udev as: Keyboard
Nov 14 13:17:40 lawrence /usr/lib/gdm-x-session[1532]: (II) event27 - MX Master 2S Keyboard: device is a keyboard

Upon turning off the mouse I see:

Nov 14 13:19:03 lawrence /usr/lib/gdm-x-session[1532]: (II) config/udev: removing device MX Master 2S Keyboard
Nov 14 13:19:03 lawrence /usr/lib/gdm-x-session[1532]: (**) Option "fd" "121"
Nov 14 13:19:03 lawrence /usr/lib/gdm-x-session[1532]: (II) event27 - MX Master 2S Keyboard: device removed
Nov 14 13:19:03 lawrence /usr/lib/gdm-x-session[1532]: (II) UnloadModule: "libinput"
Nov 14 13:19:03 lawrence /usr/lib/gdm-x-session[1532]: (II) systemd-logind: releasing fd for 13:91
Nov 14 13:19:03 lawrence /usr/lib/gdm-x-session[1532]: (EE) systemd-logind: failed to release device: Device not taken
Nov 14 13:19:03 lawrence /usr/lib/gdm-x-session[1532]: (II) config/udev: removing device MX Master 2S Mouse
Nov 14 13:19:03 lawrence /usr/lib/gdm-x-session[1532]: (**) Option "fd" "110"
Nov 14 13:19:03 lawrence /usr/lib/gdm-x-session[1532]: (II) event28 - MX Master 2S Mouse: device removed
Nov 14 13:19:03 lawrence /usr/lib/gdm-x-session[1532]: (II) UnloadModule: "libinput"
Nov 14 13:19:03 lawrence /usr/lib/gdm-x-session[1532]: (II) systemd-logind: releasing fd for 13:92

After turning back on the mouse, I see nothing in the logs; and after repairing, I see the exact same logs as above except that the mac address has incremented; e.g. in this case from FE:B2:DB:B0:D8:23 to FE:B2:DB:B0:D8:24.

The MAC address cycling may be a mouse feature to stop older paired devices from interfering with the pairing process; but I have no idea why the laptop can no longer connect to the mouse without repairing. Likely this was due to a bluez or kernel update... time to do some debugging.

Offline

#5 2020-11-15 09:46:03

arthur.spooner
Member
Registered: 2020-11-10
Posts: 3

Re: Always need to repair bluetooth mouse after reboot

I also did not experience this behavior until the last update. Unfortunately I don't know, which packages have been updated and led to this issue.

Offline

#6 2021-02-05 06:59:29

vlado9
Member
Registered: 2015-11-21
Posts: 4

Re: Always need to repair bluetooth mouse after reboot

Let me share some ideas (wild guess). MX Master 2S Mouse is able to pair with 3 devices. The switch at the bottom of the mouse shows active selection. Haven't you paired more selections?  This might explain why you see MAC address incremented. Run `bluetoothctl` (as root) and see the `paired-devices`. Preen the list if you find more than one MX Master 2S Mouse, or try to select the "correct" MAC if you want to experiment.

Last edited by vlado9 (2021-02-05 07:37:36)

Offline

Board footer

Powered by FluxBB