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 733634 - Network control center panel does not show non-active bridge slave profiles (consequently, cannot activate bridges properly)
Network control center panel does not show non-active bridge slave profiles (...
Status: RESOLVED DUPLICATE of bug 747443
Product: gnome-control-center
Classification: Core
Component: Network
Other Linux
: Normal major
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Reported: 2014-07-23 21:48 UTC by Adam Williamson
Modified: 2015-04-07 12:26 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Adam Williamson 2014-07-23 21:48:41 UTC
This bug makes it impossible to fully configure a bridged connection through the GUI.

To reproduce, start with as simple a config as you can manage: I'm testing from a Fedora Rawhide live image with a single wired network connection.

Open the Network control center panel. Create a new connection of type 'Bridge'. Click 'Add' next to the empty 'Bridged connections' panel to create a new bridge slave profile. Set the type to Ethernet and click Create... . From the 'Device MAC address' dropdown in the 'Editing bridge0 slave 1' window you now see, select the wired connection. Click 'Save...' to save the slave profile. Click 'Save...' again to save the bridge profile.

The state of play now is that we have the original 'simple' wired network profile (probably - I'm assuming you don't delete it, GNOME won't let you do that, you can only do it with nm-c-e or nmcli or something), a profile for the new bridge, and a profile for the bridge slave. Using 'nmcli con show' you can see all three of these, and see that the bridge and the 'simple' profile are active.

At this point networking still works via the simple profile, but you don't want that, you want to start your bridge. Problem is, you can't. Go to Network and click Wired, and all you see is an On/Off switch and details about the connection (it's basically showing you the 'simple' profile). The 'bridge slave' profile is not shown here or anywhere else in Network.

You can only bring the bridge up from the console, using 'nmcli con up (UUID of bridge slave connection)'. Then the bridge will come up fine (after a few seconds), and now it's *active*, it is visible in Network/Wired, with a check mark next to it. Network is now showing both profiles - you see 'bridge0 slave 1' and 'Wired connection 1', with the slave profile checked to indicate it's active.

But if you ever switch back to the simple profile - via nmcli, or just by clicking on it in the Network applet - the bridge slave profile immediately disappears from the UI again. It seems like it's never visible if it's not active.

This is with control-center-3.13.3-3.fc21 .
Comment 1 Yann Soubeyrand 2015-01-03 15:55:52 UTC

I can confirm that the same problem is present in Debian Sid (GNOME Control Center 3.14.2 and NetworkManager
Comment 2 Ingvar Hagelund 2015-01-29 08:47:25 UTC
Confirmed on fedora 21. nmcli con up [uuid] (or reboot) makes the bridge active after configuring it.

Also, when actually getting a bridge working, it does not show up in the network manager applet either. It should show as a wired interface or some other icon, indicating the networking is active.
Comment 3 Adam Williamson 2015-01-29 17:19:25 UTC
Yeah, I think I have a report for that one too. Both bugs still valid on 3.15.4.
Comment 4 Bastien Nocera 2015-04-07 12:26:52 UTC
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 747443 ***