Bug 2280057

Summary:	example-gatt-server: "Failed to create entry in database"
Product:	[Fedora] Fedora	Reporter:	H.J. Lu <hjl.tools>
Component:	bluez	Assignee:	Gopal krishna tiwari <gopalkrishna.tiwari>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	40	CC:	dwmw2, gopalkrishna.tiwari, pbrobinson, spacewar
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	bluez-5.76-1.fc40 bluez-5.76-1.fc39	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-05-23 01:08:54 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 H.J. Lu 2024-05-10 23:11:25 UTC

When searching for Bluetooth device on Fedora 40, nothing found and

$ systemctl status bluetooth

reports

May 03 10:17:28 Ulmo bluetoothd[38839]: src/gatt-database.c:database_add_chrc() Failed to create characteristic entry in database
May 03 10:17:28 Ulmo bluetoothd[38839]: src/gatt-database.c:database_add_service() Failed to add characteristic
May 03 10:17:28 Ulmo bluetoothd[38839]: src/gatt-database.c:database_add_app() Failed to add service
May 03 10:17:28 Ulmo bluetoothd[38839]: src/gatt-database.c:client_ready_cb() Failed to create GATT service entry in local database



Reproducible: Always

Steps to Reproduce:
1. Open Bluetooth setting.
2. Search for Bluetooth device.

Comment 1 H.J. Lu 2024-05-10 23:12:16 UTC

This commit:

https://github.com/bluez/bluez/commit/f34cc1da5081e1a464212dc73cde8ba4f2b79d99

fixes the issue.

Comment 2 Fedora Update System 2024-05-20 12:33:23 UTC

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

Comment 3 Fedora Update System 2024-05-20 12:33:29 UTC

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

Comment 4 Fedora Update System 2024-05-21 02:21:42 UTC

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.

Comment 5 Fedora Update System 2024-05-21 03:04:53 UTC

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.

Comment 6 Fedora Update System 2024-05-23 01:08:54 UTC

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.

Comment 7 Fedora Update System 2024-06-05 08:34:11 UTC

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.