SUMMARY The new bluetooth KCM does not indicate that Bluetooth is entirely unavailable on the hardware it's running on, instead merely being stuck on the "Bluetooth is disabled" screen where the button to enable it therefore does absolutely nothing. STEPS TO REPRODUCE 1. Put KDE neon Unstable in a Virtual Machine that does not support Bluetooth (such as VirtualBox) or any installation with Plasma 5.19.90/5.20 2. Open the Bluetooth KCM OBSERVED RESULT The "Bluetooth is disabled" screen shows EXPECTED RESULT A "Bluetooth is not available" screen should show SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon Unstable 5.19.90 (available in About System) KDE Plasma Version: 5.19.90 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION Maybe the Bluetooth KCM rewriter simply forgot to make this screen a thing?
Git commit 30df59afd80a3967abff8f013ebbe6aa4512b50b by Nicolas Fella. Committed on 20/09/2020 at 19:31. Pushed by ngraham into branch 'master'. Show appropriate message when no bluetooth adapter is available When bluetooth is blocked the manager doesn't show any adapters. Therefore the message is only shown when the rfkill state is unknown, which is the case when no bluetooth hardware is present. Depends on https://invent.kde.org/frameworks/bluez-qt/-/merge_requests/5 M +9 -1 src/kcm/package/contents/ui/Bluetooth.qml https://invent.kde.org/plasma/bluedevil/commit/30df59afd80a3967abff8f013ebbe6aa4512b50b