Bug 222042 - Network monitor plasmoid shows incorrect numbers after suspend/resume
Summary: Network monitor plasmoid shows incorrect numbers after suspend/resume
Status: RESOLVED UNMAINTAINED
Alias: None
Product: plasma4
Classification: Unmaintained
Component: widget-networkmonitor (other bugs)
Version First Reported In: 4.7.3
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-10 12:43 UTC by GGG
Modified: 2018-06-08 19:32 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description GGG 2010-01-10 12:43:05 UTC
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
Comment 1 Nicolas L. 2010-06-08 00:48:44 UTC
do you reproduce with kde 4.4.4 or 4.5beta ?
Comment 2 GGG 2010-06-08 08:11:49 UTC
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.
Comment 3 hoea 2010-06-23 10:12:28 UTC
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
Comment 4 Claude Sadois 2011-12-03 13:35:04 UTC
Is it still valid?
Comment 5 hoea 2011-12-04 20:29:44 UTC
hard to say - wlan isn't shown after resume: see bug #285346 (gentoo, plasma workspace 4.7.3)
Comment 6 Myriam Schweingruber 2012-05-16 11:40:49 UTC
Could you please test with KDE 4.8.3?
Comment 7 GGG 2012-05-16 12:16:35 UTC
(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.
Comment 8 Myriam Schweingruber 2012-06-03 18:54:28 UTC
Thank you for the feedback.
Comment 9 Nate Graham 2018-06-08 19:32:50 UTC
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