Is this reproducible on Oneiric or Precise?
I'd be very tempted to close this a Fix Released given the general age
of this bug and that I'm pretty sure it's been properly fixed in Oneiric
or even earlier.
Of course, this still means we might want to fix it for earlier releases
provided the exact cause of the issue can be figured out and that a
patch is made available, simple enough to be uploaded as SRU (I don't
see why such a fix wouldn't be, really).
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/279262
Title:
Ethernet unusable after Maverick-Natty upgrade; device unmanaged; no
way to change it
Status in “network-manager” package in Ubuntu:
Incomplete
Status in “network-manager” source package in Intrepid:
Won't Fix
Bug description:
the regression here is that devices are unmanaged even though they
dont have a "auto eth0" line in /etc/network/interfaces
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
To reproduce:
use the /etc/network/interfaces configuration from the above comment and see
that after restart the device is unmanaged in intrepid, but managed in hardy
(0.6).
The code we shipped in NM 0.6 that shows that auto connections were
blacklisted is:
for (curr_b = ifparser_getfirst (); curr_b; curr_b = curr_b->next) {
if ((!strcmp (curr_b->type, "auto") || !strcmp (curr_b->type,
"allow-hotplug"))
&& strstr (curr_b->name, iface))
blacklist = TRUE;
}
The proposed patch is committed to the ubuntu.0.7 branch (see Related
Branches section in this bug) and can be seen here:
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu.0.7/annotate/2957?file_id=012ifupdownunmanagea-20081022120139-7rgnlk84604f1ysu-1
Test packages with that patch are available:
https://edge.launchpad.net/~network-manager/+archive
Impact:
1. no impact for new users
2. no impact for users that installed in gutsy or later and didnt modify
their /etc/network/interfaces (e.g. through gnome network-admin)
3. users with dhcp that installed before that will most likely see their
interface as being "unmanaged" and "not upped on startup" even though those
interfaces were previously managed by NM. Note: we transitioned those old
installs in gutsy to NM by commenting just the "auto ethX" lines in
/etc/network/interfaces.
Risk:
+ patch appears reasonable minimal
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/279262/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
