Hi,
I just installed ubu 10.4 and the network connections tool in the control center doesn't seem to do anything. I look at wired -> eth0 -> edit -> ip4 and give ti my static ip, netmask, gateway and dns and hit apply. Give root pw. Poofs away.

Ipconfig shows no IP address. Control center -> network tools -> eth0 shows ipv4 = 0.0.0.0, netmask same.

root: /etc/init.d/networking restart <enter> shows reconfiguring net interfaces [ok]. Ifconfig shows no inet4 address.

With the tools out of the box, it appears that you neither configure nor start a network. Why do they include these tools if they don't do anything?

ANSWER: You have to hit the disguised, magic button on the top middle of the screen which looks like an unplugged extension cord and click "auto eth0". When you set an IP address in windoz, it actually makes it go. What an unfriendly and poorly thought out design. After editing the settings, the "apply" button does not do what a normal person would think apply would mean.

And another, extremely annoying bug which has been there forever is the fact that when the root pw dialog pops up and you start typing, nothing happens. Your keystrokes go nowhere. Some lazy dork eons ago forgot to place the input focus on the password text box. You have to mouse click inside the password text box before it will accept your input. It is inconceivable that nobody has ever fixed this. Sloppy inattention to detail.

And, they want this to be a commercial release. Rotsa Ruck!

BrianP

I had some problems with networking when I first installed Ubuntu. Basically it was about the network interfaces weren't set up correctly (because the network card driver was yet to be included by default).

One can't expect any default configurations to work out of the box in *every possible* hardware environment; and if it doesn't, it doesn't really matter what GUI frontend you actually use.

Having checked that the basic tools (ifconfig/iwconfig/dhcpcd...[options]) give expected results, it's all about choosing a GUI that suits you. A great alternative to gnome-networkmanager is wicd.

As for gksu bug reports I'm sure you're better off filing them with the gksu community than in a LQ thread.

cheers..

Installing wicd, as suggested by kopatops, and then disabling the gnome network connections worked for me too.

I had lan connection working so downloaded the tar.gz distro of wicd to another machine and then used scp to copy it to my machine and installed it.

Thanks for the help..