Bluetoothd errors - how to fix them?

Support
1

I noticed in journal a few bluetoothd errors:

The first group is:

[713]: src/plugin.c:plugin_init() Failed to init vcp plugin
[713]: src/plugin.c:plugin_init() Failed to init mcp plugin
713]: src/plugin.c:plugin_init() Failed to init bap plugin

The second group is:

[713]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 2C:FD:B4:72:7E:F8: Host is down (112)
[713]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
[713]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Connection refused

As far I can tell, bluetooth works fine, so I’m not sure what the errors are impairing.

2

You should ignore these messages. If you don’t want to, you need to enable experimental features. This will make theses messages go away.

https://wiki.archlinux.org/title/Bluetooth#Enabling_experimental_features

1 Like
3

Thanks! That does make the first group of errors go away.

So remaining are:

bluetoothd[717]: profiles/audio/avctp.c:avctp_control_confirm() Control: Refusing unexpected connect
bluetoothd[717]: profiles/audio/avctp.c:avctp_connect_cb() connect to 2C:FD:B4:72:7E:F8: Connection refused (111)
bluetoothd[717]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
bluetoothd[717]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Connection refused
4

It’s trying to automagically connect to a device. The device is either powered off or not available for some other reason. You have a profile set up for it so it’s using it but fails. Not a big deal. If it’s for a device you no longer have or use simpli remove it from the list of devices.

1 Like
5

In that case, all problems are solved :smiley:

Thanks @xabbu and @eriefisher .

To repeat and sum up:
There were two groups of errors, and the first one was a simple notification that some experimental options are off. Turning experimental options on, made the notifications go away.
The second group is generated after the list of Bluetooth devices that are remembered and system is trying to connect with them automatically. Since those aren’t available all the time, they generate a connection error in journal.

All is clear. Thanks again!

1 Like
6

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.