https://bugs.kde.org/show_bug.cgi?id=425992
--- Comment #74 from David Redondo <k...@david-redondo.de> --- (In reply to Franco Pellegrini from comment #73) > I use the default KDE Neon installation, and the problem appear in all my > PCs. I see that you are on 5.20.5, which does not have the new backend. While the default KDE Neon should use NetworkManager that is a bit curious. If nmcli correctly shows verything I have no idea at the moment. (In reply to Nicola Mori from comment #72) > I don't use NetworkManager, I just have it installed. But in comment 14 > another Arch user reports he is using it and still he has the problem. Maybe > Arch builds ksysguard without networkmanager-qt (as per comment 10 I > understand this might be the source of teh problem, right?). When it is build without networkmanager-qt we should have now the new backend in Plasma 5.21 hopefully. I wonder maybe there is also a case where it is build with NetworManager but you don't use it for your connections. If you run "NLCB=debug ksystemstats --replace" and don't see a bunch of stuff then we are using the NetworkManager backend, if you see a lot of output, it's using the rtnetlink backend which should always work. -- You are receiving this mail because: You are watching all bug changes.
