https://bugs.kde.org/show_bug.cgi?id=522731
Bug ID: 522731
Summary: Bluetooth game controller battery tracking regression:
device visible in upower but battery percentage is
gone.
Classification: I don't know
Product: kde
Version First unspecified
Reported In:
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
After a recent system update on Fedora KDE, Bluetooth game controllers (such as
the DualShock 4) no longer report their battery percentages to the desktop
environment or independent Bluetooth utilities (like Bluejay).
The kernel driver (hid_playstation) appears to be communicating with upower
correctly, as the device path is explicitly registered and broadcast. However,
downstream applications fail to parse or display any battery metrics from this
path.
Diagnostic Output:
Running 'upower -e' successfully lists the following active device path:
/org/freedesktop/UPower/devices/battery_ps_controller_battery_40o1bo5fo4ao9fo96
Despite the path being broadcast by upower, it seems a regression in a recent
package update has broken how the daemon formats or exposes the battery metrics
for this specific class of device, causing a blind spot for client apps.
Reproducible: Always
Steps to Reproduce:
1. Connect a PlayStation DualShock controller via Bluetooth.
2. Check the KDE battery system tray widget or an alternate manager like
Bluejay (no battery metrics or device entries are found).
--
You are receiving this mail because:
You are watching all bug changes.
