https://bugs.kde.org/show_bug.cgi?id=508516
Arjen Hiemstra <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED Latest Commit| |https://invent.kde.org/plas | |ma/ksystemstats/-/commit/a6 | |10a8215cc98c06e702ee90a0bd4 | |9a7c2986ad2 --- Comment #3 from Arjen Hiemstra <[email protected]> --- Git commit a610a8215cc98c06e702ee90a0bd49a7c2986ad2 by Arjen Hiemstra, on behalf of Kartikeya Tyagi. Committed on 12/05/2026 at 13:24. Pushed by ahiemstra into branch 'master'. Fix stuck throughput values when device disconnects When a network device disconnects, the backend previously emitted the `disconnected` signal immediately. This caused the device object to be removed from ksystemstats before the frontend (Plasma System Monitor) or the aggregate sensor could register a zero value. As a result, the "All Network Devices" graph would often flatline at the last measured speed instead of dropping to zero. This patch fixes the issue by: 1. Explicitly setting all download and upload rate sensors (both bytes and bits) to 0 immediately upon disconnection. 2. Deferring the emission of the `disconnected` to the next global `update()` cycle using a pending disconnect flag. This ensures that the frontend has exactly one polling cycle to read the "0" values before the device object is destroyed M +27 -1 plugins/network/NetworkManagerBackend.cpp M +4 -0 plugins/network/NetworkManagerBackend.h https://invent.kde.org/plasma/ksystemstats/-/commit/a610a8215cc98c06e702ee90a0bd49a7c2986ad2 -- You are receiving this mail because: You are watching all bug changes.
