Bluetooth works on rc8 on this NUC6i5SYK. Hadn't been detecting devices on this NUC6 on a couple previous 5.17 rc (bluetooth still worked booting with 5.16, but not 5.17 until rc8). Passed default and performance regression tests.

Default & performance tests pass (KVM)

This update seems to fix the Bluetooth issues (especially scanning for devices) I've been experiencing on Fedora 36 pre-beta on my ThinkPad T14s with the

( https://bugzilla.redhat.com/show_bug.cgi?id=2066216 )

I still get an unexpected event in dmesg: [ 28.792914] Bluetooth: hci0: unexpected event 0xff length: 4 > 0

But Bluetooth seems functional again, including scanning.

@jforbes somehow this update doesn't get pushed or is a delay intended?

We are in beta freeze, nothing gets pushed without a freeze exception,

This update should probably be considered for a freeze exception, as Bluetooth will be broken in the F36 beta without this update.

I've been hit by this on my work and personal laptops — both from different vendors with different chips — and have seen several people who also did early upgrades to the F36 pre-beta complain about broken Bluetooth on Twitter and Mastodon. The issue seems very widespread.

While it's a beta, people still expect the basic functionality to work. Having broken Bluetooth means people can't use mice, keyboards, and headphones.

It looks like rc8 never got pushed to testing. Can it get pushed to testing like bluez did today? Would that allow people who install the beta to update and get it?

@wayne6001 This update got submitted for stable just before it could get pushed to testing because the required count of tests were submitted to push it to stable. Anyway, you can download this update from koji for testing. https://koji.fedoraproject.org/koji/buildinfo?buildID=1933659

My comment was in response to @garrett about what happens if the beta goes out with rc7 and the bluetooth scanning problem. I agee with @garrett above, that rc8 should be in the beta. But if they can't get an exception to include rc8 in the beta, I was asking if they could instead push rc8 to the testing repo now so that the impacted beta users have the problem fixed as soon as they update (since the beta has the testing repo enabled).