I've just installed Fedora updates for ~ a week or two, and my CX 350BT no longer connects. Auto-connect does not work (and crashes blueman - see https://bugzilla.redhat.com/show_bug.cgi?id=2274766). Manual connect hangs forever. Bluetoothd logs contain: Apr 12 20:18:23 dtantsur-laptop bluetoothd[9839]: src/device.c:set_wake_allowed_complete() Set device flags return status: Invalid Parameters Apr 12 20:19:03 dtantsur-laptop bluetoothd[9839]: Authorization request for non-connected device!? Apr 12 20:19:04 dtantsur-laptop bluetoothd[9839]: Authorization request for non-connected device!? Apr 12 20:19:05 dtantsur-laptop bluetoothd[9839]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 00:1B:66:C3:37:D7: Device or resource busy Apr 12 20:19:06 dtantsur-laptop bluetoothd[9839]: Authorization request for non-connected device!? Reproducible: Always Steps to Reproduce: 1. Turn on the headset 2. Nothing happens 3. Try to connect it from blueman Actual Results: Blueman shows infinite spinner "Connecting" Expected Results: The headset connects automatically as it used to before the very recent updates kernel 6.8.4-200.fc39.x86_64 bluez-5.73-3.fc39.x86_64 blueman-2.3.5-8.fc39.x86_64
A curious update: the audio stack actually sees the device and can use it. So maybe it's blueman again that does not recognize that the device is connected? I'd still like to hear an opinion on the logging in bluetoothd, but lowering the severity for now.
*** This bug has been marked as a duplicate of bug 2274047 ***