Package: bluez
Version: 5.49-4Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
   * What led up to the situation?     boot       * What exactly did you do (or not do) that was effective (or     ineffective)?
   * What was the outcome of this action?        Many of these messages in syslog:
        systemd-udevd[265]: Process 'hid2hci --method=dell --devpath=/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.0 \            failed with exit code 1.
   * What outcome did you expect instead?        hid2hci toggle from HID to HCI mode successful
*** End of the template - remove these template lines ***
This bug was also reported at https://dev.solus-project.com/T5224 with aworkaround that alleviates the problem (disable the Dell touchpad rules in'/lib/udev/rules.d/97-hid2hci.rules' and implement a system service tomanually toggle the mode.)
-- System Information:Debian Release: buster/sid  APT prefers testing  APT policy: (990, 'testing'), (500, 'unstable')Architecture: amd64 (x86_64)
Kernel: Linux 4.16.0-2-amd64 (SMP w/2 CPU cores)Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)Shell: /bin/sh linked to /bin/dashInit: systemd (via /run/systemd/system)LSM: AppArmor: enabled
Versions of packages bluez depends on:ii  dbus          1.12.8-3ii  kmod          25-1ii  libasound2    1.1.6-1ii  libc6         2.27-3ii  libdbus-1-3   1.12.8-3ii  libdw1        0.170-0.4ii  libglib2.0-0  2.56.1-2ii  libreadline7  7.0-5ii  libudev1      238-5ii  lsb-base      9.20170808ii  udev          238-5
bluez recommends no packages.
Versions of packages bluez suggests:ii  pulseaudio-module-bluetooth  11.1-5
-- no debconf information

Over 100,000 messages from upowerd, the same two repeated over and over until upowerservice is stopped:
upowerd[1281]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.0
upowerd[1281]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.0

Run /lib/systemd/systemd-udevd -D -should print garbage in endless loop
containing ".../97-hid2hci.rules:"

If so, edit /lib/udev/rules.d/97-hid2hci.rules and add ACTION=="add", in
front of line mentioned by above command.

It should be something like this (I'm using fedora 28, but the problem
looked identical): ACTION=="add", ATTR{bInterfaceClass}=="03",
ATTR{bInterfaceSubClass}=="01", ATTR{bInterfaceProtocol}=="02", \
ATTRS{bDeviceClass}=="00", ATTRS{idVendor}=="413c",
ATTRS{bmAttributes}=="e0", \ RUN+="hid2hci --method=dell --devpath=%p",
ENV{HID2HCI_SWITCH}="1"


Source:- https://askubuntu.com/a/1059845

Hi bluez maintainers,

A person got in touch with debian-user-french people asking for help because she was facing the issue described in this bug report.

I wonder if there is any progress on finding a solution ?

For info, this problem is also mentionned in the bug report #889110 ([1])
(closed by Michael Biebl <biebl@debian.org> on 9 Feb 2018).

And in the RedHat Bug 1563554 ([2]) suggesting a workaround by just adding <ACTION=="add",> in front of the line containing <ATTR{bInterfaceClass}=="03", ATTR{bInterfaceSubClass}> in the file /lib/udev/rules.d/97-hid2hci.rules.

Can you, please, advice what is the best solution to, at least, mitigate the risk of being hit by this bug ?  Specifying the ACTION like described in the RH bugreport or using the driver usbhid like in the Тут Root's proposed patch.

And about further investigations, unfortunately, I cannot reproduce the bug and, then, I am not able to investigate further to know if it is really a driver or kernel bug.

Regards,

Jean-Marc <jean-marc@6jf.be>
https://6jf.be/keys/ED863AD1.txt

[1] https://bugs.debian.org/889110
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1563554