When you set up bluetooth DUN tethering with n multiple mobile devices, all entries relative to bluetooth DUN devices appear n times... Say you have 2 mobile phones (smartphone A and featurephone B), both capable of bluetooth tethering. Say that you use the bluetooth applet to set them up for DUN. You set up the first one. In the kde network manager plasmoid you see various entries on the left hand panel. Among them you have: "Mobile broadband" with the bluetooth symbol. On the right hand side, you may many entries, but among them you see "smartphone A - plan so and so" with a small icon of a mobile on its side so far so good. Now you set up the second phone. Now on the left panel of the nm plasmoid you see. "Mobile broadband" with the bluetooth symbol, repeated TWICE On the right hand side you see "smartphone A - plan so and so" with a small icon of a mobile on its side repeated TWICE "featurephone B - plan blah blah blah" with a small icon of a mobile on its side also repeated TWICE for a total of 4 entries rather than 2. Just imagine what happens if you now add "superphone C", "ultraphone D" and "extraphone E"... Both nmcli and the gnome nm-applet get this right, so this is kde specific. Tested on 0.9.0.2. Reproducible: Always
*** Bug 303153 has been marked as a duplicate of this bug. ***
I can confirm, but this bug should be more general. I think #303153 shows it better, it was closed as duplicate of this one. The problem is that Network Management widget doesn't care if connection is locked down for specific interface via MAC address and displays it anyway - even if Network Manager won't allow to use such connections at all. The same bug happens when many ethernet interfaces are available. Because of that, Network Management proposes me to apply my ethernet connections to my phone, which is connected via USB, despite of having them properly configured in Network Manager to be applied only on eth0 - and another way too, phone connections shows up in ethernet configuration even if it's correctly configured to be used only with usb0. I think priority of this bug should be rather high, as it leaves user with not working UI elements without any feedback. Clicking on connections locked to another interface just does nothing. Those connections shouldn't be visible at all.
Looks like this one is also a duplicate. 298974
*** This bug has been marked as a duplicate of bug 298974 ***