NetworkManager 0.8 sets IPv6 method to automatic after upgrade for some users (Was: not get IPv4 address for wired Auto connections because IPv6 fails)

[Halton Huo]

Binary package hint: network-manager

Follow with https://wiki.ubuntu.com/DebuggingNetworkManager

I get following message (/var/log/syslog) when "sudo killall NetworkManager"

When I disable eth0 IPv6 method to "Ignore" in Network Connections, the IPv4 address can be assigned correctly.

Sep 23 15:04:01 hp-dv2000 NetworkManager: <WARN> nm_signal_handler(): Caught signal 15, shutting down normally.
Sep 23 15:04:01 hp-dv2000 NetworkManager: <info> (eth0): cleaning up...
Sep 23 15:04:01 hp-dv2000 NetworkManager: <info> (eth0): taking down device.
Sep 23 15:04:01 hp-dv2000 NetworkManager: <info> exiting (success)
Sep 23 15:04:01 hp-dv2000 avahi-daemon[3243]: Withdrawing address record for fe80::21d:72ff:fe44:c146 on eth0.
Sep 23 15:04:01 hp-dv2000 init: network-manager main process ended, respawning
Sep 23 15:04:01 hp-dv2000 NetworkManager: <info> starting...
Sep 23 15:04:01 hp-dv2000 NetworkManager: <info> modem-manager is now available
Sep 23 15:04:01 hp-dv2000 NetworkManager: SCPlugin-Ifupdown: init!
Sep 23 15:04:01 hp-dv2000 NetworkManager: SCPlugin-Ifupdown: update_system_hostname
Sep 23 15:04:01 hp-dv2000 NetworkManager: SCPluginIfupdown: management mode: unmanaged
Sep 23 15:04:01 hp-dv2000 NetworkManager: SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:1c.1/0000:05:00.0/net/eth0, iface: eth0)
Sep 23 15:04:01 hp-dv2000 NetworkManager: SCPlugin-Ifupdown: device added (path: /sys/devices/pci0000:00/0000:00:1c.1/0000:05:00.0/net/eth0, iface: eth0): no exported connection
Sep 23 15:04:01 hp-dv2000 NetworkManager: SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:1c.3/0000:07:00.0/net/wlan0, iface: wlan0)
Sep 23 15:04:01 hp-dv2000 NetworkManager: SCPlugin-Ifupdown: device added (path: /sys/devices/pci0000:00/0000:00:1c.3/0000:07:00.0/net/wlan0, iface: wlan0): no exported connection
Sep 23 15:04:01 hp-dv2000 NetworkManager: SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:1c.3/0000:07:00.0/net/wmaster0, iface: wmaster0)
Sep 23 15:04:01 hp-dv2000 NetworkManager: SCPlugin-Ifupdown: device added (path: /sys/devices/pci0000:00/0000:00:1c.3/0000:07:00.0/net/wmaster0, iface: wmaster0): no exported connection
Sep 23 15:04:01 hp-dv2000 NetworkManager: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/lo, iface: lo)
Sep 23 15:04:01 hp-dv2000 NetworkManager: SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/lo, iface: lo): no exported connection
Sep 23 15:04:01 hp-dv2000 NetworkManager: SCPlugin-Ifupdown: end _init.
Sep 23 15:04:01 hp-dv2000 NetworkManager: Loaded plugin ifupdown: (C) 2008 Canonical Ltd. To report bugs please use the NetworkManager mailing list.
Sep 23 15:04:01 hp-dv2000 NetworkManager: Loaded plugin keyfile: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
Sep 23 15:04:01 hp-dv2000 NetworkManager: <info> Found radio killswitch rfkill0 (at /sys/devices/pci0000:00/0000:00:1c.3/0000:07:00.0/ieee80211/phy0/rfkill0) (driver <unknown>)
Sep 23 15:04:01 hp-dv2000 NetworkManager: <info> Wireless now disabled by radio killswitch
Sep 23 15:04:01 hp-dv2000 NetworkManager: SCPlugin-Ifupdown: (164801312) ... get_connections.
Sep 23 15:04:01 hp-dv2000 NetworkManager: SCPlugin-Ifupdown: (164801312) ... get_connections (managed=false): return empty list.
Sep 23 15:04:01 hp-dv2000 NetworkManager: Ifupdown: get unmanaged devices count: 0
Sep 23 15:04:01 hp-dv2000 NetworkManager: <info> (eth0): new Ethernet device (driver: 'sky2')
Sep 23 15:04:01 hp-dv2000 NetworkManager: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0
Sep 23 15:04:01 hp-dv2000 NetworkManager: <info> (eth0): now managed
Sep 23 15:04:01 hp-dv2000 NetworkManager: <info> (eth0): device state change: 1 -> 2 (reason 2)
Sep 23 15:04:01 hp-dv2000 NetworkManager: <info> (eth0): bringing up device.
Sep 23 15:04:01 hp-dv2000 NetworkManager: <info> (eth0): preparing device.
Sep 23 15:04:01 hp-dv2000 NetworkManager: <info> (eth0): deactivating device (reason: 2).
Sep 23 15:04:01 hp-dv2000 NetworkManager: <info> (wlan0): driver supports SSID scans (scan_capa 0x01).
Sep 23 15:04:01 hp-dv2000 NetworkManager: <info> (wlan0): new 802.11 WiFi device (driver: 'iwl3945')
Sep 23 15:04:01 hp-dv2000 NetworkManager: <info> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/1
Sep 23 15:04:01 hp-dv2000 NetworkManager: <info> (wlan0): now managed
Sep 23 15:04:01 hp-dv2000 NetworkManager: <info> (wlan0): device state change: 1 -> 2 (reason 2)
Sep 23 15:04:01 hp-dv2000 NetworkManager: <info> (wlan0): bringing up device.
Sep 23 15:04:01 hp-dv2000 NetworkManager: <info> (wlan0): deactivating device (reason: 2).
Sep 23 15:04:01 hp-dv2000 NetworkManager: <WARN> default_adapter_cb(): bluez error getting default adapter: The name org.bluez was not provided by any .service files
Sep 23 15:04:04 hp-dv2000 NetworkManager: <info> (eth0): carrier now ON (device state 2)
Sep 23 15:04:04 hp-dv2000 NetworkManager: <info> (eth0): device state change: 2 -> 3 (reason 40)
Sep 23 15:04:04 hp-dv2000 NetworkManager: <info> Activation (eth0) starting connection 'Auto eth0'
Sep 23 15:04:04 hp-dv2000 NetworkManager: <info> (eth0): device state change: 3 -> 4 (reason 0)
Sep 23 15:04:04 hp-dv2000 NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Sep 23 15:04:04 hp-dv2000 NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Sep 23 15:04:04 hp-dv2000 NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Sep 23 15:04:04 hp-dv2000 NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Sep 23 15:04:04 hp-dv2000 NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Sep 23 15:04:04 hp-dv2000 NetworkManager: <info> (eth0): device state change: 4 -> 5 (reason 0)
Sep 23 15:04:04 hp-dv2000 NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Sep 23 15:04:04 hp-dv2000 NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Sep 23 15:04:04 hp-dv2000 NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Sep 23 15:04:04 hp-dv2000 NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Sep 23 15:04:04 hp-dv2000 NetworkManager: <info> (eth0): device state change: 5 -> 7 (reason 0)
Sep 23 15:04:04 hp-dv2000 NetworkManager: <info> Activation (eth0) Beginning DHCP transaction (timeout in 45 seconds)
Sep 23 15:04:04 hp-dv2000 dhclient: Internet Systems Consortium DHCP Client V3.1.2
Sep 23 15:04:04 hp-dv2000 dhclient: Copyright 2004-2008 Internet Systems Consortium.
Sep 23 15:04:04 hp-dv2000 dhclient: All rights reserved.
Sep 23 15:04:04 hp-dv2000 dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Sep 23 15:04:04 hp-dv2000 dhclient:
Sep 23 15:04:04 hp-dv2000 NetworkManager: <info> dhclient started with pid 3365
Sep 23 15:04:04 hp-dv2000 NetworkManager: <info> Activation (eth0) Beginning IP6 addrconf.
Sep 23 15:04:04 hp-dv2000 NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Sep 23 15:04:04 hp-dv2000 NetworkManager: <info> DHCP: device eth0 state changed (null) -> preinit
Sep 23 15:04:04 hp-dv2000 dhclient: Listening on LPF/eth0/00:1d:72:44:c1:46
Sep 23 15:04:04 hp-dv2000 dhclient: Sending on LPF/eth0/00:1d:72:44:c1:46
Sep 23 15:04:04 hp-dv2000 dhclient: Sending on Socket/fallback
Sep 23 15:04:05 hp-dv2000 avahi-daemon[3243]: Registering new address record for fe80::21d:72ff:fe44:c146 on eth0.*.
Sep 23 15:04:07 hp-dv2000 dhclient: DHCPREQUEST of 129.158.217.49 on eth0 to 255.255.255.255 port 67
Sep 23 15:04:07 hp-dv2000 dhclient: DHCPACK of 129.158.217.49 from 129.158.217.2
Sep 23 15:04:07 hp-dv2000 NetworkManager: <info> DHCP: device eth0 state changed preinit -> reboot
Sep 23 15:04:07 hp-dv2000 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) scheduled...
Sep 23 15:04:07 hp-dv2000 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) started...
Sep 23 15:04:07 hp-dv2000 NetworkManager: <info> address 129.158.217.49
Sep 23 15:04:07 hp-dv2000 NetworkManager: <info> prefix 24 (255.255.255.0)
Sep 23 15:04:07 hp-dv2000 NetworkManager: <info> gateway 129.158.217.254
Sep 23 15:04:07 hp-dv2000 NetworkManager: <info> hostname 'dhcp-cbjs05-217-49'
Sep 23 15:04:07 hp-dv2000 dhclient: bound to 129.158.217.49 -- renewal in 6370 seconds.
Sep 23 15:04:07 hp-dv2000 NetworkManager: <info> nameserver '129.158.216.14'
Sep 23 15:04:07 hp-dv2000 NetworkManager: <info> nameserver '129.158.166.14'
Sep 23 15:04:07 hp-dv2000 NetworkManager: <info> nameserver '129.158.71.131'
Sep 23 15:04:07 hp-dv2000 NetworkManager: <info> domain name 'Prc.Sun.COM'
Sep 23 15:04:07 hp-dv2000 NetworkManager: <info> wins '129.158.216.17'
Sep 23 15:04:07 hp-dv2000 NetworkManager: <info> wins '129.158.216.18'
Sep 23 15:04:07 hp-dv2000 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) complete.
Sep 23 15:04:14 hp-dv2000 NetworkManager: <info> Device 'eth0' IP6 addrconf timed out or failed.
Sep 23 15:04:14 hp-dv2000 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP6 Configure Timeout) scheduled...
Sep 23 15:04:14 hp-dv2000 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP6 Configure Timeout) started...
Sep 23 15:04:14 hp-dv2000 NetworkManager: <info> (eth0): device state change: 7 -> 9 (reason 5)
Sep 23 15:04:14 hp-dv2000 NetworkManager: <info> Marking connection 'Auto eth0' invalid.
Sep 23 15:04:14 hp-dv2000 NetworkManager: <info> Activation (eth0) failed.
Sep 23 15:04:14 hp-dv2000 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP6 Configure Timeout) complete.
Sep 23 15:04:14 hp-dv2000 NetworkManager: <info> (eth0): device state change: 9 -> 3 (reason 0)
Sep 23 15:04:14 hp-dv2000 NetworkManager: <info> (eth0): deactivating device (reason: 0).
Sep 23 15:04:14 hp-dv2000 NetworkManager: <info> (eth0): canceled DHCP transaction, dhcp client pid 3365

