Version: (using KDE 4.3.4) OS: Linux Installed from: Ubuntu Packages After suspend/resume network monitor graphic sometimes (i.e. not after every suspend/resume cycle) shows incorrect negative value of about -1000 kb/s for incoming/outgoing traffic instead of correct positive values. Restarting the plasmoid (i.e. by entering its configuration dialog and pressing OK) will fix it: all data is reset and plots are drawed correctly. How to reproduce: Add network monitor plasmoid to desktop. Suspend, then resume. At some point, the plot is drawing -1000 kb/sec value. I am using Ubuntu 9.10 x86_64
do you reproduce with kde 4.4.4 or 4.5beta ?
I didn't try such recent versions of KDE as I am still in Ubuntu 9.10. Strange enough, this problem doesn't seem to reproduce anymore. Maybe some fixes were committed or it's just because of unstable nature of the bug.
I can reproduce with kde 4.4.4 on gentoo - maybe it is related to remove and reload of the kernel module(s) for the network card
Is it still valid?
hard to say - wlan isn't shown after resume: see bug #285346 (gentoo, plasma workspace 4.7.3)
Could you please test with KDE 4.8.3?
(In reply to comment #6) > Could you please test with KDE 4.8.3? At the moment the most recent Linux distro I have installed is Ubuntu 11.10 which has KDE 4.7.x. I won't be able to switch to KDE 4.8.3 until I upgrade to KDE 12.04 which I plan to do in a month.
Thank you for the feedback.
Hello! This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug is already resolved in Plasma 5. Accordingly, we hope you understand why we must close this bug report. If the issue described here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging Thanks for your understanding! Nate Graham