ok, not fixed I still get it on a laptop, but it seems to make a difference whether knetworkmanager was started automatically in the seesion or run later
ok, not fixed I still get it on a laptop, but it seems to make a difference whether knetworkmanager was started automatically in the seesion or run later