Bug 2116384

Summary:	ConfigurationDirectory mode differs
Product:	[Fedora] Fedora	Reporter:	Ben Cotton <bcotton>
Component:	bluez	Assignee:	Gopal krishna tiwari <gopalkrishna.tiwari>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	38	CC:	bnocera, dwmw2, gopalkrishna.tiwari, pbrobinson, spacewar
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-07-01 12:09:33 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2144504

Description Ben Cotton 2022-08-08 12:49:53 UTC

Description of problem:
I'm trying to diagnose why my laptop stopped seeing Bluetooth devices this morning. I don't think this is related, but it stood out as something to report. Even if the log message is spurious, it can confuse users.


Version-Release number of selected component (if applicable):
bluez-5.65-1.fc36.x86_64


How reproducible:
Always

Steps to Reproduce:
1. `systemctl restart bluetooth`

Actual results:
Aug 08 08:34:25 fedora systemd[1]: Starting bluetooth.service - Bluetooth service...
Aug 08 08:34:25 fedora systemd[4251]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMod>
Aug 08 08:34:25 fedora bluetoothd[4251]: Bluetooth daemon 5.65
Aug 08 08:34:25 fedora systemd[1]: Started bluetooth.service - Bluetooth service.


Expected results:
Aug 08 08:45:11 fedora systemd[1]: Starting bluetooth.service - Bluetooth service...
Aug 08 08:45:11 fedora bluetoothd[5463]: Bluetooth daemon 5.64
Aug 08 08:45:11 fedora systemd[1]: Started bluetooth.service - Bluetooth service.


Additional info:
Downgrading to bluez-5.64-1.fc36.x86_64 clears the error message.

Comment 1 Ben Cotton 2023-04-25 17:44:16 UTC

This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 2 Sandro Bonazzola 2023-05-16 08:17:59 UTC

Still reproducible on Fedora 38: bluez-5.66-5.fc38.x86_64

Seems related to bug #2144504

Comment 3 Peter Robinson 2023-07-01 12:09:33 UTC


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