No, localhost was already there but I had to add the machine name to /etc/hosts like this:
127.0.0.1 localhost 127.0.0.2 inspironjaime Where "inspironjaime" was the name I gave to the machine at install time. This problem happened when the name resolver was in a state in which it took long times to resolve any name or fail, like when the machine is connected to a LAN but can't reach a DNS. It seems like GNOME was trying to resolve the machine name every time a new window was opened, by adding the machine name to /etc/hosts as mentioned it was guaranteed to have an instant response so it didn't get delayed. I'm sorry but I can't check if this is still happening because now I'm using KDE4 on all my machines and purged GNOME (I got tired of all this .net - mono stuff around and all the cumbersome and unknown - no one knows where they are - config files and registers that reminded me Windows) Jaime Alberto Silva Colorado Ing. Electricista Gerente SG Automatización Ltda. Pereira \ Risaralda \ Colombia http://www.sgautomatizacion.com On Fri, May 28, 2010 at 7:17 AM, Fabian Greffrath <[email protected]>wrote: > As a workaround I've added the hostname to /etc/hosts with an IP like >> 127.0.0.2 (a loopback device address) >> > > Does this mean you did not have your localhost added to /etc/hosts before? > Please post your complete /etc/hosts file here. > > Does the problem still persist with a recent Debian GNOME setup? > > - Fabian >
