[Touch-packages] [Bug 1432599]

2023-11-16 Thread thaller 
When an interface is configured outside of NetworkManager's knowledge
(like libvirt's or docker's bridge), then NetworkManager generates an
in-memory connection profile and pretends(!) that this is active. This
is to show that something is going on with the device, and
NetworkManager is supposed to touch that device.

Whether this pretend mode is of any use is a good question. It's
obviously confusing. I actually do make use of this behaviour to have a
dispatcher script that does something for such external devices, so it's
not entirely useless. Also, it causes the output of `nmcli device` to
show that *something* is going on there. Although, maybe that's more
confusing than helpful. In any case, NetworkManager needs a way to
express that something is happening with this devices, and this is the
way it does that. It doesn't mean that NetworkManager actually touches
the device.


Comment 26 does not say what actual problem NetworkManager causes by this 
(aside the confusion to the user).

Comment 26 also explains that `nm-online` gives wrong results. I think 
nm-online has one real use-case: to implement 
`NetworkManager-wait-online.service` (with the `--startup` option).
Without the `--startup` option, I don't think it's of any use at all. It can 
only return "online" or "offline". It maps the NetworkManager's states "local", 
"site", and "global" to "online". I think that is is sensible, if you connect 
to a libvirt bridge some network is configured and nm-online considers that as 
"online". However I don't think that describing the online state in two words 
is meaningful and calling `nm-online` is not useful.


For a while NetworkManager had a udev rule to automatically unmanage docker 
bridges. But that was dropped, because docker bridges are nothing special. It's 
a common thing that something aside NetworkManager configures an interface and 
NetworkManager must not interfere. So, what actual problems are causes by this?


---


> 1) You should never need to create (actually *shouldn't* create) an ifcfg-* 
> file for a libvirt-created bridge. If proper operation requires this, then 
> there is definitely a bug.

Right. NM doesn't.

> 2) NetworkManager should never mess around with bridge devices created
by other entities (e.g. libvirt, but really anyone else), and no special
plugin should be required to make that happen. If we (libvirt) wanted NM
to manage the bridge, we would create it via NM.

Right. NM shouldn't. Does it?

-- 
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/1432599

Title:
  Network-manager tries to manage virbr0, which it should not

Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager package in Fedora:
  Won't Fix

