GNOME Bugzilla – Bug 645094
Network: custom connections don't show up in the list
Last modified: 2013-01-30 19:53:48 UTC
Go to nm-connection-editor, create a custom wired or wireless connection.
Now bring up the network panel.
Expected result: custom connection should show up in the list. It doesn't
Similar: Go to nm-connection-editor and change the name of an existing vpn connecition while the network panel is open.
Expected result: the name change should be reflected in the device list. It isn't
Interestingly, _new_ vpn connections _are_ picked up.
I'll work on this after lunch.
I had to switch to working on a dbus errata, I've got some code here that I'll commit after talking a bit to dcbw.
After some more discussion, the current code for showing custom connections leads to some suboptimal results for people who are upgrading from NM 0.8 (ie everybody), since it causes two wired connections to show up by default (System eth0 and Auto ern0), at least on system that have the new device naming policy for network devices. Since it is too late to sort that out in detail, I'm proposing that we simply restrict the creation of custom connections to vpn for now, since newly created vpn connections do show up in the list.
Committed a minimal fix along those lines. Dropping off the blocker list
*** Bug 647569 has been marked as a duplicate of this bug. ***
Custom connections will probably need some rethinking of the device list
Current ideas include keeping the list just for devices, and having e.g. custom
wired connections show up as a combo box on the right hand side.
The custom connection combo would only be shown if there actually are custom
connection (expected to be rare). Creation/deletion of custom connections could
then be relegated to being the options button.
*** Bug 644960 has been marked as a duplicate of this bug. ***
not happening for 3.2
*** Bug 677910 has been marked as a duplicate of this bug. ***
For wired, this is being addressed in the wip/network branch
I'll consider this fixed for now