This bug was fixed in the package network-manager - 0.9.8.8-0ubuntu28
---------------
network-manager (0.9.8.8-0ubuntu28) utopic; urgency=medium
* debian/patches/add_ofono_support.patch: Ignore calls to set_mm_enabled;
we don't need to do any action when that happens. (LP: #1350332)
* debian/patches/provisioning_wait_ofono_properties.patch: keep Online into
consideration when setting the CONNECTED state for the modem device, as
when flight mode is toggled the oFono Interfaces may be re-created and
could still be Powered and Attached. (LP: #1350332)
* debian/patches/ignore_rfkill_if_urfkill_present.patch: don't write state
file on state changes from urfkill, as urfkill will handle persistence
itself. (LP: #1381406)
* debian/patches/bridge_ignore_without_connections.patch: Drop patch; this
is no longer necessary given upstream commit 17338069 which avoids
touching bridge connections that weren't created by NM. (LP: #1273201)
-- Mathieu Trudel-Lapierre <mathieu...@ubuntu.com> Thu, 09 Oct 2014 14:38:18
-0400
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1273201
Title:
bridge_ignore_without_connections.patch breaks NM created bridge at
boot
Status in “network-manager” package in Ubuntu:
Fix Released
Bug description:
I've created a bridge with network-manager-gnome, the bridge slave
physical device is eth0. After a reboot the bridge is brought up, but
eth0 isn't attached.
First test-case:
Created a bridge with network-manager-gnome with the bridge slave physical
device is eth0 and remove all other connections. After a reboot the bridge is
brought up, but eth0 isn't attached. When I open
/etc/NetworkManager/NetworkManager.conf and save it without any modification,
eth0 is instantly added to my bridge. Strange!
Second test-case:
Created a bridge with network-manager-gnome with the bridge slave physical
device is eth0. Disable the "autoconnect" of the default wired network. After a
reboot the bridge is brought up, but eth0 isn't attached. Instead eth0 is
brought up and full configured.
After compiling and testing different upstream versions, i could track
the problem down to bridge_ignore_without_connections.patch. A
network-manager package without this specific patch, brings my bridge
up at boot and adds eth0 to the bridge in both test-cases.
I've checked the behaviour on my ubuntu 13.10 box with network-manager
(0.9.8.0-0ubuntu22) and the trusty version network-manager
(0.9.8.8-0ubuntu1) .
Till now i couldn't encounter any sideeffects of removing this patch
with the bridge created by libvirt.
Regards
Mathias Kresin
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1273201/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