Bug description:
  Since a recent upgrade in vivid, nm is trying to manage virbr0. This
  results in my main machine not getting a real IP address on eth0, and
  virtual machines not being able to use the network.

  This is probably related to
  https://bugzilla.redhat.com/show_bug.cgi?id=1166199

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 16 12:36:07 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-12-13 (92 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  IpRoute:
   default via 10.0.0.1 dev eth0  proto static  metric 1024
   10.0.0.0/24 dev eth0  proto kernel  scope link  src 10.0.0.75
   192.168.111.0/24 dev wlan0  proto kernel  scope link  src 192.168.111.8
   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
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  http_proxy: http://localhost:8118/
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.
  no_proxy: localhost,127.0.0.0/8,::1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432599/+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

[Touch-packages] [Bug 1432599]

2023-11-16 Thread david.ward 
In previous versions of GNOME (such as the version in RHEL 7.6), an
active NetworkManager connection profile for virbr0 caused a wired
Ethernet connection to appear in the top bar in GNOME Shell. It seems
this is actually now suppressed, and GNOME Control Center does not
expose the virbr0 device on the network panel (or allow it to be
configured there).


For users who are looking to check if a NetworkManager connection profile is 
active excluding libvirt's, disabling NetworkManager's control of the bridge 
devices still seems to me like an appropriate method to adjust the behavior of 
nm-online. I'm not sure I agree with the comment about *never* using ifcfg: the 
configuration I provided above is equivalent to setting 
"unmanaged-devices=interface-name:virbr0" in 
/etc/NetworkManager/NetworkManager.conf. It is read by NetworkManager's 
ifcfg-rh settings plugin, versus NetworkManager's keyfile settings plugin.

It's also worth mentioning that libvirt allows hook scripts to be run
when a virtual network switch is started/stopped, which can substitute
for NetworkManager dispatcher scripts for these devices:
https://libvirt.org/hooks.html

-- 
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/1432599

Title:
  Network-manager tries to manage virbr0, which it should not

Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager package in Fedora:
  Won't Fix

Bug description:
  Since a recent upgrade in vivid, nm is trying to manage virbr0. This
  results in my main machine not getting a real IP address on eth0, and
  virtual machines not being able to use the network.

  This is probably related to
  https://bugzilla.redhat.com/show_bug.cgi?id=1166199

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 16 12:36:07 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-12-13 (92 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  IpRoute:
   default via 10.0.0.1 dev eth0  proto static  metric 1024
   10.0.0.0/24 dev eth0  proto kernel  scope link  src 10.0.0.75
   192.168.111.0/24 dev wlan0  proto kernel  scope link  src 192.168.111.8
   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
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  http_proxy: http://localhost:8118/
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.
  no_proxy: localhost,127.0.0.0/8,::1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432599/+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

[Touch-packages] [Bug 1432599]

2023-11-16 Thread david.ward 
This has remained reproducible in every release from Fedora 23 through
Fedora 30 -- the problem never went away (and the underlying
reason/behavior never changed). Please re-open against Fedora 30.

This occurs in Fedora Workstation when it is installed to disk. The
behavior can be very easily seen by booting the Fedora Workstation live
image, without any wired or wireless network connections. (However the
missing 'libvirt-daemon-config-network' package needs to be installed
from local storage after boot, except on Fedora 23 and Fedora 26 where
this is already present.)


[liveuser@localhost ~]$ nmcli connection
NAMEUUID  TYPEDEVICE 
virbr0  f20e2384-0dca-4a6b-b4cb-3dd1582c1ce1  bridge  virbr0 
[liveuser@localhost ~]$ nm-online
Connecting...   30s [online]


This is (falsely) indicating that "the network is connected", as described in 
nm-online(1). Configuring NetworkManager to not manage virbr0 still works 
around this:

[liveuser@localhost ~]$ cat > ifcfg-virbr0 << EOF
> DEVICE=virbr0
> NM_CONTROLLED=no
> EOF
[liveuser@localhost ~]$ sudo cp ifcfg-virbr0 /etc/sysconfig/network-scripts/
[liveuser@localhost ~]$ rm ifcfg-virbr0 
[liveuser@localhost ~]$ sudo nmcli connection reload
[liveuser@localhost ~]$ nmcli connection

[liveuser@localhost ~]$ nm-online
Connecting...0s [offline]


But this should be an automatic setting, not a manual one. We already
know that the explicit configuration of this interface is handled by
libvirt (see /etc/libvirt/qemu/networks/default.xml), and NetworkManager
should not be managing it and potentially changing its state.

However this more generally applies to any virtual network switch
created with libvirt though, whether or not it is named virbr0.

Which package should contain the hooks to do this? Should NetworkManager
be able to identify a libvirt network switch, or should libvirt
configure NetworkManager (perhaps using a separate settings plugin) to
not manage its devices?

-- 
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/1432599

Title:
  Network-manager tries to manage virbr0, which it should not

Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager package in Fedora:
  Won't Fix

Bug description:
  Since a recent upgrade in vivid, nm is trying to manage virbr0. This
  results in my main machine not getting a real IP address on eth0, and
  virtual machines not being able to use the network.

  This is probably related to
  https://bugzilla.redhat.com/show_bug.cgi?id=1166199

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 16 12:36:07 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-12-13 (92 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  IpRoute:
   default via 10.0.0.1 dev eth0  proto static  metric 1024
   10.0.0.0/24 dev eth0  proto kernel  scope link  src 10.0.0.75
   192.168.111.0/24 dev wlan0  proto kernel  scope link  src 192.168.111.8
   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
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  http_proxy: http://localhost:8118/
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.
  no_proxy: localhost,127.0.0.0/8,::1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432599/+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

[Touch-packages] [Bug 1432599]

2023-11-16 Thread laine 
(NB: I'm a libvirt developer, so I'm writing this comment from that POV)

1) You should never need to create (actually *shouldn't* create) an
ifcfg-* file for a libvirt-created bridge. If proper operation requires
this, then there is definitely a bug.

2) NetworkManager should never mess around with bridge devices created
by other entities (e.g. libvirt, but really anyone else), and no special
plugin should be required to make that happen. If we (libvirt) wanted NM
to manage the bridge, we would create it via NM.

People normally don't see the issue you describe, because almost
everybody has a permanently online internet connection these days, but I
can see why it would be problematic.

Since this behavior has been present in NM for such a long time, I would
say that the proper place for the bug to be filed would be upstream
rather than in Fedora. I don't know if the NM developers pay more
attention to their mailing list, or to their issue tracker on
gitlab.freedesktop.org.

-- 
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/1432599

Title:
  Network-manager tries to manage virbr0, which it should not

Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager package in Fedora:
  Won't Fix

Bug description:
  Since a recent upgrade in vivid, nm is trying to manage virbr0. This
  results in my main machine not getting a real IP address on eth0, and
  virtual machines not being able to use the network.

  This is probably related to
  https://bugzilla.redhat.com/show_bug.cgi?id=1166199

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 16 12:36:07 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-12-13 (92 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  IpRoute:
   default via 10.0.0.1 dev eth0  proto static  metric 1024
   10.0.0.0/24 dev eth0  proto kernel  scope link  src 10.0.0.75
   192.168.111.0/24 dev wlan0  proto kernel  scope link  src 192.168.111.8
   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
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  http_proxy: http://localhost:8118/
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.
  no_proxy: localhost,127.0.0.0/8,::1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432599/+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

[Touch-packages] [Bug 1432599] Re: Network-manager tries to manage virbr0, which it should not

2017-10-27 Thread Bug Watch Updater 
Launchpad has imported 26 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1166199.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2014-11-20T14:55:32+00:00 Richard wrote:

Description of problem:

Since I upgraded to Fedora 21, NetworkManager is now offering
to manage virbr0.  In fact, if I disconnect from wireless,
then it falls back to "helpfully" connecting me to virbr0, which
is of course completely useless.

More seriously, I suspect that NM is actually breaking virbr0.
For some reason, virbr0-nic became disconnected from the virbr0
bridge, and that broke all libvirt networking, and I suspect
this happened about the time that NM decided to connect my
main network to virbr0.

I've no idea what we can do about this, or even which component
this belongs to.

On my machine I tried adding:
NM_CONTROLLED=no
to /etc/sysconfig/network-scripts/ifcfg-virbr0
although this has so far not made any difference (but
I haven't rebooted yet).

Version-Release number of selected component (if applicable):

libvirt-1.2.9-4.fc21.x86_64
NetworkManager-0.9.10.0-13.git20140704.fc21.x86_64

How reproducible:

100%

Steps to Reproduce:
1. Use Fedora 21 and libvirt and NM.

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1432599/comments/0


On 2015-01-09T21:55:24+00:00 Aleksandar wrote:

Any update on this? It's been close to 2 months. I just performed a
fedup to 21 and I hit the same issue. My em1 device remains disconnected
and virbr0 is shown connected but of course I can't get internet through
it. Good that at least wifi works though.

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1432599/comments/1


On 2015-01-09T22:11:14+00:00 Aleksandar wrote:

looks like re-occurrence of bug 1063545 and bug 1064441
I'm changing product and version to fedora21 as it looks like a network manager 
issue.

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1432599/comments/2


On 2015-01-09T22:40:56+00:00 Aleksandar wrote:

Created attachment 978433
log from systemctl restart NetworkManager

I've got rid of virbr0 device by putting into
/etc/NetworkManager/NetworkManager.conf the following content:

> [keyfile]
> unmanaged-devices=interface-name:virbr0

It also should support unmanaged-devices=mac:...

But I still can't get em1 to connect. Attaching what I get from
/var/log/messages on NetworkManager service restart.

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1432599/comments/3


On 2015-01-09T22:47:23+00:00 Aleksandar wrote:

Forgot to say that running dhcp manually brings up the interface just fine:
> $ sudo dhclient -d em1
> Internet Systems Consortium DHCP Client 4.3.1
> Copyright 2004-2014 Internet Systems Consortium.
> All rights reserved.
> For info, please visit https://www.isc.org/software/dhcp/
> 
> Listening on LPF/em1/3c:97:0e:19:30:f9
> Sending on   LPF/em1/3c:97:0e:19:30:f9
> Sending on   Socket/fallback
> DHCPREQUEST on em1 to 255.255.255.255 port 67 (xid=0x37c3b531)
> DHCPREQUEST on em1 to 255.255.255.255 port 67 (xid=0x37c3b531)
> DHCPACK from 192.168.1.1 (xid=0x37c3b531)
> bound to 192.168.1.145 -- renewal in 19334 seconds.

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1432599/comments/4


On 2015-01-09T23:03:58+00:00 Aleksandar wrote:

Very strange, after restarting the router, network manager started to
successfully start the em1 interface. Before restarting the router, only
manual dhclient request was working. Can that be related to leasing IP?
I couldn't find how to configure that in NetworkManager :(

> After connection though I see the following in the log:
> Jan 10 00:56:36 localhost NetworkManager[7383]:   Activation (em1) 
> successful, device activated.
> Jan 10 00:56:36 localhost dnsmasq[8458]: started, version 2.72 cachesize 400
> Jan 10 00:56:36 localhost dnsmasq[8458]: compile time options: IPv6 
> GNU-getopt DBus no-i18n IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth 
> DNSSEC loop-detect
> Jan 10 00:56:36 localhost dnsmasq[8458]: using nameserver 192.168.1.1#53
> Jan 10 00:56:36 localhost dnsmasq[8458]: cleared cache
> Jan 10 00:56:36 localhost dbus[1023]: [system] Activating via systemd: 
> service name='org.freedesktop.nm_dispatcher' 
> unit='dbus-org.freedesktop.nm-dispatcher.service'
> Jan 10 00:56:36 localhost dbus[1023]: [system]

[Touch-packages] [Bug 1432599] Re: Network-manager tries to manage virbr0, which it should not

2016-05-27 Thread Trent McPheron 
This affected me when I went from Xubuntu 15.10 to 16.04; the wired
network icon would be shown whenever I wasn't connected to any actual
networks, and adding the config tweak in #4 triages the issue for me.

-- 
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/1432599

Title:
  Network-manager tries to manage virbr0, which it should not

Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager package in Fedora:
  Unknown

Bug description:
  Since a recent upgrade in vivid, nm is trying to manage virbr0. This
  results in my main machine not getting a real IP address on eth0, and
  virtual machines not being able to use the network.

  This is probably related to
  https://bugzilla.redhat.com/show_bug.cgi?id=1166199

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 16 12:36:07 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-12-13 (92 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  IpRoute:
   default via 10.0.0.1 dev eth0  proto static  metric 1024
   10.0.0.0/24 dev eth0  proto kernel  scope link  src 10.0.0.75
   192.168.111.0/24 dev wlan0  proto kernel  scope link  src 192.168.111.8
   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
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  http_proxy: http://localhost:8118/
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.
  no_proxy: localhost,127.0.0.0/8,::1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432599/+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

[Touch-packages] [Bug 1432599] Re: Network-manager tries to manage virbr0, which it should not

2015-10-30 Thread RobertDahlström 
For me this happened after upgrade from 15.04 to 15.10.
Adding suggested fix to NetworkManager.conf solved the issue.

-- 
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/1432599

Title:
  Network-manager tries to manage virbr0, which it should not

Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager package in Fedora:
  Unknown

Bug description:
  Since a recent upgrade in vivid, nm is trying to manage virbr0. This
  results in my main machine not getting a real IP address on eth0, and
  virtual machines not being able to use the network.

  This is probably related to
  https://bugzilla.redhat.com/show_bug.cgi?id=1166199

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 16 12:36:07 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-12-13 (92 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  IpRoute:
   default via 10.0.0.1 dev eth0  proto static  metric 1024
   10.0.0.0/24 dev eth0  proto kernel  scope link  src 10.0.0.75
   192.168.111.0/24 dev wlan0  proto kernel  scope link  src 192.168.111.8
   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
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  http_proxy: http://localhost:8118/
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.
  no_proxy: localhost,127.0.0.0/8,::1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432599/+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

[Touch-packages] [Bug 1432599] Re: Network-manager tries to manage virbr0, which it should not

2015-03-30 Thread Andreas Olsson 
** Bug watch added: Red Hat Bugzilla #1166199
   https://bugzilla.redhat.com/show_bug.cgi?id=1166199

** Also affects: network-manager (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1166199
   Importance: Unknown
   Status: Unknown

-- 
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/1432599

Title:
  Network-manager tries to manage virbr0, which it should not

Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager package in Fedora:
  Unknown

Bug description:
  Since a recent upgrade in vivid, nm is trying to manage virbr0. This
  results in my main machine not getting a real IP address on eth0, and
  virtual machines not being able to use the network.

  This is probably related to
  https://bugzilla.redhat.com/show_bug.cgi?id=1166199

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 16 12:36:07 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-12-13 (92 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  IpRoute:
   default via 10.0.0.1 dev eth0  proto static  metric 1024
   10.0.0.0/24 dev eth0  proto kernel  scope link  src 10.0.0.75
   192.168.111.0/24 dev wlan0  proto kernel  scope link  src 192.168.111.8
   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
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  http_proxy: http://localhost:8118/
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.
  no_proxy: localhost,127.0.0.0/8,::1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432599/+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

[Touch-packages] [Bug 1432599] Re: Network-manager tries to manage virbr0, which it should not

2015-03-30 Thread Launchpad Bug Tracker 
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: network-manager (Ubuntu)
   Status: New = Confirmed

-- 
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/1432599

Title:
  Network-manager tries to manage virbr0, which it should not

Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager package in Fedora:
  Unknown

Bug description:
  Since a recent upgrade in vivid, nm is trying to manage virbr0. This
  results in my main machine not getting a real IP address on eth0, and
  virtual machines not being able to use the network.

  This is probably related to
  https://bugzilla.redhat.com/show_bug.cgi?id=1166199

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 16 12:36:07 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-12-13 (92 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  IpRoute:
   default via 10.0.0.1 dev eth0  proto static  metric 1024
   10.0.0.0/24 dev eth0  proto kernel  scope link  src 10.0.0.75
   192.168.111.0/24 dev wlan0  proto kernel  scope link  src 192.168.111.8
   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
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  http_proxy: http://localhost:8118/
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.
  no_proxy: localhost,127.0.0.0/8,::1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432599/+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

[Touch-packages] [Bug 1432599] Re: Network-manager tries to manage virbr0, which it should not

2015-03-30 Thread Andreas Olsson 
Taking a cue from https://bugzilla.redhat.com/show_bug.cgi?id=1166199 I
worked around the issue by adding the following to my
/etc/NetworkManager/NetworkManager.conf

  [keyfile]
  unmanaged-devices=interface-name:virbr0

Yet I imagine that the real solution is something more general.

** Changed in: network-manager (Ubuntu)
   Importance: Undecided = Medium

-- 
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/1432599

Title:
  Network-manager tries to manage virbr0, which it should not

Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager package in Fedora:
  Unknown

Bug description:
  Since a recent upgrade in vivid, nm is trying to manage virbr0. This
  results in my main machine not getting a real IP address on eth0, and
  virtual machines not being able to use the network.

  This is probably related to
  https://bugzilla.redhat.com/show_bug.cgi?id=1166199

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 16 12:36:07 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-12-13 (92 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  IpRoute:
   default via 10.0.0.1 dev eth0  proto static  metric 1024
   10.0.0.0/24 dev eth0  proto kernel  scope link  src 10.0.0.75
   192.168.111.0/24 dev wlan0  proto kernel  scope link  src 192.168.111.8
   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
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  http_proxy: http://localhost:8118/
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.
  no_proxy: localhost,127.0.0.0/8,::1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432599/+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

[Touch-packages] [Bug 1432599] Re: Network-manager tries to manage virbr0, which it should not

2015-03-30 Thread Franck 
Here is the feedback I got from the network-manager mailing list:

On Thu, 2015-03-19 at 09:18 +0100, Franck Routier (perso) wrote:
 Hi list,

 I'm using Ubuntu and just upgraded to (still in development) Vivid.
 Now I see that network-manager handles my virbr0 bridge (libvirt), which 
 it didn't before.

NM will recognize and manage all network interfaces, but that does not
mean that NM actually touches the interfaces.  If the interface already
has a configuration, NM simply assumes the existing configuration and
waits for you to tell it to do something.  That's a difference from
older versions of NM (0.9.8 and earlier) where NM was mostly ignorant of
existing configuration.

We know that NM 0.9.10 still has a few edge cases where it touches
interfaces and shouldn't, but almost all of those have already been
fixed in NM 1.0 and later.

Dan

-- 
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/1432599

Title:
  Network-manager tries to manage virbr0, which it should not

Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager package in Fedora:
  Unknown

Bug description:
  Since a recent upgrade in vivid, nm is trying to manage virbr0. This
  results in my main machine not getting a real IP address on eth0, and
  virtual machines not being able to use the network.

  This is probably related to
  https://bugzilla.redhat.com/show_bug.cgi?id=1166199

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 16 12:36:07 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-12-13 (92 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  IpRoute:
   default via 10.0.0.1 dev eth0  proto static  metric 1024
   10.0.0.0/24 dev eth0  proto kernel  scope link  src 10.0.0.75
   192.168.111.0/24 dev wlan0  proto kernel  scope link  src 192.168.111.8
   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
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  http_proxy: http://localhost:8118/
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.
  no_proxy: localhost,127.0.0.0/8,::1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432599/+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

[Touch-packages] [Bug 1432599] Re: Network-manager tries to manage virbr0, which it should not

2015-03-30 Thread Franck 
The 

/etc/NetworkManager/NetworkManager.conf

[keyfile]
unmanaged-devices=interface-name:virbr0



indeed does the trick.

-- 
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/1432599

Title:
  Network-manager tries to manage virbr0, which it should not

Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager package in Fedora:
  Unknown

Bug description:
  Since a recent upgrade in vivid, nm is trying to manage virbr0. This
  results in my main machine not getting a real IP address on eth0, and
  virtual machines not being able to use the network.

  This is probably related to
  https://bugzilla.redhat.com/show_bug.cgi?id=1166199

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 16 12:36:07 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-12-13 (92 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  IpRoute:
   default via 10.0.0.1 dev eth0  proto static  metric 1024
   10.0.0.0/24 dev eth0  proto kernel  scope link  src 10.0.0.75
   192.168.111.0/24 dev wlan0  proto kernel  scope link  src 192.168.111.8
   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
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  http_proxy: http://localhost:8118/
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.
  no_proxy: localhost,127.0.0.0/8,::1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432599/+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

[Touch-packages] [Bug 1432599] Re: Network-manager tries to manage virbr0, which it should not

2015-03-19 Thread Franck 
Here is a bug report, related to the subject:
https://bugzilla.gnome.org/show_bug.cgi?id=731014

Notice vboxnet0 also appears in nm-applet, but is shown as Unmanaged,
unlike virbr0.

** Bug watch added: GNOME Bug Tracker #731014
   https://bugzilla.gnome.org/show_bug.cgi?id=731014

-- 
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/1432599

Title:
  Network-manager tries to manage virbr0, which it should not

Status in network-manager package in Ubuntu:
  New

Bug description:
  Since a recent upgrade in vivid, nm is trying to manage virbr0. This
  results in my main machine not getting a real IP address on eth0, and
  virtual machines not being able to use the network.

  This is probably related to
  https://bugzilla.redhat.com/show_bug.cgi?id=1166199

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 16 12:36:07 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-12-13 (92 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  IpRoute:
   default via 10.0.0.1 dev eth0  proto static  metric 1024
   10.0.0.0/24 dev eth0  proto kernel  scope link  src 10.0.0.75
   192.168.111.0/24 dev wlan0  proto kernel  scope link  src 192.168.111.8
   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
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  http_proxy: http://localhost:8118/
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.
  no_proxy: localhost,127.0.0.0/8,::1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432599/+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

[Touch-packages] [Bug 1432599] Re: Network-manager tries to manage virbr0, which it should not

2015-03-16 Thread Franck 
** Description changed:

- Since a recent upgrade in vivid, nm is tryoing to manage virbr0. This
+ Since a recent upgrade in vivid, nm is trying to manage virbr0. This
  results in my main machine not getting a real IP address on eth0, and
  virtual machines not being able to use the network.
  
  This is probably related to
  https://bugzilla.redhat.com/show_bug.cgi?id=1166199
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 16 12:36:07 2015
  IfupdownConfig:
-  # interfaces(5) file used by ifup(8) and ifdown(8)
-  auto lo
-  iface lo inet loopback
+  # interfaces(5) file used by ifup(8) and ifdown(8)
+  auto lo
+  iface lo inet loopback
  InstallationDate: Installed on 2014-12-13 (92 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  IpRoute:
-  default via 10.0.0.1 dev eth0  proto static  metric 1024 
-  10.0.0.0/24 dev eth0  proto kernel  scope link  src 10.0.0.75 
-  192.168.111.0/24 dev wlan0  proto kernel  scope link  src 192.168.111.8 
-  192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
+  default via 10.0.0.1 dev eth0  proto static  metric 1024
+  10.0.0.0/24 dev eth0  proto kernel  scope link  src 10.0.0.75
+  192.168.111.0/24 dev wlan0  proto kernel  scope link  src 192.168.111.8
+  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
-  WimaxEnabled=true
+  [main]
+  NetworkingEnabled=true
+  WirelessEnabled=true
+  WWANEnabled=true
+  WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  http_proxy: http://localhost:8118/
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.
  no_proxy: localhost,127.0.0.0/8,::1

-- 
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/1432599

Title:
  Network-manager tries to manage virbr0, which it should not

Status in network-manager package in Ubuntu:
  New

Bug description:
  Since a recent upgrade in vivid, nm is trying to manage virbr0. This
  results in my main machine not getting a real IP address on eth0, and
  virtual machines not being able to use the network.

  This is probably related to
  https://bugzilla.redhat.com/show_bug.cgi?id=1166199

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 16 12:36:07 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-12-13 (92 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  IpRoute:
   default via 10.0.0.1 dev eth0  proto static  metric 1024
   10.0.0.0/24 dev eth0  proto kernel  scope link  src 10.0.0.75
   192.168.111.0/24 dev wlan0  proto kernel  scope link  src 192.168.111.8
   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
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  http_proxy: http://localhost:8118/
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.
  no_proxy: localhost,127.0.0.0/8,::1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432599/+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

[Touch-packages] [Bug 1432599] [NEW] Network-manager tries to manage virbr0, which it should not

2015-03-16 Thread Franck 
Public bug reported:

Since a recent upgrade in vivid, nm is trying to manage virbr0. This
results in my main machine not getting a real IP address on eth0, and
virtual machines not being able to use the network.

This is probably related to
https://bugzilla.redhat.com/show_bug.cgi?id=1166199

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: network-manager 0.9.10.0-4ubuntu11
ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
Uname: Linux 3.19.0-9-generic x86_64
ApportVersion: 2.16.2-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Mar 16 12:36:07 2015
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2014-12-13 (92 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
IpRoute:
 default via 10.0.0.1 dev eth0  proto static  metric 1024
 10.0.0.0/24 dev eth0  proto kernel  scope link  src 10.0.0.75
 192.168.111.0/24 dev wlan0  proto kernel  scope link  src 192.168.111.8
 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
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
http_proxy: http://localhost:8118/
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: 
Error: Object 'nm' is unknown, try 'nmcli help'.
no_proxy: localhost,127.0.0.0/8,::1

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug vivid

-- 
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/1432599

Title:
  Network-manager tries to manage virbr0, which it should not

Status in network-manager package in Ubuntu:
  New

Bug description:
  Since a recent upgrade in vivid, nm is trying to manage virbr0. This
  results in my main machine not getting a real IP address on eth0, and
  virtual machines not being able to use the network.

  This is probably related to
  https://bugzilla.redhat.com/show_bug.cgi?id=1166199

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 16 12:36:07 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-12-13 (92 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  IpRoute:
   default via 10.0.0.1 dev eth0  proto static  metric 1024
   10.0.0.0/24 dev eth0  proto kernel  scope link  src 10.0.0.75
   192.168.111.0/24 dev wlan0  proto kernel  scope link  src 192.168.111.8
   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
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  http_proxy: http://localhost:8118/
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.
  no_proxy: localhost,127.0.0.0/8,::1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432599/+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