Bug 514116

Summary: "Pair device" is not available when Bluetooth is enabled, and Bluetooth does not stay enabled in settings.
Product: [Applications] systemsettings Reporter: Moj <mojfps>
Component: kcm_bluetoothAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: filip.kendes1, nowrep
Priority: NOR    
Version First Reported In: 6.5.4   
Target Milestone: ---   
Platform: EndeavourOS   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Screencast displaying Bluetooth settings interactions

Description Moj 2026-01-03 17:40:01 UTC
Created attachment 188192 [details]
Screencast displaying Bluetooth settings interactions

SUMMARY

The toggles for enabling Bluetooth in settings appear not to work. Enabling both toggles does not give any option to pair a new device, though the system does acknowledge that a Bluetooth adapter is available. After closing the system settings window, both toggles revert to the off position.  

STEPS TO REPRODUCE
1.  Plug in USB Bluetooth adapter (ASUS), observe Bluetooth adapter notification
2.  Open system settings and enable Bluetooth with both the side panel toggle and the toggle on the Bluetooth settings window
3. Observe that no option appears to pair a new device

OBSERVED RESULT

No option to pair a new Bluetooth device appears when Bluetooth is enabled

EXPECTED RESULT

An option to pair a new Bluetooth device appears when Bluetooth is enabled

SOFTWARE/OS VERSIONS

Linux: EndeavourOS Linux x86_64 build 2025.03.19 (Kernel 6.18.1-arch1-2)
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.21.0
Qt Version: 6.10.1

ADDITIONAL INFORMATION

Setting the Bluetooth entry in Status and Notifications to "Always Visible" also does not work. Bluetooth does not show up under Status and Notifications.
Comment 1 Moj 2026-01-03 18:05:51 UTC
I enabled Bluetooth via Konsole and the option did appear, so I'm not sure if the toggle is not enabling Bluetooth or what the issue actually is, but this workaround works for now.
Comment 2 Filip 2026-01-04 09:57:44 UTC

*** This bug has been marked as a duplicate of bug 513893 ***
Comment 3 Filip 2026-01-04 10:02:17 UTC

*** This bug has been marked as a duplicate of bug 496376 ***