After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 645094 - Network: custom connections don't show up in the list
Network: custom connections don't show up in the list
Product: gnome-control-center
Classification: Core
Component: Network
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
: 644960 647569 677910 (view as bug list)
Depends on:
Reported: 2011-03-18 02:31 UTC by Matthias Clasen
Modified: 2013-01-30 19:53 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Matthias Clasen 2011-03-18 02:31:28 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
Comment 1 Matthias Clasen 2011-03-18 02:33:38 UTC
Interestingly, _new_ vpn connections _are_ picked up.
Comment 2 Richard Hughes 2011-03-18 12:59:32 UTC
I'll work on this after lunch.
Comment 3 Richard Hughes 2011-03-18 18:36:36 UTC
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.
Comment 4 Matthias Clasen 2011-03-23 22:23:38 UTC
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.
Comment 5 Matthias Clasen 2011-03-26 19:11:58 UTC
Committed a minimal fix along those lines. Dropping off the blocker list
Comment 6 Matthias Clasen 2011-04-13 04:35:05 UTC
*** Bug 647569 has been marked as a duplicate of this bug. ***
Comment 7 Matthias Clasen 2011-05-24 12:28:21 UTC
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.
Comment 8 Matthias Clasen 2011-05-24 12:30:57 UTC
*** Bug 644960 has been marked as a duplicate of this bug. ***
Comment 9 Matthias Clasen 2011-09-23 13:03:18 UTC
not happening for 3.2
Comment 10 Matthias Clasen 2012-06-14 02:30:46 UTC
*** Bug 677910 has been marked as a duplicate of this bug. ***
Comment 11 Matthias Clasen 2012-12-22 16:45:42 UTC
For wired, this is being addressed in the wip/network branch
Comment 12 Matthias Clasen 2013-01-30 19:53:48 UTC
I'll consider this fixed for now