Bug 478801 - KDE System Settings bluetooth page won't show paired device info / buttons to add new devices
Summary: KDE System Settings bluetooth page won't show paired device info / buttons to...
Status: RESOLVED DOWNSTREAM
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_bluetooth (show other bugs)
Version: 5.27.10
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-12-20 22:11 UTC by jonathandudrey
Modified: 2023-12-21 21:06 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
blank bluetooth settings page (43.08 KB, image/png)
2023-12-20 22:11 UTC, jonathandudrey
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jonathandudrey 2023-12-20 22:11:24 UTC
Created attachment 164332 [details]
blank bluetooth settings page

SUMMARY
Not a crash, rather a report of broken bluetooth settings page following system update.

STEPS TO REPRODUCE
1. I, guess... roll the latest system update from KDE Discover? The buttons to add new bluetooth devices are just absent. Paired device info is absent. The bluetooth settings page is just... blank. And my bluetooth mouse can no longer connect with my computer.

OBSERVED RESULT
1. No buttons to add bluetooth devices or ANY device info on the bluetooth settings page (or any other buttons for that matter).

EXPECTED RESULT
1. Buttons and info for paired devices, working bluetooth mouse.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora Linux 39 (KDE Plamsa "Spin")
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.111.0
Qt Version: 5.15.11

ADDITIONAL INFORMATION
- Bluetooth was working fine before the latest system update.
Comment 1 Nate Graham 2023-12-21 21:06:25 UTC
If your mouse can't connect, it sounds to me like there's a problem with the whole Bluetooth stack on your machine, and the page in System Settings being blank is a symptom of that issue, not a cause. I'd recommend that you follow up with the Fedora folks about it, a it may be a kernel regression or other similar issue.

If they investigate and they still think it's a KDE issue, we can re-open this bug report.

Thanks!