From 54f3b9a6fa47b618a31474d3786ed26248d3091d Mon Sep 17 00:00:00 2001 From: =?utf8?q?Fr=C3=A9d=C3=A9ric=20Dalleau?= Date: Tue, 4 Oct 2011 09:37:22 +0200 Subject: [PATCH] bluetooth: Do not unload module-bluetooth-device on ERR or HUP This happens in the following scenario : An HandsfreeGateway connects RFCOMM and then SCO. A card appears in PA and can be used. If for some reason, SCO is disconnected, module-bluetooth-device is unloaded. The card will disappear, even if RFCOMM is still connected. After that, it is not possible to connect SCO again from PA. --- src/modules/bluetooth/module-bluetooth-device.c | 1 - 1 file changed, 1 deletion(-) diff --git a/src/modules/bluetooth/module-bluetooth-device.c b/src/modules/bluetooth/module-bluetooth-device.c index ac76a196..81abcd6f 100644 --- a/src/modules/bluetooth/module-bluetooth-device.c +++ b/src/modules/bluetooth/module-bluetooth-device.c @@ -1721,7 +1721,6 @@ static void thread_func(void *userdata) { fail: /* If this was no regular exit from the loop we have to continue processing messages until we receive PA_MESSAGE_SHUTDOWN */ pa_log_debug("IO thread failed"); - pa_asyncmsgq_post(u->thread_mq.outq, PA_MSGOBJECT(u->core), PA_CORE_MESSAGE_UNLOAD_MODULE, u->module, 0, NULL, NULL); pa_asyncmsgq_wait_for(u->thread_mq.inq, PA_MESSAGE_SHUTDOWN); finish: -- 2.39.2