ProblemType: Bug
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
Date: Wed Sep 23 15:09:51 2009
DistroRelease: Ubuntu 9.10
IfupdownConfig:
 auto lo
 iface lo inet loopback
IpRoute:
 129.158.217.0/24 dev eth0 proto kernel scope link src 129.158.217.49 metric 1
 169.254.0.0/16 dev eth0 scope link metric 1000
 default via 129.158.217.254 dev eth0 proto static
NonfreeKernelModules: nvidia
Package: network-manager 0.8~a~git.20090911t130220.4c77fa0-0ubuntu6
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.35-generic
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: yes
SourcePackage: network-manager
Uname: Linux 2.6.31-10-generic i686
WpaSupplicantLog:

[Alexander Sack (asac)]

seems that Auto connections don't have the ipv6 settings set to ignore by default.

Please confirm that creating a new ethernet connection in the connection editor makes this work for you.

[Alexander Sack (asac)]

any info on this?

[Alexander Sack (asac)]

bug 430899 might be a dupe of this.

[Tony Espy (awe)]

Halton, can you confirm whether or not this system was upgraded from Jaunty ( 9.04 )?

[Tony Espy (awe)]

I just installed Jaunty, and only used my Ethernet connection, next I did an upgrade to Karmic and after it finished and re-booted, my Ethernet connection worked just fine. I double-checked it in the Connections Editor and IPv6 methods is set to "Ignore" as it should be.

