Version: unspecified (using KDE 4.7.2) OS: Linux If I suspend my system to disk or ram via pm-utils I have to remove the kernel module (this happens automatically via a SUSPEND_MODULES entry in /etc/pm/config.d/defaults) for my wlan dongle (it’s the Broadcom “wl” driver) because otherwise it freezes. When I resume my system the network monitor widget no longer displays the wlan0 interface but only shows eth0 which I don’t use. Reproducible: Always Steps to Reproduce: 1. Install an external wlan dongle. 2. Add a network monitor widget and select the wlan interface as monitored interface. 3. Suspend your system. 4. Restart the system. Actual Results: The previously displayed wlan interface is no longer selectable in the network monitor widget’s config dialog and it’s usage is not displayed by the widget. Expected Results: When the module is re-loaded on startup the newly created network interface is recognized by the network monitor widget.
Forgot one thing: May be related to https://bugs.kde.org/show_bug.cgi?id=221481
I can still reproduce this with 4.8.0
I can still reproduce this with 4.8.3
Reproduces on Kubuntu 12.04, KDE 4.8.5 ... and its dead on annoying.
I can't reproduce this here with Kubuntu Quantal beta2, KDE 4.9.1
Created attachment 74267 [details] screenshot widget vs. knemo
does NOT work here with gentoo / kde 4.9.1 the problems seems to be the SUSPEND_MODULES entry for the wlan module during hibernate. Without this it seems to work, but in this configuration in 99 out of 100 suspends my network card isn't working ;-(( see screenshot: no plot (the flat line is from before the suspend) and no interfaces in the network monitor widget configuration. knemo shows the interface and the amount of data transfered.
Reopening based on comment #7
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