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

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://he

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

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 pac

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

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

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

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

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

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 did

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

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 i

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

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

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

** 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 yo

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

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

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

** 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.