SUMMARY When the bluetooth service is not started, the Bluetooth page in System Settings shows "No devices paired" instead of something like "Bluetooth service is not start". Such UX mislead the users to find the button of pairing devices without letting them realize that such attempt is doomed to fail because of something unmentioned in the UI, and the correct solution is `sudo systemctl start bluetooth`. This is a bug report instead of a feature request. STEPS TO REPRODUCE 1. Install EndeavourOS with KDE Plasma. 2. Open Bluetooth in System Settings. OBSERVED RESULT "No devices paired". EXPECTED RESULT "Bluetooth service not started". SOFTWARE/OS VERSIONS EndeavourOS with KDE Plasma KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 ADDITIONAL INFORMATION
Fixed in plasma 6.0; Now it says "bluetooth is disabled" with an Enable button.
(In reply to fanzhuyifan from comment #1) > Fixed in plasma 6.0; Now it says "bluetooth is disabled" with an Enable > button. Disabling/enabling the bluetooth systemd unit is not the same thing as disabling/enabling bluetooth via the UI (which relies on rfkill)
(In reply to Nicolas Fella from comment #2) > (In reply to fanzhuyifan from comment #1) > > Fixed in plasma 6.0; Now it says "bluetooth is disabled" with an Enable > > button. > > Disabling/enabling the bluetooth systemd unit is not the same thing as > disabling/enabling bluetooth via the UI (which relies on rfkill) Ahh sorry. Can reproduce.