This bug was fixed in the package network-manager - 0.9.10.0-4ubuntu15
---------------
network-manager (0.9.10.0-4ubuntu15) vivid; urgency=medium
* debian/patches/dont_mangle_bridges.patch: reinstate code to avoid mangling
bridges we didn't explicitly create, so that lxc, libvirt and others
don't get their bridges broken when NM restarts, etc. (LP: #1444205)
* d/p/0002-wifi-expose-the-last_seen-property-for-a-NMAccessPoi.patch:
compare apples to apples when trying to decide whether an AP is old enough
to be removed from the scan list (use boottime everywhere, rather than
trying to compare monotonic to boottime).
* d/p/0002-wifi-cull-the-scan-list-before-signalling-ScanDone-b.patch:
refreshed.
-- Mathieu Trudel-Lapierre <mathieu...@ubuntu.com> Wed, 15 Apr 2015 16:06:56
-0500
** Changed in: network-manager (Ubuntu)
Status: In Progress => 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/1444205
Title:
'service network-manager restart' causes NM to destroy IP config of
interfaces it's not managing (e.g., virbr0)
Status in network-manager package in Ubuntu:
Fix Released
Bug description:
On occasion I need to restart the network-manager service due to
configuration changes or because the service has gotten itself into an
inconsistent state. When NM restarts, this breaks network devices on
my system that are not managed by NM (e.g. my network-manager bridge,
virbr0), by removing their IP addresses.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: network-manager 0.9.10.0-4ubuntu13
ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
Uname: Linux 3.19.0-12-generic x86_64
ApportVersion: 2.17-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Apr 14 18:31:20 2015
InstallationDate: Installed on 2010-09-24 (1663 days ago)
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64
(20100816.1)
IpRoute:
default via 172.31.0.1 dev wlan2 proto static metric 1024
169.254.0.0/16 dev wlan2 scope link metric 1000
172.31.0.0/16 dev wlan2 proto kernel scope link src 172.31.43.142
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WWanEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to vivid on 2014-12-06 (129 days ago)
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code
2: Error: Object 'nm' is unknown, try 'nmcli help'.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1444205/+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
