reassign 513852 network-manager forcemerge 513874 513852 thanks It turns out that this bug is caused by the attached interfaces file. Specifically, the 'home' interface stanza--commenting that out causes the system to return to normal.
I've no idea why network-manager is setting the system hostname to 'localhost.localdomain' (see the merged bug, above) but commenting out the 'home' interface also prevents this from occurring. -- Sam Morris <s...@robots.org.uk>
# 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 # The primary network interface #allow-hotplug eth0 #iface eth0 inet dhcp iface office_static inet static address 192.168.168.8 netmask 255.255.255.0 #gateway 192.168.168.248 # virgin, down? #gateway 192.168.168.252 # pipex #gateway 192.168.168.253 # virgin gateway 192.168.168.254 # virgin #dns-nameservers 192.168.168.248 #dns-nameservers 192.168.168.138 dns-nameservers 4.2.2.1 #iface home inet static # address 169.254.0.1 # netmask 255.255.0.0 # network 169.254.0.0 # broadcast 169.254.255.255 # gateway 169.254.0.2 # # dns-* options are implemented by the resolvconf package, if installed # dns-nameservers 212.74.112.66 212.74.112.67 iface home inet dhcp wireless-ssid sofasofa wireless-key AE12-B294-01F2-C140-5D32-9716-90
