regression: wired network shown as disabled after boot

Same thing happens in Gnome.

This is still the case with recent updates of network-manager.

Another workaround is to reconnect the ethernet cable: network-manager will then reconnect (new DHCP request).

Is it possible that this bug is related to the fact that network is established by ifupdown package (as it is simple DHCP/auto config) and then network-manager does not properly detect that interface is already up (or some kind of timing issue when eth0 is still getting IP from DHCP server when n-m is checking it).

Thank you for taking the time to report this bug and helping to make Ubuntu better. The output of '/var/log/daemon.log' after booting up and being "disconnected" would be helpful. Thanks in advance.

Brian,

Please find attached the info requested in bug #105234.

File encrypted as I'm not sure it doesn't contain any sensitive info (too tired to review the whole thing).

Thanks

Sebastien - I looked through your attachment and did not find any sensitive, so it would be helpful if you could upload an unencrypted version of it for others to look at. Thanks in advance!

Here is the information requested :

Contains :
interfaces.txt
daemonlog.txt
ethtooleth0.txt
dmesg.txt
lspcivvn.txt

Thanks
Seb

Please find attached the excerpt of daemon.log after booting up

I'm using Gutsy up-to-date (network-manager 0.6.5-0ubuntu9) and I have the exact same problem.

As this is regression (compared to Feisty) and has impact on first impression on users (network seems to be down), I would suggest to add milestone for one of Tribe releases.

guido .... what is up with your blacklist file?
--
  /etc/modprobe.d/blacklist line 1: ignoring bad line starting with '#'
--
??

Actually, Alexander, I have no idea!

I noticed the problem, and tried to fix it, even coping the files over from another machine in which they work fine and writing them (both blacklist and modules appear to be malformed) from scratch with nano, but to no avail.

It seems to read characters that are note there, I thought about some strange encoding problem, but shoudn't they by ok as utf-8?

Anyway, it basically the comments that are skipped, so most of the times everything works. I don't know what else to do, so I planned to set up a fresh tribe 6 as soon as it comes out to is if it there has been a problem during the install.

Actually, Alexander, I have no idea!

I noticed the problem, and tried to fix it, even coping the files over from another machine in which they work fine and writing them (both blacklist and modules appear to be malformed) from scratch with nano, but to no avail.

It seems to read characters that are note there, I thought about some strange encoding problem, but shoudn't they by ok as utf-8?

Anyway, it's basically the comments that are skipped, so most of the times everything works. I don't know what else to do, so I planned to set up a fresh tribe 6 as soon as it comes out to is if it there has been a problem during the install.

On Fri, Aug 31, 2007 at 05:42:26PM -0000, Guido Conaldi wrote:
> Actually, Alexander, I have no idea!
>
> I noticed the problem, and tried to fix it, even coping the files over
> from another machine in which they work fine and writing them (both
> blacklist and modules appear to be malformed) from scratch with nano,
> but to no avail.
>
> It seems to read characters that are note there, I thought about some
> strange encoding problem, but shoudn't they by ok as utf-8?
>

is this on a livecd or real install?

 - Alexander

real install

I think this bug is the same as bug 133374, but I will leave it to Alexander if he wants to close one of the bugs as duplicate of the other.

this issue will be dealt with the fix for bug 139403.