https://bugs.kde.org/show_bug.cgi?id=525589
Thibaut FRANCOIS <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #5 from Thibaut FRANCOIS <[email protected]> --- Also affected on CachyOS with a Logitech MX Keys and an MX Master 3, both via a Logitech receiver (hid-logitech-hidpp). Plasma 6.7.5, Frameworks 6.30.0, Qt 6.11.2, kernel 7.2.4-3-cachyos, Wayland, upower 1.91.4. Adding a UPower trace, since it may help narrow down where the -1 comes from: UPower itself never exposes a negative percentage. These devices report battery in HID++ "status" mode, so the kernel only provides three coarse levels (low/normal/full) and UPower synthesises a percentage flagged "should be ignored". During a power-cycle of the keyboard there is a window of roughly 3.4 s where the coarse level is `unknown`: [15:50:32.214] battery_hidpp_battery_1 (Logitech MX Keys) state: unknown battery-level: unknown percentage: 50% (should be ignored) icon-name: 'battery-missing-symbolic' [15:50:35.528] battery_hidpp_battery_1 state: discharging battery-level: unknown percentage: 50% (should be ignored) icon-name: 'battery-caution-symbolic' [15:50:35.590] battery_hidpp_battery_1 state: fully-charged battery-level: full percentage: 100% (should be ignored) icon-name: 'battery-full-charged-symbolic' So the -1 appears to be produced downstream, when the `unknown` coarse level is converted to a percentage, and that value is then compared against the low-battery threshold. The battery widget is unaffected and keeps showing 100% throughout. Separately, the notification title always reads "keyboard battery low" even when the device is the MX Master 3 mouse. That part is not a Plasma bug: `upower -d` already reports the mouse under the `keyboard` device type, so the wrong type is coming from upstream. -- You are receiving this mail because: You are watching all bug changes.
