Some bluetooth headsets do not support connecting more then one bluetooth
profile (e.g. in parallel A2DP and HSP, or HSP and HFP) and issuing
connect() syscall for second profile returns just ECONNREFUSED.
Prior this patch bluetooth daemon for such situation reported following
message to log:
Unable to get connect data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
Message is incorrect as connect() syscall failed, not getpeername(). This
patch fixes this problem and logs correct error message:
Headset Voice gateway failed connect to XX:XX:XX:XX:XX:XX: Connection refused (111)
Main problem was in ext_connect() function which called bt_io_get() for
retrieving remote address (BT_IO_OPT_DEST) and if it failed then original
error from connect() syscall was masked. Because it is not possible to
retrieve BT_IO_OPT_DEST for unconnected socket, original destination
address for error message is propagated via connect_add() function in btio.
---
Having correct error message in logs is important. Due to this mangled
error message I was not able to easily debug why particular bluetooth
headset sometimes connection with nonsense error that Transport endpoint
was not connected.
---
src/profile.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/src/profile.c b/src/profile.c
index c2992e795..6961a107b 100644
--- a/src/profile.c
+++ b/src/profile.c
@@ -1085,12 +1085,13 @@ static void ext_connect(GIOChannel *io, GError *err, gpointer user_data)
if (!bt_io_get(io, &io_err,
BT_IO_OPT_DEST, addr,
BT_IO_OPT_INVALID)) {
- error("Unable to get connect data for %s: %s", ext->name,
- io_err->message);
if (err) {
+ error("%s failed %s", ext->name, err->message);
g_error_free(io_err);
io_err = NULL;
} else {
+ error("Unable to get connect data for %s: %s",
+ ext->name, io_err->message);
err = io_err;
}
goto drop;
--
2.20.1
