From f013e99e160f385a0c02793c612ef4c8a8ffc4d7 Mon Sep 17 00:00:00 2001 From: Peter Hutterer Date: Tue, 7 Mar 2017 16:55:58 +1000 Subject: [PATCH] rules: set ID_BUS=bluetooth for any device with id/bustype attr of 0x0005 (#5539) Not all bluetooth devices come through the bluetooth subsystem and those that don't currently lack the ID_BUS=bluetooth env. This again fails to apply udev rules and/or hwdb entries that rely on the bluetooth bustype to be set. Fix this by checking the attribute id/bustype on the device instead of just the subsystem. Fixes #4566 --- rules/60-persistent-input.rules | 2 ++ 1 file changed, 2 insertions(+) diff --git a/rules/60-persistent-input.rules b/rules/60-persistent-input.rules index 607144bf8a..91efbe7294 100644 --- a/rules/60-persistent-input.rules +++ b/rules/60-persistent-input.rules @@ -3,6 +3,8 @@ ACTION=="remove", GOTO="persistent_input_end" SUBSYSTEM!="input", GOTO="persistent_input_end" SUBSYSTEMS=="bluetooth", ENV{ID_BUS}="bluetooth", GOTO="persistent_input_end" +# Bluetooth devices don't always have the bluetooth subsystem +ATTRS{id/bustype}=="0005", ENV{ID_BUS}="bluetooth", GOTO="persistent_input_end" SUBSYSTEMS=="rmi4", ENV{ID_BUS}="rmi", GOTO="persistent_input_end" SUBSYSTEMS=="serio", ENV{ID_BUS}="i8042", GOTO="persistent_input_end"