Upgrading to Hardy Trashes Network Settings
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Invalid
|
Medium
|
Unassigned |
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.