https://bugs.kde.org/show_bug.cgi?id=526178
David Edmundson <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/bluedevil/-/commit/e781c |ma/bluedevil/-/commit/51daa |89310dc7d22cca329171098f252 |da4109a1a8184a821b10325faa6 |337acee2 |63606591 --- Comment #4 from David Edmundson <[email protected]> --- Git commit 51daada4109a1a8184a821b10325faa663606591 by David Edmundson. Committed on 24/09/2026 at 17:54. Pushed by ngraham into branch 'Plasma/6.8'. wizard: always start our own discovery session The discover page only called startDiscovery() when the adapter was not already discovering. If another D-Bus client was discovering at the time, the wizard never became a discovery client itself, so the scan was whatever that client had asked for. KDE Connect's Bluetooth backend keeps a discovery session with a BR/EDR-only transport filter, and while it runs the wizard finds no Bluetooth LE devices at all: keyboards, mice and game controllers never appear. BlueZ tracks discovery per client and merges the filters of every discovering client; one unfiltered client makes it scan both LE and BR/EDR. So start discovery unconditionally. If this client is already discovering, BlueZ returns InProgress, which is harmless. (cherry picked from commit aa2c9639b4ae9889cc161403a20f5d45ee146daa) Co-authored-by: Robert August Vincent II (Bob) <[email protected]> M +6 -2 src/wizard/pages/discover.cpp https://invent.kde.org/plasma/bluedevil/-/commit/51daada4109a1a8184a821b10325faa663606591 -- You are receiving this mail because: You are watching all bug changes.
