Bug#1051432: bluez 5.6.9 Some bluetooth mouse not working, problem persists

Terrance Hendrik

unread,

Sep 7, 2023, 5:10:05 PM9/7/23

to

Package: bluez

Version: 5.6.9-1

Not sure if this issue is about bluez or other packages or modules

System info:

```
$ lsb_release -a
No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux trixie/sid
Release:	n/a
Codename:	trixie

$ uname -a
Linux <hostname> 6.4.0-4-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.4.13-1 (2023-08-31) x86_64 GNU/Linux

```

journalctl -f, after connected


```
Sep 08 04:57:06 <hostname> blueman-manager[11378]: blueman-manager 04.57.06 WARNING  ManagerDeviceList:396 _monitor_power_levels: Failed to get power levels, probably a LE device.
Sep 08 04:57:06 <hostname> bluetoothd[1053]: src/service.c:service_accept() input-hog profile accept failed for <BTMAC>
Sep 08 04:57:06 <hostname> bluetoothd[1053]: src/service.c:service_accept() input-hog profile accept failed for <BTMAC>
```

Bluetooth adapter: 8087:0026 Intel Corp. AX201 Bluetooth


Mouse is Logitech MX Anywhere 3, and MX Master 3. connected to Bluetooth.

Terrance Hendrik

unread,

Sep 7, 2023, 6:00:06 PM9/7/23

to

bluetoothctl

[MX Anywhere 3]# info