I'm going to try one more time after first making my Ethernet connection "available to all users".

[Tony Espy (awe)]

So I tried again with a fresh install of Jaunty. Turns out that "make available to all users" is the default, so I un-checked for eth0 before running the upgrade. The upgrade ran OK, and I made sure to unplug the Ethernet cable before rebooting.

After the reboot, I plugged in the cable and things worked as expected.

On a whim, I checked the applet and this is where it got strange... the applet showed me connected to "Auto eth0", but also showed a second "Auto eth0" and a "Auto Ethernet" connections under "Available". I checked them out in the Connections Editor, and "Auto Ethernet" shows it a Last Used of "2 hours ago", whereas the other two "Auto eth0" entries show "never" ( even though one of them is the currently active connection ). Also the two "Auto eth0" differ only due to the "available to all users" setting.

[Alexander Sack (asac)]

On Wed, Oct 14, 2009 at 02:35:23AM -0000, Tony Espy wrote:
> So I tried again with a fresh install of Jaunty. Turns out that "make
> available to all users" is the default, so I un-checked for eth0 before
> running the upgrade. The upgrade ran OK, and I made sure to unplug the
> Ethernet cable before rebooting.
>
> After the reboot, I plugged in the cable and things worked as expected.
>
> On a whim, I checked the applet and this is where it got strange... the
> applet showed me connected to "Auto eth0", but also showed a second
> "Auto eth0" and a "Auto Ethernet" connections under "Available". I
> checked them out in the Connections Editor, and "Auto Ethernet" shows it
> a Last Used of "2 hours ago", whereas the other two "Auto eth0" entries
> show "never" ( even though one of them is the currently active
> connection ). Also the two "Auto eth0" differ only due to the
> "available to all users" setting.
>

