Bug 2274769

Summary:	Bluetooth headset stopped connecting after the recent updates
Product:	[Fedora] Fedora	Reporter:	Dmitry Tantsur <dtantsur>
Component:	bluez	Assignee:	Gopal krishna tiwari <gopalkrishna.tiwari>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	39	CC:	dwmw2, gopalkrishna.tiwari, pbrobinson, spacewar
Target Milestone:	---	Keywords:	Regression
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-04-15 10:14:38 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Dmitry Tantsur 2024-04-12 18:28:50 UTC

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

Comment 1 Dmitry Tantsur 2024-04-12 18:32:05 UTC

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.

Comment 2 Peter Robinson 2024-04-15 10:14:38 UTC


*** This bug has been marked as a duplicate of bug 2274047 ***