Device E5:9F:06:B5:08:8D (random)
Name: MX Anywhere 3
Alias: MX Anywhere 3
Appearance: 0x03c2 (962)
Icon: input-mouse
Paired: yes
Bonded: yes
Trusted: yes
Blocked: no
Connected: yes
WakeAllowed: no
LegacyPairing: no
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Battery Service (0000180f-0000-1000-8000-00805f9b34fb)
UUID: Human Interface Device (00001812-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (00010000-0000-1000-8000-011f2000046d)
Modalias: usb:v046DpB025d0014
Battery Percentage: 0x4b (75)

Nobuhiro Iwamatsu

unread,

Oct 24, 2023, 2:20:05 AM10/24/23

to

Hi,

2023年9月8日(金) 6:57 Terrance Hendrik <terrance...@gmail.com>:

Could you please set ClassicBondedOnly=true and LEAutoSecurity=true in
/etc/bluetooth/input.conf and check?

```
[General]
ClassicBondedOnly = true
LEAutoSecurity = true
```

Best regards,
Nobuhiro

--
Nobuhiro Iwamatsu
iwamatsu at {nigauri.org / debian.org / kernel.org}
GPG ID: 32247FBB40AD1FA6

Terrance Hendrik

unread,

Nov 15, 2023, 9:20:05 AM11/15/23

to

Thank you, Iwanmatsu san!

But no luck,still logs

```

Nov 14 21:44:49 <hostname> blueman-manager[10028]: blueman-manager 21.44.49 WARNING ManagerDeviceList:396 _monitor_power_levels: Failed to get power levels, probably a LE device.
Nov 14 21:44:49 <hostname> bluetoothd[9996]: src/service.c:service_accept() input-hog profile accept failed for <MAC>
Nov 14 21:44:51 <hostname> bluetoothd[9996]: src/service.c:service_accept() input-hog profile accept failed for <MAC>

```

I uncommented those lines and restarted bluetooth.service.

Also tried adding `--experimental` to service execstart, only gets worse.

Strangely, other 3 computers running almost the same kernel 6.3-6.5 and bluez 5.6x - 5.70, logi mice work perfectly fine.

Terrance Hendrik

unread,

Nov 17, 2023, 3:40:06 AM11/17/23

to

seems more like an issue with kernel/gui than bluez.

checked my modprobe.d blacklists, most are system default.

```

blacklist ath_pci
blacklist evbug
blacklist usbmouse
blacklist usbkbd
blacklist eepro100
blacklist de4x5
blacklist eth1394
blacklist snd_intel8x0m
blacklist snd_aw2
blacklist prism54
blacklist bcm43xx
blacklist garmin_gps
blacklist asus_acpi
blacklist snd_pcsp
blacklist pcspkr
blacklist amd76x_edac
blacklist ohci1394
blacklist sbp2
blacklist dv1394
blacklist raw1394
blacklist video1394
blacklist aty128fb
blacklist atyfb
blacklist radeonfb
blacklist cirrusfb
blacklist cyber2000fb
blacklist cyblafb
blacklist gx1fb
blacklist hgafb
blacklist i810fb
blacklist intelfb
blacklist kyrofb
blacklist lxfb
blacklist matroxfb_base
blacklist neofb
blacklist nvidiafb
blacklist pm2fb
blacklist rivafb
blacklist s1d13xxxfb
blacklist savagefb
blacklist sisfb
blacklist sstfb
blacklist tdfxfb
blacklist tridentfb
blacklist vfb
blacklist viafb
blacklist vt8623fb
blacklist udlfb
blacklist intel_hid
blacklist sparse_keymap
blacklist nfc
blacklist pn533
blacklist pn533_usb
blacklist nouveau
blacklist hackrf

```

Is it possible something's wrong with DKMS? the other 3 computers have no DKMS.

Terrance Hendrik

unread,

Jan 26, 2024, 8:00:05 AM1/26/24

to

Update 2024-01-26

1. It has nothing to do with GUI. In text mode the issue is the same.

2. it has nothing to do with DKMS, removing it changes nothing.

3. I swapped SSD between 2 computers, the issue goes with the SSD. So it's not a hardware issue

4. I `apt purge` bluez and blueman, removed /etc/bluetooth, then reinstall them, the issue persists.

5. I compared files in /etc/udev/rules.d and /lib/modules on both computer, they are identical.

only difference is modules.dep*, modules.symbols* and extra dkms modules.

6. other info

on the working OS, connecting a logitech mouse has 2 syslog messages

```

... blueman-manager[7228]: blueman-manager 18.32.55 WARNING ManagerDeviceList:396 _monitor_power_levels: Failed to get power levels, probably a LE device.
... kernel: input: MX Anywhere 3 Mouse as /devices/virtual/misc/uhid/0005:046D:B025.000D/input/input37
... kernel: hid-generic 0005:046D:B025.000D: input,hidraw5: BLUETOOTH HID v0.14 Mouse [MX Anywhere 3] on <MAC>

```

on the NOT working OS, connecting a logitech mouse has 2 syslog messages

```

... thWJ16P bluetoothd[7933]: src/service.c:service_accept() input-hog profile accept failed for F6:8C:E4:DD:B8:6B<MAC>
... thWJ16P bluetoothd[7933]: src/service.c:service_accept() input-hog profile accept failed for F6:8C:E4:DD:B8:6B<MAC>

```

7. Final Question:

What else can affect the behavior between bluez and the kernel??

On Fri, Nov 17, 2023 at 8:36 AM Debian Bug Tracking System <ow...@bugs.debian.org> wrote:

Thank you for the additional information you have supplied regarding
this Bug report.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
Debian Bluetooth Maintainers <team+pkg-...@tracker.debian.org>

If you wish to submit further information on this problem, please
send it to 105...@bugs.debian.org.

Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.

--
1051432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051432
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Terrance Hendrik

unread,

Jan 27, 2024, 3:00:06 AM1/27/24

to

I fixed this, after months of research.

This is not an issue of bluez.

hidp/uhid really IS the problem. I don't know what makes a Linux decide to load `uhid` or `hidp`, my "good" and "bad" Linux SSD are dd'ed from same source, and they even have same partition uuid.

long story short, blacklist hidp and force load uhid kernel module, all mice work happily now!

echo "blacklist hidp" | sudo tee /etc/modprobe.d/blacklist-hidp.conf
echo -e  "# Fix BLE mouse issue\nuhid" | sudo tee /etc/modules-load.d/uhid.conf
cp --update=none /etc/bluetooth/input.conf{,backup}
sudo sed -ie "s:.*UserspaceHID=.*:UserspaceHID=true:" /etc/bluetooth/input.conf

then reboot.