hmm. do you also see NM reconnecting whenever you edit a connection?

Also, since when is system-connection the default in jaunty?

 - Alexander

[Halton Huo (halton-huo)]

I do kept updating to latest development Ubuntu repo. I'm not sure when the IPv6 setting is changed to Automatic. But if you change IPv6 from Ignore to Automatic, this bug always happens .

[Tony Espy (awe)]

Alexander, I just did a fresh Jaunty install on my Macbook Pro.

I have a single wired connection which I haven't actually used yet. It's called "Auto eth0", and it has the following attributes:

Global:
 * Connect automatically - True
 * Available to all users - True

Wired:
 * MAC address - 00:1B:63:AC:3C:23
 * MTU - Automatic

IPv4:
 * Method: Automatic (DHCP)

[Tony Espy (awe)]

OK, did yet another Jaunty-to-Karmic upgrade, but this time I made sure Jaunty had been updated to latest first.

I also followed the same procedure and unplugged the Ethernet cable before rebooting, and then plugged it in after it came up.

This time, I ended up with just a single Wired interface ( Auto eth0 ), and the IPv6 setting was set to Ignore as with all my other updates, so everything worked as expected.

I suspect there's at least one issue ( ie. multiple Wired connections ) when upgrading from base Jaunty to Karmic, however I still have yet to hit the IPv6 = Automatic issue yet.

[Tony Espy (awe)]

Alexander, to answer your other question about NM re-connecting when I edit a connection...

When I edit a wired connection, I don't see any visible disconnect / re-connects when I change MTU or auto-connect and hit Apply. If however I make "Available to all users" false, I see a disconnect, and the system doesn't automatically re-connect. This also seems to be a culprit in the creation of more than one Wired interface. After the disconnect, if I click on the applet menu, I see:

Wired Network
   disconnected
o Auto Ethernet

If I select it, then the I'm connected, and if I open the Connection Editor, I now see two wired interfaces:

Auto Ethernet
Auto eth0

Neither of them are available to all users, and the new Auto Ethernet connection doesn't seem to have a MAC address set.

[Alexander Sack (asac)]

one symptom related to this bug: "nm reconnects when connection editor is opened" turned out to be a crash caused by polkit for system connections. There are two variants: bug 432452 and bug 438574 ... which should be fixed in next policykit upload.

[Martin Pitt (pitti)]

Not reproducible after many attempts, removing milestone.

[Alexander Sack (asac)]

keeping bug open, but untargetting from karmic until we get a new dupe of someone who upgraded _after_ beta.

[Rick Spencer (rick-rickspencer3)]

