ok. i think the regression is that devices are unmanaged even though
they dont have a auto eth0 line for instance.
If you have auto eth0/wlan0 or something and a iface eth0/wlan0... line
in your interfaces the behaviour is the same as in hardy. e.g. NM doesnt
manage such devices.
Here an example
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
ok, i renamed this bug to be more specific. if that doesnt really match
your issue, please file a new bug. This definitly includes when you have
problems getting access to network.
Anyway, i see several issues reported so far here, which I would like to
comment on now:
1. the original reporter
oops, don't worry. I didnt close this bug. Sorry if my last line caused
confusion.
--
network-manager unmanaged mode causes confusion (Devices not managed after
reboot)
https://bugs.launchpad.net/bugs/279262
You received this bug notification because you are a member of Ubuntu
Bugs, which is
OK. I've filed:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/284189
--
network-manager unmanaged mode causes confusion (Devices not managed after
reboot)
https://bugs.launchpad.net/bugs/279262
You received this bug notification because you are a member of Ubuntu
Bugs, which
