View previous topic :: View next topic |
Author |
Message |
nagmat84 Apprentice
Joined: 27 Mar 2007 Posts: 226
|
Posted: Sat Apr 06, 2024 3:49 pm Post subject: Warnings from Bluetooth service upon boot |
|
|
I see the following warnings (or above) in my system log for Bluetooth during boot Code: | Apr 06 17:08:15 matthias-pc (uetoothd)[705]: bluetooth.service: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
Apr 06 17:08:15 matthias-pc bluetoothd[705]: src/plugin.c:plugin_init() System does not support csip plugin
Apr 06 17:08:15 matthias-pc bluetoothd[705]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
Apr 06 17:08:15 matthias-pc bluetoothd[705]: src/plugin.c:plugin_init() System does not support micp plugin
Apr 06 17:08:15 matthias-pc bluetoothd[705]: src/plugin.c:plugin_init() System does not support vcp plugin
Apr 06 17:08:15 matthias-pc bluetoothd[705]: src/plugin.c:plugin_init() System does not support mcp plugin
Apr 06 17:08:15 matthias-pc bluetoothd[705]: src/plugin.c:plugin_init() System does not support bass plugin
Apr 06 17:08:15 matthias-pc bluetoothd[705]: src/plugin.c:plugin_init() System does not support bap plugin
Apr 06 17:08:15 matthias-pc bluetoothd[705]: src/adapter.c:reset_adv_monitors_complete() Failed to reset Adv Monitors: Failed (0x03)
Apr 06 17:08:15 matthias-pc bluetoothd[705]: Failed to clear UUIDs: Failed (0x03)
Apr 06 17:08:15 matthias-pc bluetoothd[705]: Failed to add UUID: Failed (0x03)
Apr 06 17:08:15 matthias-pc bluetoothd[705]: Failed to add UUID: Failed (0x03)
Apr 06 17:08:15 matthias-pc bluetoothd[705]: Failed to add UUID: Failed (0x03) | The messages about the unsupported plugins are warnings, the rest are errors.
How do I fix them?
This is the entire log Code: | Apr 06 17:08:15 matthias-pc systemd[1]: Starting Bluetooth service...
Apr 06 17:08:15 matthias-pc (uetoothd)[705]: bluetooth.service: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
Apr 06 17:08:15 matthias-pc bluetoothd[705]: Bluetooth daemon 5.72
Apr 06 17:08:15 matthias-pc bluetoothd[705]: Starting SDP server
Apr 06 17:08:15 matthias-pc bluetoothd[705]: src/plugin.c:plugin_init() System does not support csip plugin
Apr 06 17:08:15 matthias-pc bluetoothd[705]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
Apr 06 17:08:15 matthias-pc bluetoothd[705]: src/plugin.c:plugin_init() System does not support micp plugin
Apr 06 17:08:15 matthias-pc bluetoothd[705]: src/plugin.c:plugin_init() System does not support vcp plugin
Apr 06 17:08:15 matthias-pc bluetoothd[705]: src/plugin.c:plugin_init() System does not support mcp plugin
Apr 06 17:08:15 matthias-pc bluetoothd[705]: src/plugin.c:plugin_init() System does not support bass plugin
Apr 06 17:08:15 matthias-pc bluetoothd[705]: src/plugin.c:plugin_init() System does not support bap plugin
Apr 06 17:08:15 matthias-pc bluetoothd[705]: Bluetooth management interface 1.22 initialized
Apr 06 17:08:15 matthias-pc bluetoothd[705]: src/adapter.c:reset_adv_monitors_complete() Failed to reset Adv Monitors: Failed (0x03)
Apr 06 17:08:15 matthias-pc bluetoothd[705]: Battery Provider Manager created
Apr 06 17:08:15 matthias-pc systemd[1]: Started Bluetooth service.
Apr 06 17:08:15 matthias-pc bluetoothd[705]: Failed to clear UUIDs: Failed (0x03)
Apr 06 17:08:15 matthias-pc bluetoothd[705]: Failed to add UUID: Failed (0x03)
Apr 06 17:08:15 matthias-pc bluetoothd[705]: Failed to add UUID: Failed (0x03)
Apr 06 17:08:15 matthias-pc bluetoothd[705]: Failed to add UUID: Failed (0x03)
Apr 06 17:09:29 matthias-pc bluetoothd[705]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/A2DPSource/ldac
Apr 06 17:09:29 matthias-pc bluetoothd[705]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/A2DPSink/aptx_hd
Apr 06 17:09:29 matthias-pc bluetoothd[705]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/A2DPSource/aptx_hd
Apr 06 17:09:29 matthias-pc bluetoothd[705]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/A2DPSink/aptx
Apr 06 17:09:29 matthias-pc bluetoothd[705]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/A2DPSource/aptx
Apr 06 17:09:29 matthias-pc bluetoothd[705]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/A2DPSink/aac
Apr 06 17:09:29 matthias-pc bluetoothd[705]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/A2DPSource/aac
Apr 06 17:09:29 matthias-pc bluetoothd[705]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/A2DPSink/sbc
Apr 06 17:09:29 matthias-pc bluetoothd[705]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/A2DPSource/sbc
Apr 06 17:09:29 matthias-pc bluetoothd[705]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/A2DPSink/sbc_xq
Apr 06 17:09:29 matthias-pc bluetoothd[705]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/A2DPSource/sbc_xq
Apr 06 17:09:29 matthias-pc bluetoothd[705]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Apr 06 17:09:29 matthias-pc bluetoothd[705]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Apr 06 17:09:29 matthias-pc bluetoothd[705]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Apr 06 17:09:29 matthias-pc bluetoothd[705]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Apr 06 17:09:29 matthias-pc bluetoothd[705]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/A2DPSource/faststream
Apr 06 17:09:29 matthias-pc bluetoothd[705]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/A2DPSource/faststream_duplex
Apr 06 17:09:29 matthias-pc bluetoothd[705]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/A2DPSink/opus_05
Apr 06 17:09:29 matthias-pc bluetoothd[705]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/A2DPSource/opus_05
Apr 06 17:09:29 matthias-pc bluetoothd[705]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Apr 06 17:09:29 matthias-pc bluetoothd[705]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Apr 06 17:12:25 matthias-pc bluetoothd[705]: Terminating
Apr 06 17:12:25 matthias-pc systemd[1]: Stopping Bluetooth service...
Apr 06 17:12:25 matthias-pc bluetoothd[705]: Endpoint unregistered: sender=:1.49 path=/MediaEndpoint/A2DPSource/ldac
Apr 06 17:12:25 matthias-pc bluetoothd[705]: Endpoint unregistered: sender=:1.49 path=/MediaEndpoint/A2DPSink/aptx_hd
Apr 06 17:12:25 matthias-pc bluetoothd[705]: Endpoint unregistered: sender=:1.49 path=/MediaEndpoint/A2DPSource/aptx_hd
Apr 06 17:12:25 matthias-pc bluetoothd[705]: Endpoint unregistered: sender=:1.49 path=/MediaEndpoint/A2DPSink/aptx
Apr 06 17:12:25 matthias-pc bluetoothd[705]: Endpoint unregistered: sender=:1.49 path=/MediaEndpoint/A2DPSource/aptx
Apr 06 17:12:25 matthias-pc bluetoothd[705]: Endpoint unregistered: sender=:1.49 path=/MediaEndpoint/A2DPSink/aac
Apr 06 17:12:25 matthias-pc bluetoothd[705]: Endpoint unregistered: sender=:1.49 path=/MediaEndpoint/A2DPSource/aac
Apr 06 17:12:25 matthias-pc bluetoothd[705]: Endpoint unregistered: sender=:1.49 path=/MediaEndpoint/A2DPSink/sbc
Apr 06 17:12:25 matthias-pc bluetoothd[705]: Endpoint unregistered: sender=:1.49 path=/MediaEndpoint/A2DPSource/sbc
Apr 06 17:12:25 matthias-pc bluetoothd[705]: Endpoint unregistered: sender=:1.49 path=/MediaEndpoint/A2DPSink/sbc_xq
Apr 06 17:12:25 matthias-pc bluetoothd[705]: Endpoint unregistered: sender=:1.49 path=/MediaEndpoint/A2DPSource/sbc_xq
Apr 06 17:12:25 matthias-pc bluetoothd[705]: Endpoint unregistered: sender=:1.49 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Apr 06 17:12:25 matthias-pc bluetoothd[705]: Endpoint unregistered: sender=:1.49 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Apr 06 17:12:25 matthias-pc bluetoothd[705]: Endpoint unregistered: sender=:1.49 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Apr 06 17:12:25 matthias-pc bluetoothd[705]: Endpoint unregistered: sender=:1.49 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Apr 06 17:12:25 matthias-pc bluetoothd[705]: Endpoint unregistered: sender=:1.49 path=/MediaEndpoint/A2DPSource/faststream
Apr 06 17:12:25 matthias-pc bluetoothd[705]: Endpoint unregistered: sender=:1.49 path=/MediaEndpoint/A2DPSource/faststream_duplex
Apr 06 17:12:25 matthias-pc bluetoothd[705]: Endpoint unregistered: sender=:1.49 path=/MediaEndpoint/A2DPSink/opus_05
Apr 06 17:12:25 matthias-pc bluetoothd[705]: Endpoint unregistered: sender=:1.49 path=/MediaEndpoint/A2DPSource/opus_05
Apr 06 17:12:25 matthias-pc bluetoothd[705]: Endpoint unregistered: sender=:1.49 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Apr 06 17:12:25 matthias-pc bluetoothd[705]: Endpoint unregistered: sender=:1.49 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Apr 06 17:12:25 matthias-pc bluetoothd[705]: Battery Provider Manager destroyed
Apr 06 17:12:25 matthias-pc bluetoothd[705]: Stopping SDP server
Apr 06 17:12:25 matthias-pc bluetoothd[705]: Exit
Apr 06 17:12:25 matthias-pc systemd[1]: bluetooth.service: Deactivated successfully.
Apr 06 17:12:25 matthias-pc systemd[1]: Stopped Bluetooth service. |
|
|
Back to top |
|
|
netfab Veteran
Joined: 03 Mar 2005 Posts: 1906 Location: 127.0.0.1
|
|
Back to top |
|
|
nagmat84 Apprentice
Joined: 27 Mar 2007 Posts: 226
|
Posted: Mon Apr 08, 2024 6:30 am Post subject: |
|
|
I am not sure what you want to tell me with that link to the documentation and the hint that I might have to emable the experimental features.
How should that make the warnings go away? |
|
Back to top |
|
|
netfab Veteran
Joined: 03 Mar 2005 Posts: 1906 Location: 127.0.0.1
|
Posted: Mon Apr 08, 2024 8:26 am Post subject: |
|
|
Because these warnings comes from experimental profiles plugins that can be enabled only with D-Bus experimental option.
That is what the documentation link explains. You must enable experimental features or ignore them. |
|
Back to top |
|
|
nagmat84 Apprentice
Joined: 27 Mar 2007 Posts: 226
|
Posted: Tue Apr 09, 2024 5:38 pm Post subject: |
|
|
I will give it a try and see what will be changed.
Nonetheless, I still don't fully understand it. What does try to register experimental plugins with what? Is bluetoothd trying to register experimental features with something else, i.e. is bluetoothd in the role of the entity which tries registering? Or is something else trying to register experimental features with bluetoothd, i.e. is bluetoothd in the role of the registrar? I would like to keep my system at an overall stable state and I am wondering where do that experimental features (which cannot be registered and hence trigger the warning) come from in the first place? What causes that experimental attempt in the first place?
I would expect to see that kind of warning only if there was a mismatch between some packages using experimental features while some other packages do not support them. However, if everything is at a stable stage, then there shouldn't be such a message. |
|
Back to top |
|
|
|