Comment 53 for bug 32906
Revision history for this message
| Sam (samuel-gower-deactivatedaccount) wrote Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on | #53 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
This problem occurred for my friend on his laptop when he upgraded from Gusty to Hardy. I first tried going into recovery mode and resetting the hostname, but there was no change. So instead I used the network-admin to change /etc/hosts; I aliased 127.0.0.1 as the hostname and localhost.
I'll try reproducing this on my own machine later, and see if I can confirm that network-admin corrupts the hosts file by adding the domain to the end of the host.