2007/11/26, Josselin Mouette <[EMAIL PROTECTED]>: > reassign 452469 gnome-session > thanks > > Le vendredi 23 novembre 2007 à 18:04 +0100, Remi Vanicat a écrit : > > > There can be two reasons for this kind of issues: > > > 1. There is something misconfigured in the network settings (e.g. > > > the loopback interface or the DNS server), which is causing > > > timeouts. > > > > mm, telnet localhost smtp work as excpected, so the loopback interface > > seem to work. > > I've just test it: the session launch work as excpected if the network > > cable is unplug. So the problem is probably there >
Furher investigation show that for absence of hang time, the cable must be unplug, and it must be the first time I logon scince last reboot. If network has been plug and unplug, opening a new session might lead to some waiting. Note also that from time to time, nautilus hang for some time as it was on logging. > Yes, it would be interesting to see the network configuration > (ifconfig), the DNS configuration (/etc/resolv.conf) and the route > configuration (route -n) when the cable is plugged. When cable is plugged : $ route Table de routage IP du noyau Destination Passerelle Genmask Indic Metric Ref Use Iface 192.168.2.0 * 255.255.255.0 U 0 0 0 eth0 default 192.168.2.1 0.0.0.0 UG 0 0 0 eth0 $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 192.168.1.1 search neuf.fr $ ifconfig ath0 Lien encap:Ethernet HWaddr 00:16:CF:AF:70:16 adr inet6: fe80::216:cfff:feaf:7016/64 Scope:Lien UP BROADCAST RUNNING MULTICAST MTU:1500 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 lg file transmission:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) eth0 Lien encap:Ethernet HWaddr 00:16:D4:60:2A:7C inet adr:192.168.2.100 Bcast:192.168.2.255 Masque:255.255.255.0 adr inet6: fe80::216:d4ff:fe60:2a7c/64 Scope:Lien UP BROADCAST RUNNING MULTICAST MTU:1492 Metric:1 RX packets:261002 errors:0 dropped:0 overruns:0 frame:0 TX packets:151904 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:1000 RX bytes:109420129 (104.3 MiB) TX bytes:14079942 (13.4 MiB) Interruption:21 Adresse de base:0xa000 lo Lien encap:Boucle locale inet adr:127.0.0.1 Masque:255.0.0.0 adr inet6: ::1/128 Scope:Hôte UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:5795 errors:0 dropped:0 overruns:0 frame:0 TX packets:5795 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:0 RX bytes:1847248 (1.7 MiB) TX bytes:1847248 (1.7 MiB) wifi0 Lien encap:UNSPEC HWaddr 00-16-CF-AF-70-16-00-00-00-00-00-00-00-00-00-00 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:588605 errors:0 dropped:0 overruns:0 frame:1979901 TX packets:857 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:199 RX bytes:60143199 (57.3 MiB) TX bytes:39422 (38.4 KiB) Interruption:22 > > Another thought: do you have network-manager installed? Yes, but it is supposed to be the only thing that manage my network. I also use nfs on this computer (as a client, obviously when the network cable s plugged) _______________________________________________ pkg-gnome-maintainers mailing list pkg-gnome-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-gnome-maintainers