Description of problem: When trying to connect the controller, it fails Version-Release number of selected component (if applicable): 5.64 How reproducible: Steps to Reproduce: 1. Pair XBOX Series Wireless controller 2. Connect to it Actual results: The controller is not connected Expected results: The controller is connected and can be used Additional info: `bluetoothctl` output: Attempting to connect to F4:6A:D7:6E:47:E3 [CHG] Device F4:6A:D7:6E:47:E3 Connected: yes Failed to connect: org.bluez.Error.Failed le-connection-abort-by-local `journalctl` output: fedora kernel: input: Xbox Wireless Controller as /devices/virtual/misc/uhid/0005:045E:0B13.001F/input/input49 fedora kernel: hid-generic 0005:045E:0B13.001F: input,hidraw2: BLUETOOTH HID v5.09 Gamepad [Xbox Wireless Controller] on e0:d4:64:38:dc:b2 fedora bluetoothd[1271]: profiles/deviceinfo/deviceinfo.c:read_pnpid_cb() Error reading PNP_ID value: Request attribute has encountered an unlikely error fedora bluetoothd[1271]: profiles/deviceinfo/dis.c:read_pnpid_cb() Error reading PNP_ID value: Request attribute has encountered an unlikely error fedora bluetoothd[1271]: profiles/input/hog-lib.c:info_read_cb() HID Information read failed: Request attribute has encountered an unlikely error fedora bluetoothd[1271]: profiles/input/hog-lib.c:report_reference_cb() Read Report Reference descriptor failed: Request attribute has encountered an unlikely error fedora bluetoothd[1271]: profiles/input/hog-lib.c:report_reference_cb() Read Report Reference descriptor failed: Request attribute has encountered an unlikely error sometimes: fedora kernel: Bluetooth: hci0: Opcode 0x2043 failed: -110 fedora kernel: Bluetooth: hci0: request failed to create LE connection: err -110
What bluetooth controller does your machine have? Please report the version of the kernel, linux-firmware. When did it last work?
I have a "Controller E0:D4:64:38:DC:B2 BlueZ 5.64" controller Kernel version 5.17.6-300.fc36.x86_64 linux-firmware version 20220411 I do not know when it last worked, since it has been hidden by another problem for longer, but I think remember it working around the 20th of December 2021
(In reply to aoellerer from comment #2) > I have a "Controller E0:D4:64:38:DC:B2 BlueZ 5.64" controller I need the HW make/model, it might be USB attached at which point you could include the appropriate line from the output of lsusb
Ah sorry, ID 045e:0b12 Microsoft Corp. Xbox Wireless Controller (model 1914)
(In reply to aoellerer from comment #4) > Ah sorry, ID 045e:0b12 Microsoft Corp. Xbox Wireless Controller (model 1914) So that's the bluetooth controller, or is it a wireless gaming input device (and if the later why is it showing up on USB?)?
Sorry, I thought you meant details on the gamepad, so I connected it via usb Here is the output of `bluetoothctl show`: Controller E0:D4:64:38:DC:B2 (public) Name: BlueZ 5.64 Alias: BlueZ 5.64 Class: 0x006c010c Powered: yes Discoverable: no DiscoverableTimeout: 0x000000b4 Pairable: yes UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb) UUID: Handsfree Audio Gateway (0000111f-0000-1000-8000-00805f9b34fb) UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb) UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb) UUID: Headset (00001108-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb) UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb) UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb) UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0540 Discovering: no Roles: central Roles: peripheral Advertising Features: ActiveInstances: 0x00 (0) SupportedInstances: 0x0c (12) SupportedIncludes: tx-power SupportedIncludes: appearance SupportedIncludes: local-name SupportedSecondaryChannels: 1M SupportedSecondaryChannels: 2M SupportedSecondaryChannels: Coded And here the (hopefully) appropriate lines from `lshw`: *-usb:1 description: Bluetooth wireless interface product: AX200 Bluetooth vendor: Intel Corp. physical id: 4 bus info: usb@1:4.4 version: 0.01 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s
FEDORA-2022-ec763229a2 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-ec763229a2
FEDORA-2022-1ef9e72355 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-1ef9e72355
FEDORA-2022-ec763229a2 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-ec763229a2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-ec763229a2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-1ef9e72355 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-1ef9e72355` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-1ef9e72355 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-ec763229a2 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-1ef9e72355 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.