Can't repro this, so won't get fixed for Karmic, if in fact the bug still exists.

[Halton Huo (halton-huo)]

Does anybody else can reproduce this bug if you manually change IPv6 settings to Automatic? If so, I do think this bug should be kept opening.

[Alexander Sack (asac)]

On Wed, Oct 21, 2009 at 02:28:48AM -0000, Halton Huo wrote:
> Does anybody else can reproduce this bug if you manually change IPv6
> settings to Automatic? If so, I do think this bug should be kept
> opening.

this bug is not about issues that might appear if you manually set IP6 to
Automatic. If you have issues with IP6 Automatic setup, then file a new
bug about that.

This bug is _solely_ about NM using "Automatic" rather than Ignore for IP6
after upgrade - without the user ever touching the IP6 settings at all.

 - Alexander

[Halton Huo (halton-huo)]

> this bug is not about issues that might appear if you manually set IP6 to
> Automatic. If you have issues with IP6 Automatic setup, then file a new
> bug about that.
>
> This bug is _solely_ about NM using "Automatic" rather than Ignore for IP6
> after upgrade - without the user ever touching the IP6 settings at all.
Alex, it is really I want when I initially report this bug. Should I open a new one in that way?

[oliver (oliver-schinagl)]

I just installed the latest RC using the netboot images via PXE, and after apt-get install ubuntu-desktop I get a non working wired connection still.

I do have some ifupdown (eth0) wired connection which won't get used, nor can I edit it. Editing nm-system-settings.conf i can change managed to true and the wired connection becomes useable.

What ever happened to the whole 'just plug-in a wire and it works'?

[Alexander Sack (asac)]

On Fri, Oct 23, 2009 at 12:50:36AM -0000, oliver wrote:
> I just installed the latest RC using the netboot images via PXE, and
> after apt-get install ubuntu-desktop I get a non working wired
> connection still.
>
> I do have some ifupdown (eth0) wired connection which won't get used,
> nor can I edit it. Editing nm-system-settings.conf i can change managed
> to true and the wired connection becomes useable.
>
> What ever happened to the whole 'just plug-in a wire and it works'?

if you have anything in /etc/network/interfaces configured, you opt-out
from that ... rather say "hey, i will use the old ifup/ifdown commands"

... so remove everything related to eth0 fromt hat file or run NM in managed
mode. seems to work well for you.

 - Alexander

[Mathieu Trudel-Lapierre (cyphermox)]

Looks to me like bug #466886 is a duplicate of this one.

[Josh (majik)]

On Wed, Oct 21, 2009 at 02:28:48AM -0000, Halton Huo wrote:
>> Does anybody else can reproduce this bug if you manually change IPv6
>> settings to Automatic? If so, I do think this bug should be kept
>> opening.

> this bug is not about issues that might appear if you manually set IP6 to
> Automatic. If you have issues with IP6 Automatic setup, then file a new
> bug about that.

> This bug is _solely_ about NM using "Automatic" rather than Ignore for IP6
> after upgrade - without the user ever touching the IP6 settings at all.

> - Alexander

I created a separate bug for the IPv6 issue ( bug #466886) but it was marked as a duplicate of this bug...

See comment #22 .

Maybe people could *read* the bug they're marking bugs dupes of before marking them dupes?

[Mathieu Trudel-Lapierre (cyphermox)]

Right, sorry about that Josh. Reverting my change :)

[Mathieu Trudel-Lapierre (cyphermox)]

@Alexander, I'd mark the fact that this is upgrade-related in the bug title or a tag, but I'm not sure how you want to manage them...

[oliver (oliver-schinagl)]

@Alexander,

sorry for the late reply, I noticed it on the final build as well, I installed ubuntu via PXE, and then apt-get install ubuntu-desktop. After that all completed I ended up with unmanaged wired connection. I can see how 'just editing the file' fixes it, but a) why do I have to do this in the first place? Why does the stuff get there anyhow? Is this related to installing the net-installer first and then running apt-get install ubuntu-desktop? shouldn't that also result in a system where you plug in your cable, and it just works?

[Alexander Sack (asac)]

On Wed, Dec 23, 2009 at 12:33:48AM -0000, oliver wrote:
> @Alexander,
>
> sorry for the late reply, I noticed it on the final build as well, I
> installed ubuntu via PXE, and then apt-get install ubuntu-desktop. After
> that all completed I ended up with unmanaged wired connection. I can see
> how 'just editing the file' fixes it, but a) why do I have to do this in
> the first place? Why does the stuff get there anyhow? Is this related to
> installing the net-installer first and then running apt-get install
> ubuntu-desktop? shouldn't that also result in a system where you plug in
> your cable, and it just works?
>

