we have an identified regression here, so importance: high. ** Changed in: network-manager (Ubuntu) Importance: Low => High
** Summary changed: - network-manager unmanaged mode causes confusion (Devices not managed after reboot) + [regression] network-manager unmanaged mode sets devices to unmanaged that were previously managed ** Description changed: + the regression here is that devices are unmanaged even though they dont + have a "auto eth0" line for instance. + + Here an example of an interfaces configuration that should not set the devices in unmanaged mode + https://bugs.edge.launchpad.net/ubuntu/+source/network-manager/+bug/279262/comments/14 + + + Original: + After update/upgrade/dist-upgrade of Ubuntu Intrepid today ( 6 Oct 2008 ) My network layer is not working more if i try to configure it (now is disabled) from top right icon i get: nm-ifupdown-connection.c 82 connection update not supported (read only) The system dont' ask me for a (sudo) password if i try to edit connections. Thank you ** Summary changed: - [regression] network-manager unmanaged mode sets devices to unmanaged that were previously managed + [regression] network-manager unmanaged mode sets devices to unmanaged that were managed in hardy and before ** Summary changed: - [regression] network-manager unmanaged mode sets devices to unmanaged that were managed in hardy and before + [regression] network-manager unmanaged mode sets devices to unmanaged that were managed in hardy -- [regression] network-manager unmanaged mode sets devices to unmanaged that were managed in hardy https://bugs.launchpad.net/bugs/279262 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
