FS#68408 - [bluez] bluetoothd has trouble parsing the default config

Attached to Project: Arch Linux
Opened by Ronan Pigott (Brocellous) - Sunday, 25 October 2020, 08:38 GMT
Last edited by Andreas Radke (AndyRTR) - Monday, 08 February 2021, 10:48 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Andreas Radke (AndyRTR)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No



Since bluez 5.55-1, bluetoothd complains a lot in the journal when reading the default config file that keys are missing. I think it's the result of this [1] patchset. I'm not sure if this means the default config file from upstream actually needs to be modified for distribution or what, since these errors come from parsing a config unchanged from upstream. I haven't noticed any adverse effects using my bluetooth devices.

[1] https://marc.info/?l=linux-bluetooth&m=159171144217659
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Monday, 08 February 2021, 10:48 GMT
Reason for closing:  Upstream
Additional comments about closing:  Upstream fix available.
Comment by Ronan Pigott (Brocellous) - Thursday, 26 November 2020, 04:20 GMT Comment by Andreas Radke (AndyRTR) - Monday, 08 February 2021, 10:48 GMT
diff --git a/src/main.conf b/src/main.conf
index d3bc61441..ad36638b7 100644
--- a/src/main.conf
+++ b/src/main.conf
@@ -86,7 +86,7 @@
# profile is connected. Defaults to true.
#RefreshDiscovery = true

# The following values are used to load default adapter parameters for BR/EDR.
# BlueZ loads the values into the kernel before the adapter is powered if the
# kernel supports the MGMT_LOAD_DEFAULT_PARAMETERS command. If a value isn't

That's affecting further config file changes to be included in the next release. Feel free to use bluez-git if needed until next release.