| What | Removed | Added |
|---|---|---|
| CC | wbauer@tmo.at |
(In reply to Matthias Klostermair from comment #6) > I just stumbled accross changelog for plasma 5.5.4 (here): > https://www.kde.org/announcements/plasma-5.5.3-5.5.4-changelog.php > > Could it be they have this fixed in that release?: > https://bugs.kde.org/show_bug.cgi?id=358028 > > Maybe this is related? I will try to test that 5.5.4 release when it arrives > in KF5 repos. Sounds indeed like this mentioned issue. I backported that fix to the Leap 42.1 package. Would be nice if somebody that is affected and running Leap could test it, it's available here: http://download.opensuse.org/repositories/home:/wolfi323:/branches:/OBS_Maintained:/plasma-nm5/openSUSE_Leap_42.1_Update (only plasma-nm5 itself needs to be updated) Tumbleweed users, please report back whether 5.5.4 fixes it for you. For now, you can get it from KDE:Frameworks5, again it should work to just install plasma-nm5 from there in case you don't want to fully switch to that repo. But it will appear in the TW main repo too at some time in the next weeks. Please note that this could only help with NetworkManager of course. Nobody here specified whether they used NetworkManager or Wicked. For the record, I cannot reproduce the problem here. Neither on 13.2 nor on Leap 42.1, neither with Wicked nor with NetworkManager.