Description of problem: For an unknown reason the binary /usr/lib/udev/hid2hci was dropped from bluez-hid2hci-5.55-3.5.mga8.x86_64.rpm even if still referenced in /usr/lib/udev/rules.d/97-hid2hci.rules The problem is that it prevent the forced hid2hci conversion required on dell laptop to switch from fake bluetooth touchpad and keypad to the real devices. Full explaination are avaible on : http://www.avalpa.com/assets/andrea/studio15/debian_on_dell_studio15.html Version-Release number of selected component (if applicable): bluez-hid2hci-5.55-3.5.mga8.x86_64 How reproducible: Always Steps to Reproduce: 1. enable wireless with kill switch touch 2. lsusb Bus 002 Device 037: ID 413c:8158 Dell Computer Corp. Integrated Touchpad / Trackstick Bus 002 Device 036: ID 413c:8157 Dell Computer Corp. Integrated Keyboard 3. dmesg 7030.052606] iwlwifi 0000:04:00.0: RF_KILL bit toggled to enable radio. [ 7030.052616] iwlwifi 0000:04:00.0: reporting RF_KILL (radio enabled) [ 7030.389202] usb 2-1.6: new full-speed USB device number 38 using ehci-pci [ 7030.469277] usb 2-1.6: New USB device found, idVendor=0a5c, idProduct=4500, bcdDevice= 1.00 [ 7030.469289] usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 7030.469292] usb 2-1.6: Product: BCM2046B1 [ 7030.469294] usb 2-1.6: Manufacturer: Broadcom [ 7030.469901] hub 2-1.6:1.0: USB hub found [ 7030.470054] hub 2-1.6:1.0: 3 ports detected [ 7030.741259] usb 2-1.6.1: new full-speed USB device number 39 using ehci-pci [ 7030.823363] usb 2-1.6.1: New USB device found, idVendor=413c, idProduct=8157, bcdDevice= 1.00 [ 7030.823372] usb 2-1.6.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 7030.825558] input: HID 413c:8157 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6.1/2-1.6.1:1.0/0003:413C:8157.0016/input/input47 [ 7030.877547] hid-generic 0003:413C:8157.0016: input,hidraw3: USB HID v1.11 Keyboard [HID 413c:8157] on usb-0000:00:1d.0-1.6.1/input0 [ 7030.946314] usb 2-1.6.2: new full-speed USB device number 40 using ehci-pci [ 7031.028846] usb 2-1.6.2: New USB device found, idVendor=413c, idProduct=8158, bcdDevice= 1.00 [ 7031.028854] usb 2-1.6.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 7031.032368] input: HID 413c:8158 Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6.2/2-1.6.2:1.0/0003:413C:8158.0017/input/input48 [ 7031.032526] hid-generic 0003:413C:8158.0017: input,hidraw4: USB HID v1.11 Mouse [HID 413c:8158] on usb-0000:00:1d.0-1.6.2/input0 Where with the binary you correctly all devices : 1. enable wireless with kill switch touch 2. lsusb Bus 002 Device 044: ID 413c:8156 Dell Computer Corp. Wireless 370 Bluetooth Mini-card Bus 002 Device 043: ID 413c:8158 Dell Computer Corp. Integrated Touchpad / Trackstick Bus 002 Device 042: ID 413c:8157 Dell Computer Corp. Integrated Keyboard 3. dmesg [ 7125.364713] iwlwifi 0000:04:00.0: RF_KILL bit toggled to enable radio. [ 7125.364723] iwlwifi 0000:04:00.0: reporting RF_KILL (radio enabled) [ 7125.621265] usb 2-1.6: new full-speed USB device number 41 using ehci-pci [ 7125.702053] usb 2-1.6: New USB device found, idVendor=0a5c, idProduct=4500, bcdDevice= 1.00 [ 7125.702062] usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 7125.702067] usb 2-1.6: Product: BCM2046B1 [ 7125.702070] usb 2-1.6: Manufacturer: Broadcom [ 7125.702409] hub 2-1.6:1.0: USB hub found [ 7125.702597] hub 2-1.6:1.0: 3 ports detected [ 7125.973255] usb 2-1.6.1: new full-speed USB device number 42 using ehci-pci [ 7126.054990] usb 2-1.6.1: New USB device found, idVendor=413c, idProduct=8157, bcdDevice= 1.00 [ 7126.055000] usb 2-1.6.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 7126.057744] input: HID 413c:8157 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6.1/2-1.6.1:1.0/0003:413C:8157.0018/input/input50 [ 7126.109519] hid-generic 0003:413C:8157.0018: input,hidraw3: USB HID v1.11 Keyboard [HID 413c:8157] on usb-0000:00:1d.0-1.6.1/input0 [ 7126.173195] usb 2-1.6.2: new full-speed USB device number 43 using ehci-pci [ 7126.255702] usb 2-1.6.2: New USB device found, idVendor=413c, idProduct=8158, bcdDevice= 1.00 [ 7126.255713] usb 2-1.6.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 7126.261522] input: HID 413c:8158 Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6.2/2-1.6.2:1.0/0003:413C:8158.0019/input/input51 [ 7126.262134] hid-generic 0003:413C:8158.0019: input,hidraw4: USB HID v1.11 Mouse [HID 413c:8158] on usb-0000:00:1d.0-1.6.2/input0 [ 7126.557213] usb 2-1.6.3: new full-speed USB device number 44 using ehci-pci [ 7126.640012] usb 2-1.6.3: New USB device found, idVendor=413c, idProduct=8156, bcdDevice= 4.56 [ 7126.640027] usb 2-1.6.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 7126.640030] usb 2-1.6.3: Product: Dell Wireless 370 Bluetooth Mini-card [ 7126.640031] usb 2-1.6.3: Manufacturer: Dell Computer Corp
Please apply this patch and if we may get an update for mga8 that would be wonderfull :) Index: SPECS/bluez.spec =================================================================== --- SPECS/bluez.spec (révision 1868012) +++ SPECS/bluez.spec (copie de travail) @@ -172,8 +172,8 @@ and mouse. %files hid2hci -#{_prefix}/lib/udev/hid2hci -#{_mandir}/man1/hid2hci.1* +%{_prefix}/lib/udev/hid2hci +%{_mandir}/man1/hid2hci.1* %{_udevrulesdir}/97-hid2hci.rules %post hid2hci @@ -227,6 +227,7 @@ --enable-sixaxis \ --enable-nfc \ --enable-mesh \ + --enable-hid2hci \ %{?with_deprecated:--enable-deprecated} \ --with-systemdsystemunitdir=%{_unitdir} \ --with-systemduserunitdir=%{_userunitdir}
In cauldron: [marja@DenkBlok4 ~]$ rpm -qa bluez-hid2hci bluez-hid2hci-5.64-1.mga9 [marja@DenkBlok4 ~]$ urpmq -l bluez-hid2hci /usr/lib/udev/rules.d/97-hid2hci.rules [marja@DenkBlok4 ~]$ Assigning to all packagers collectively, since there is no registered maintainer for bluez
Whiteboard: (none) => MGA8TOOCC: (none) => marja11Version: 8 => CauldronAssignee: bugsquad => pkg-bugs
The regression was intruduced by shlomif with update to bluez 5.55 (from MGA7 to MGA8) https://svnweb.mageia.org/packages/cauldron/bluez/current/SPECS/bluez.spec?r1=1605711&r2=1628735
Fixed in cauldron with bluez-5.64-2.mga9.
Whiteboard: MGA8TOO => (none)Version: Cauldron => 8
Please test bluez-5.55-3.6.mga8 from mga8 core/updates_testing.
Assignee: pkg-bugs => qa-bugs
SRPMS: bluez-5.55-3.6.mga8 RPMS: bluez-5.55-3.6.mga8 bluez-cups-5.55-3.6.mga8 bluez-mesh-5.55-3.6.mga8 bluez-hid2hci-5.55-3.6.mga8 lib(64)bluez3-5.55-3.6.mga8 lib(64)bluez-devel-5.55-3.6.mga8
Checking here - hid2hci is missing but strangely enough it is still listed in the bash completions list at /usr/share/bash-completion/completions/
CC: (none) => tarazed25
mga8, x64 Updated and ran into difficulties. Restarted bluetooth daemon but had to jump through many hoops to make my usual connection to a portable audio device. Desktop freezes happened a couple of times and even logout failed at one point forcing another reboot. No idea what was going on. This is normally a very simple operation. It is working now and detects my ancient Nokia mobile phone and an HP Officejet 100 portable printer. Not in a position to follow up the OP's problem. Works for me.
Confirming that hid2hci is present. $ ll /usr/lib/udev/hid2hci -rwxr-xr-x 1 root root 15616 Jul 9 19:54 /usr/lib/udev/hid2hci* It seems to work in general so giving this an OK for 64-bits.
Whiteboard: (none) => MGA8-64-OK
I'm concerned about Comment 8. Even if it did eventually work, you make it sound like the cure may be worse than the disease.
CC: (none) => andrewsfarm
Apparently my Acer Aspire isn't bluetooth-capable, so all I have is a clean install
CC: (none) => herman.viaene
@TJ in reply to comment 10. Yes, bluetooth can be flaky at times. Usually it works very smoothly but now and again it gives trouble. My feeling is that it is a procedural matter, like not doing things in the correct sequence but who knows. It always works in the end, with a curse or two. The only other thing I can think of is sensitivity; maybe something borderline.
Thanks, guys. Validating.
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugs
CC: (none) => davidwhodginsKeywords: (none) => advisory
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2022-0102.html
Status: NEW => RESOLVEDResolution: (none) => FIXED