Upgrading to Hardy Trashes Network Settings

Bug #223263 reported by JR on 2008-04-27
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)

Bug Description

Ubuntu 8.0.4

I upgraded my Xubuntu system from gutsy to hardy via the Update Manager. Upon reboot I got the error message "can not resolve host Buriram" and neither my wired or wireless network connection would work. The Network Manager was all grayed out and useless.

I found, on the net, that the /etc/hosts file was probably trashed by the upgrade. I went in and changed the local host from "Buriram.Thailand" to "Buriram" and that fixed the resolve host error. (This was difficult to change because "sudo" kept giving me the resolve error!) I did a reboot, however my network was still trashed and Network Manager was still grayed out, useless. I had to use 'dhclient eth0' to configure my wired ethernet interface and get a working internet connection. The upgrade also wiped out my 'wicd' network manager. :( I use wicd because it works with my wireless card under ndswrapper device.

Upgrading to Hardy should not trash the network settings. The 'sudo' command should not fail on the local machine with a "resolve" error. Network Manager should not be "bricked" by the upgrade. Upgrading should not remove 'wicd'.

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please add the log files from '/var/log/dist-upgrade/' to this bug report as attachments? Thanks in advance.

Changed in update-manager:
importance: Undecided → Medium
JR (jon3141) wrote :

I have attached an archive of the upgrade log files.

Michael Vogt (mvo) wrote :
Changed in network-manager:
status: Incomplete → Triaged
Tom Helner (duffman) wrote :

I have seen this "grayed out Network Manager" issue on a few Hardy systems.
In every case there was an interface other than loopback configured in /etc/network/interfaces.

Please verify that your /etc/network/interfaces file looks like this:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

JR (jon3141) wrote :

I have attached a copy of the /etc/network/interfaces file. It looks okay to me.

CaptSpify (captspify) wrote :

I'm having the same issue, is there any fix for this yet?

i've attached my logs as well

Alexander Sack (asac) wrote :

this isnt triaged. i still dont understand what this problem is about. can you come up with a easy to reproduce step by step instructions?

only then add your thoughts about what might have caused it.

Update the bug description accordingly please. Thanks!

Changed in network-manager:
status: Triaged → Incomplete
Chris Coulson (chrisccoulson) wrote :

Alexander - I wonder if part of this problem is related to bug 185209?

 We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in network-manager:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers