Problem description ------------------- When I try to connect a Wii U Pro Controller to Fedora 40, I get the following message: """ Failed to pair: org.bluez.Error.AuthenticationRejected """ Works with Fedora 39 (fresh install). Expected behaviour ------------------ """ Device 18:2A:7B:45:F1:C4 Connected: yes """ The behaviour is the same with the GUI. This issue was not present in Fedora 39. I also tested on a new installation of Fedora and it works the same way. Reproducible: Always Steps to Reproduce: Step 1: Launch bluetoothctl (in Konsole) Step 2: Put the Wii U Pro Controller in “pairing mode” (by pressing the Sync button) Step 3: In bluetoothctl, type: "pair 18:2A:7B:45:F1:C4" Actual Results: Command output: """ Attempting to pair with 18:2A:7B:45:F1:C4 [CHG] Device 18:2A:7B:45:F1:C4 Connected: yes [CHG] Device 18:2A:7B:45:F1:C4 Connected: no [CHG] Device 18:2A:7B:45:F1:C4 Connected: yes [Nintendo RVL-CNT-01-UC]# Failed to pair: org.bluez.Error.AuthenticationRejected """ Expected Results: Expected behaviour ------------------ """ Device 18:2A:7B:45:F1:C4 Connected: yes """ Works with fedora 39 lsusb output: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 1bcf:2cb8 Sunplus Innovation Technology Inc. HP 8MP Camera Bus 003 Device 003: ID 0bda:5668 Realtek Semiconductor Corp. HP Full-HD Camera Bus 003 Device 004: ID 04f3:0c79 Elan Microelectronics Corp. Bus 003 Device 005: ID 06cb:00f0 Synaptics, Inc. Bus 003 Device 006: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Please supply the rpm NVR of the F-39 working and the F-40 non working versions of bluez
works: 5.69-1.fc39 doesn't work: 5.75-1.fc40 Between the two, there was a regression but I don't know exactly when because I don't update regularly.
If you edit /etc/bluetooth/input.conf and change the "#ClassicBondedOnly=true" line to "ClassicBondedOnly=false" does it start to work?
No change with modification of /etc/bluetooth/input.conf and after a systemctl restart bluetooth
I suspect the problem is around classic mode and security, there's more detail in rhbz 2254091.
With input.conf modified, it works when I just try to connect to device (and not pair).
It's a little bit tricky to connect to controller. It works only with command line and I must do like this : 1. Push Sync button of controller, 2. In bluetoothctl: "scan on", "connect 18:2A:7B:45:F1:C4". But if I shut down controller and try to connect again, it doesn't work. To make it work again, I must restart bluetooth and redo steps. With Fedora 39, after pairing the controller, when I wanted to use it, I just had to turn it on with the power button. That was very simple.
> With Fedora 39, after pairing the controller, when I wanted to use it, I > just had to turn it on with the power button. That was very simple. Well if you could go through the various releases in F-39 from 5.69-1.fc39 to the 5.75 release that would be useful as it seems there may be more than one problem here. The BT Classic issue mentioned in comment #3 was changed upstream due to a CVE security issue so we're not going to revert that, but there were some other issues around input that have been mostly fixed with 5.75-1
With: dnf list bluez --showduplicates, I tried to see the different versions of bluez and it seems to me that there are only 2: 5.69-1.fc39 and 5.75-1.fc39. Anyway, on my fedora 39, when I downgrade bluez, the connection to the controller works without problem and no reconnection problem. I don't know if there are intermediate versions of bluez between 5.69 and 5.75. Anyway, I haven't yet found a way to access these versions with dnf.
I found a way to test the different versions. The first one to malfunction is 5.73-2. It brings both pairing problems and reconnection problems for the Wii U Pro controller. 5.72-1 is ok with both.
> I don't know if there are intermediate versions of bluez between 5.69 and > 5.75. Anyway, I haven't yet found a way to access these versions with dnf. You'll need to grab them from koji: https://koji.fedoraproject.org/koji/packageinfo?packageID=6777
Yes, this is what I did for the last post. ;-)
(In reply to Nicolas Sellenet from comment #12) > Yes, this is what I did for the last post. ;-) I figured, documenting it for others that may find this bug too ;-)
Do you think it would be possible for connecting to my controller to become again as simple as it was before security patch? Today, via the GUI, configuration is impossible. All that remains is bluetoothctl which is not very user-friendly.
FEDORA-2024-9f7bb41811 (bluez-5.76-1.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-9f7bb41811
FEDORA-2024-e34c8cbb70 (bluez-5.76-1.fc39) has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-e34c8cbb70
FEDORA-2024-9f7bb41811 has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-9f7bb41811` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-9f7bb41811 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-e34c8cbb70 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-e34c8cbb70` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-e34c8cbb70 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-9f7bb41811 (bluez-5.76-1.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-e34c8cbb70 (bluez-5.76-1.fc39) has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.