User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9b2) Gecko/2007121914 Minefield/3.0b2 Build Identifier: This strange error message ("could not look up internet address for Foo") occurs just for so at startup, which means that /etc/hosts is correct and that things worked at earlier time. I know this problem from a previous gnome installation and have it now with Xfce. The first time I was able to solve the issue by exchanging the util-linux login with the shadow-passwords login. However, I never understood this issue because the network is accessible, the desktop works and internet works too. This time the problem occurred 'suddenly' after an xorg update. A re-install of Xfce didn't help. Can you please tell me what the matter is (what the session manager asks the xorg server and why this may fail?) My network is routed via a DSL-Router. The ifconfig is as follows: eth0 Link encap:Ethernet HWaddr 00:13:D4:F5:1F:3B inet addr:192.168.178.21 Bcast:192.168.178.255 Mask:255.255.255.0 inet6 addr: fe80::213:d4ff:fef5:1f3b/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1011383 errors:0 dropped:0 overruns:0 frame:0 TX packets:528083 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1439981404 (1373.2 Mb) TX bytes:35725991 (34.0 Mb) Interrupt:17 Base address:0xc000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Reproducible: Always
Assuming that "Foo" is your host name (the name returned by gethostbyname), then this messsage tells you, that this name cannot be resolved using the libc DNS resolver (most probably a broken /etc/hosts, but that's not the only possible cause). This is a safety check in xfce4-session to ensure that your environment is sane, because otherwise applications will not be able to connect to the session manager at all.
found the bug in my settings