[PATCH BlueZ 2/2] adapter: Fix Discovering staying true after a failed stop

[Kevin Dewald <kevin@simpleble.org>]

When Stop Discovery for the last client fails, for example because the
controller times out the scan disable, stop_discovery_complete()
removes the client but keeps Discovering true until the kernel reports
the discovery state. When the kernel then reports the discovery as
stopped, discovering_callback() only triggers passive scanning, as no
client is left, so Discovering stays true and the next StartDiscovery
with the same filter returns without starting a discovery.

Clear Discovering when the kernel reports the discovery as stopped and
no client is left.

Fixes: c1226f79ec97 ("adapter: Fix not checking status of stop discovery command")
Assisted-by: Claude:claude-opus-5.5
---
 src/adapter.c | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/src/adapter.c b/src/adapter.c
index 4d753028a..c8889bee1 100644
--- a/src/adapter.c
+++ b/src/adapter.c
@@ -2146,6 +2146,17 @@ static void discovering_callback(uint16_t index, uint16_t length,
 	 * passive scanning attempt.
 	 */
 	if (!adapter->discovery_list) {
+		/*
+		 * Discovering is left set when stopping the discovery of the
+		 * last client failed, so clear it once the kernel reports the
+		 * discovery as stopped.
+		 */
+		if (!adapter->discovery_enable && adapter->discovering) {
+			adapter->discovering = false;
+			g_dbus_emit_property_changed(dbus_conn, adapter->path,
+						ADAPTER_INTERFACE, "Discovering");
+		}
+
 		if (!adapter->connect_le)
 			trigger_passive_scanning(adapter);
 		return;
-- 
2.54.0 (Apple Git-157)