Summary: | plasma systemmonitor network device sensors not selectable as long the device is not connected | ||
---|---|---|---|
Product: | [Applications] plasma-systemmonitor | Reporter: | Till Schäfer <till2.schaefer> |
Component: | general | Assignee: | KSysGuard Developers <ksysguard-bugs> |
Status: | REOPENED --- | ||
Severity: | normal | CC: | ahiemstra, jesper, kde, nate, plasma-bugs |
Priority: | NOR | ||
Version: | 5.23.2 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Till Schäfer
2021-03-05 08:48:51 UTC
I don't see why this is a problem in real life? There are infinite potential devices one could have that are disconnected and to try showing them opens up a can of worms. Both technical and for UX. I reported it, because I wanted to add some widgets to my desktop in order to display network usage for LAN and WLAN while I was traveling. For me it is important to separate these traffic statistics because I want to check if my laptop is actually using LAN or WLAN for transfer in some circumstances. I was not able to add the LAN widget until I was home in order to connect my laptop to a wired network. I think adding a LAN widget is quite common and also makes sense in a "no cable plugged in" state. Maybe I was a bit unclear what I mean with disconnected devices. I was not talking about potential hardware devices I may connect to my computer via usb or so. I am talking about devices actually present at my computer, but either not connected to a wire or not connected to a wifi. I guess there are not that many in desktop computers. Maybe the problem of understanding my problem here is the mixed naming of the devices, because the category says devides (which are LAN1 (enp0s1), LAN2 (eth0), WIFI(wlp...), etc for me), the content are also devices, but their are named by the connected network (which is something else in my understanding). I already opened another bug report for this issue: Bug 433951 *** Bug 459091 has been marked as a duplicate of this bug. *** |