The page is empty, just showing this qrc:/kcm/kcm_bluetooth/main.qml:152 Type Kirigami.InlineMessage unavailable file:///usr/lib64/qt6/qml/org/kde/kirigami/InlineMessage.qml:63 Type KT.InlineMessage unavailable qrc:/qt/qml/org/kde/kirigami/templates/InlineMessage.qml:123 Cannot assign object of type "TP.IconPropertiesGroup" to property of type "IconPropertiesGroup_QMLTYPE_80*" as the former is neither the same as the latter nor a sub-class of it. user@PC:~$ systemctl status bluetooth ○ bluetooth.service - Bluetooth service Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled) Drop-In: /usr/lib/systemd/system/service.d └─10-timeout-abort.conf Active: inactive (dead) user@PC:~$ systemctl restart --now bluetooth user@PC:~$ systemctl status bluetooth ○ bluetooth.service - Bluetooth service Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled) Drop-In: /usr/lib/systemd/system/service.d └─10-timeout-abort.conf Active: inactive (dead) Docs: man:bluetoothd(8) user@PC:~$ sudo bluetoothctl enable Unable to open mgmt_socket Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.9.9-200.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics bluez-libs-5.77-1.fc40.x86_64 bluez-5.77-1.fc40.x86_64 bluez-obexd-5.77-1.fc40.x86_64 kf6-bluez-qt-6.4.0-2.fc40.x86_64 bluez-cups-5.77-1.fc40.x86_64 bluedevil-6.1.3-2.fc40.x86_64 NetworkManager-bluetooth-1.46.2-1.fc40.x86_64
Thanks for the bug report! This is a known issue, and a fix is in progress. Please follow the linked bug report for updates. This is not actually related to the bluetooth stack; it is triggered by opening the mouse or network settings. If you log out and log back in, you should be able to access the bluetooth settings without issues as long as you don't open one of the settings pages that causes the error. in other pages. *** This bug has been marked as a duplicate of bug 488326 ***