desktop-packages team mailing list archive

[Launchpad Bug Tracker <214360@xxxxxxxxxxxxxxxxxx>]

[Expired for gnome-system-tools (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: gnome-system-tools (Ubuntu)
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-system-tools in Ubuntu.
https://bugs.launchpad.net/bugs/214360

Title:
  [Hardy] network-admin settings to DHCP do not work

Status in “gnome-system-tools” package in Ubuntu:
  Expired

Bug description:
  On a newly-updated Hardy beta install I selected System ->
  Administration -> Network and chose my wired interface and Properties.
  The interface had the "Roaming mode" checkbox enabled and it was able
  to use DHCP to obtain an IP address, etc.

  I unchecked the Roaming Mode box and selected DHCP in the
  "Configuration" box, then added my domain name to the "General" tab
  (the hostname was already there) and clicked OK and close.

  I rebooted my system, and it was a huge mess:

   1) My ethernet interface was configured for IPV6 (!!) and no DHCP
  request was made (according to the log files).  This means I couldn't
  access any of my DNS servers, which are only available via IPV4, among
  other things.

   2) My /etc/hosts file did not have an entry for my hostname "myhost";
  there was ONLY an entry for "myhost.mydomain.com".  This caused me to
  not be able to sudo anymore, since I got an error "host myhost not
  found".

  Since I couldn't sudo I had to reboot off my CD, mount my root
  partition, and edit my /etc/hosts file to add "myhost" to the
  127.0.0.1 IP address.  Then I was able to reboot and re-enable roaming
  mode and thus get my eth0 interface to use ipv4 again.

  I'm not exactly sure what changing the configuration in network-admin
  is supposed to do.  I did see that it added a line "iface eth0 inet
  dhcp" to my /etc/network/interfaces file, which is what I would
  expect.  However, after the reboot I could see form the logs that
  NetworkManager was still running; maybe that was interfering?  For
  sure there were NO messages about dhcp in any of the log files after I
  rebooted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/214360/+subscriptions