Created attachment 126116 [details] Duplicate network Everything from git master. I see a duplicate entry for my currently connected wifi network. See attached screenshot. here's the log info shown when I open the applet: plasma-nm: Requesting wifi scan on device "wlp1s0" plasma-nm: New connection "Network Node" added plasma-nm: New connection "sunport" added plasma-nm: New connection "NETGEAR73" added plasma-nm: New connection "RRX Hotspot" added plasma-nm: New connection "Free Wi-Fi Vodafone+DUSAirport" added plasma-nm: New connection "Schloss-Gehrden" added plasma-nm: New connection "Network Node" added plasma-nm: New connection "ATL Free Wi-Fi" added plasma-nm: New wireless network "Network Node" added plasma-nm: Item "Network Node" : device changed to "/org/freedesktop/NetworkManager/Devices/2" plasma-nm: Access point "Network Node" : merged to "Network Node" connection plasma-nm: Item "Network Node" : device changed to "/org/freedesktop/NetworkManager/Devices/2" plasma-nm: Item "Network Node" : active connection state changed to 2 plasma-nm: Wireless scan on "wlp1s0" succeeded plasma-nm: New wireless network "CenturyLink4759_5G" added plasma-nm: New wireless network "CenturyLink9149" added plasma-nm: New wireless network "CenturyLink2600" added plasma-nm: New wireless network "GreyWolf" added plasma-nm: New wireless network "CenturyLink7734" added plasma-nm: New wireless network "CenturyLink4738" added plasma-nm: Last scan finished 7541 ms ago and last request scan was sent 10300 ms ago, Skipping scanning interface: "wlp1s0" plasma-nm: Rescheduling a request scan for "wlp1s0" in 2459 plasma-nm: Requesting wifi scan on device "wlp1s0" plasma-nm: Wireless scan on "wlp1s0" succeeded
From the log it looks the "Network Node" connection is there twice. Can you open the KCM and verify there is just one?
I do indeed see two entries in the KCM. Looks like I can delete the duplicate. But I guess the question remains: how did it get created?
I have no idea, maybe you logged in with a different user? Can we close this bug now?
All right.