Created attachment 127731 [details] this is where i get the bug, i'm not sure if it's a kde bug or a manjaro one SUMMARY STEPS TO REPRODUCE 1. click the network icon in the panel OBSERVED RESULT speed shows 0 for a second then a false number that's higher than the real one then after a second or 2 you get the real number EXPECTED RESULT you get the actual speed from the first time SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.6.5-1-MANJARO (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION
I can sometimes reproduce this on 5.20.3. I opened it to test and got shown a 1.3Gbit/s number which is impossible due to the network connection only being 1Gbit/s and there would have been very little traffic on my connection at the time I opened it.
Ah yes this bug! It was just fixed a little bit ago.
*** Bug 429438 has been marked as a duplicate of this bug. ***
Created attachment 136956 [details] Wrong upload/download speed
Network applet shows an incorrect value for the download/upload speed when first opened. Again. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20210320 / X11 KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 NetworkManager: 1.30.0
*** Bug 436635 has been marked as a duplicate of this bug. ***
Git commit d5df9379ef9825a65178d5d2335237cd0f84b90e by David Redondo. Committed on 17/05/2021 at 09:37. Pushed by davidre into branch 'master'. Prevent showing wrong speeds on initial open Previous attempt was the onCompleted block. However it turns out that at that point the model still has the old byte amounts. The order is showSpeedChanged -> setRefreshRate -> Timer.onCompleted/runningChanged -> model updates So set the amount to 0 in onCompleted and trigger the Timer on start (like a Timer with 0 interval). This initial trigger happens after the odel gets a new value and we have a correct amount on the first regular trigger of the Timer. FIXED-IN:5.22 M +3 -2 applet/contents/ui/ConnectionItem.qml https://invent.kde.org/plasma/plasma-nm/commit/d5df9379ef9825a65178d5d2335237cd0f84b90e
Git commit c36ab9a29f70986b5672a9f7b2913a18ef1f0aaa by David Redondo. Committed on 17/05/2021 at 09:47. Pushed by davidre into branch 'Plasma/5.22'. Prevent showing wrong speeds on initial open Previous attempt was the onCompleted block. However it turns out that at that point the model still has the old byte amounts. The order is showSpeedChanged -> setRefreshRate -> Timer.onCompleted/runningChanged -> model updates So set the amount to 0 in onCompleted and trigger the Timer on start (like a Timer with 0 interval). This initial trigger happens after the odel gets a new value and we have a correct amount on the first regular trigger of the Timer. FIXED-IN:5.22 (cherry picked from commit d5df9379ef9825a65178d5d2335237cd0f84b90e) M +3 -2 applet/contents/ui/ConnectionItem.qml https://invent.kde.org/plasma/plasma-nm/commit/c36ab9a29f70986b5672a9f7b2913a18ef1f0aaa
*** Bug 433632 has been marked as a duplicate of this bug. ***