https://bugs.kde.org/show_bug.cgi?id=513536
--- Comment #19 from deanrock <[email protected]> --- Hey, on my side (Fedora 43) this is only happening after: https://invent.kde.org/network/kdeconnect-kde/-/commit/2f62b712c7cb8415dde784621ab667a992af856f However, it seems to me that this just uncovers the underlying issue, because the problem only occurs when device discovery is started via `QBluetoothServiceDiscoveryAgent`. If I'm not mistaken, before this commit, `mServiceDiscoveryAgent->start()` never gets triggered, because `BluetoothLinkProvider::connectTimer` was never started, whereas afterwards `AsyncLinkProvider::connectTimer` is started right away. -- You are receiving this mail because: You are watching all bug changes.
