FS#41397 - [networkmanager] tries to manage vboxnet0
Attached to Project:
Arch Linux
Opened by acidicX (acidicX) - Wednesday, 30 July 2014, 12:38 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 10 June 2016, 23:22 GMT
Opened by acidicX (acidicX) - Wednesday, 30 July 2014, 12:38 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 10 June 2016, 23:22 GMT
|
Details
Since yesterday's update to 0.9.10.0-2 NM tries to manage
the vboxnet0 interface. This makes no sense and wasn't the
case before. I guess it was blacklisted somehow and now it
isn't anymore.
To solve this temporarily, I've added it to unmanaged-devices, but it still shows up in the NM list (but now as unmanaged). Before the update, it wasn't in the NM interface list at all. I don't know if the problem comes from upstream, I've found no bug report there yet. Steps to reproduce: Start NM with VirtualBox installed See also: https://bbs.archlinux.org/viewtopic.php?id=184999 |
This task depends upon
As stated in the initial details this was not the case before the upgrade.