could be that net-install sets up a interfaces entrey ... which
blacklists it from NM atm.

This is needed becase there are folks that insist on using ifupdown
(the manual tools) and there is no good bi-directional integration for
ifupdown and NM atm.

 - Alexander

[antonio manuel (ac26649)]

You are in the right way but solution is uncommenting the file /etc/sysctl.conf in the way you need.
I also had the same problem with NM, then I wrote my personal /etc/network/interfaces adding some lines then uncommenting /etc/sysctl.conf NM begin to work not at all there are also some Servers I could not contact but I think is a configuration problem.
God Networking.

[viktor (lfraisse)]

Not sure if I have to post this here: Auto eth0 was not working yesterday (I checked my network card and ISP connection) although there had not been updates performed in the recent days.

Workaround: I had to open Network Manager and manually create a wired auto-dhcp connection.
Auto eth0 works fine today without the need of the previously created wired profile.

I'm running up-to-date Lucid amd64 (upgraded from karmic during beta stage).

May 2 11:42:01 karmic-koala dhclient: DHCPREQUEST of 192.168.0.17 on eth0 to 192.168.0.1 port 67
May 2 11:42:02 karmic-koala dhclient: DHCPACK of 192.168.0.17 from 192.168.0.1
May 2 11:42:02 karmic-koala dhclient: bound to 192.168.0.17 -- renewal in 1572 seconds.
May 2 11:42:02 karmic-koala NetworkManager: <info> DHCP: device eth0 state changed bound -> renew
May 2 11:42:02 karmic-koala NetworkManager: <info> address 192.168.0.17
May 2 11:42:02 karmic-koala NetworkManager: <info> prefix 24 (255.255.255.0)
May 2 11:42:02 karmic-koala NetworkManager: <info> gateway 192.168.0.1
May 2 11:42:02 karmic-koala NetworkManager: <info> nameserver '89.2.0.1'
May 2 11:42:02 karmic-koala NetworkManager: <info> nameserver '89.2.0.2'
May 2 12:08:14 karmic-koala dhclient: DHCPREQUEST of 192.168.0.17 on eth0 to 192.168.0.1 port 67
May 2 12:08:15 karmic-koala dhclient: DHCPACK of 192.168.0.17 from 192.168.0.1
May 2 12:08:15 karmic-koala dhclient: bound to 192.168.0.17 -- renewal in 1791 seconds.
May 2 12:17:02 karmic-koala CRON[2719]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 2 12:38:06 karmic-koala dhclient: DHCPREQUEST of 192.168.0.17 on eth0 to 192.168.0.1 port 67
May 2 12:38:07 karmic-koala dhclient: DHCPACK of 192.168.0.17 from 192.168.0.1
May 2 12:38:07 karmic-koala dhclient: bound to 192.168.0.17 -- renewal in 1726 seconds.
May 2 12:53:11 karmic-koala anacron[3235]: Anacron 2.3 started on 2010-05-02
May 2 12:53:11 karmic-koala anacron[3235]: Normal exit (0 jobs run)
May 2 12:53:12 karmic-koala NetworkManager: <info> Sleeping...
May 2 12:53:12 karmic-koala NetworkManager: <info> (eth0): now unmanaged
May 2 12:53:12 karmic-koala NetworkManager: <info> (eth0): device state change: 8 -> 1 (reason 37)
May 2 12:53:12 karmic-koala NetworkManager: <info> (eth0): deactivating device (reason: 37).
May 2 12:53:12 karmic-koala NetworkManager: <info> (eth0): canceled DHCP transaction, dhcp client pid 1025
May 2 12:53:12 karmic-koala NetworkManager: <WARN> check_one_route(): (eth0) error -34 returned from rtnl_route_del(): Sucess#012
May 2 12:53:12 karmic-koala NetworkManager: <info> (eth0): cleaning up...
May 2 12:53:12 karmic-koala NetworkManager: <info> (eth0): taking down device.

[Thomas Hood (jdthood)]

There has been no activity in this bug report for quite a long time and I wonder whether or not it has been fixed in the meantime and/or become irrelevant because Karmic is no longer supported and the bug perhaps only occurred on upgrade to Karmic and not to Lucid.