Your lo interface is not up. Applications trying to contact your localhost interface will wait forever, explaining your slow startup times.
-----Oorspronkelijk bericht----- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Namens Vladislav Titov Verzonden: dinsdag 8 mei 2007 11:01 Aan: [email protected] Onderwerp: Re: [arch] KDE init problem >Le Tue, 8 May 2007 11:52:51 +0400 (MSD), >"Vladislav Titov" <[EMAIL PROTECTED]> a crit : > >> Hello all. >> All was working fine before last update (I have performed it yesterday - 07 >> may 2007). Now I have problems with KDE applications: >> >> 1. If I try to login into KDE session then it hangs for several minutes on >> "Initializing system services" during splash screen display. After about 5-7 >> minutes panel appears on screen, but there are nothing on panel (window >> buttons, clock and other - all is absent). After next 5-7 minutes panel is >> started successfully and became operational. >> >> 2. If I try to login into Fluxbox then I get different problems with KDE >> applications: a) Krusader takes too long time to start - about 5 minutes, b) >> kcontrol (KDE control center) hangs during call to Open/Save dialog >windows - >> also about for 5 minutes. >> >> I can't find anything useful in logs /var/log/messages.log etc.(may be I >> search in wrong place..). Only thing I found is that Krusader wrote in >> console something like "ERROR :: Can't talk to klauncher". >> >> Can anybody give me any advice where to look to find out reason of such >> problem? It seems for me that this is some kind of config or daemon hanging >> problem, but I didn't change such kind of settings recently. >> >> Thanks in advance. >> Best regards, >> Vladislav Titov >> > >Hello > >This looks like a problem in the name resolution of your computer. > >Check that the hostname set in /etc/rc.conf is resolvable (in /etc/hosts for >example). Thank you. It seems that you are right. Usually I am working inside 2 networks. Because of it I have used 2 network profiles for it - 1) eth0, dhcp; 2) ath0, WiFi with WPA encyphering, dhcp. But recently I decided to move from using network profiles to using ifplugd daemon. I had setup ifplugd daemon and it seems to work, but now I see that there are some strange problem with DHCP. In case of using network profiles I just set IFOPTS="dhcp" inside profile file in /etc/network-profiles. After move to ifplugd I have commented NET_PROFILES=(menu) inside rc.conf and add lines eth0="dhcp" ath0="dhcp" After this ifplugd brings up eth0 (and ath0) successfully, I can browse internet via local proxy, ping other computers, but I can't ping myself (There are no such problem with network profiles). Output of ifconfig eth0 is identical in both cases - with ifplugd and network-profiles. I suspect following: In case of using network profile I have active only eth0 interface. In case of ifplugd I have: [EMAIL PROTECTED] ~]$ ifconfig ath0 Link encap:Ethernet HWaddr 00:0F:CB:B2:E2:9B inet6 addr: fe80::20f:cbff:feb2:e29b/64 Scope:Link UP BROADCAST 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 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) eth0 Link encap:Ethernet HWaddr 00:0D:9D:90:49:57 inet addr:172.17.9.241 Bcast:172.17.15.255 Mask:255.255.248.0 inet6 addr: fe80::20d:9dff:fe90:4957/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:72004 errors:0 dropped:0 overruns:0 frame:0 TX packets:2227 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:8978660 (8.5 Mb) TX bytes:465974 (455.0 Kb) Interrupt:11 wifi0 Link encap:UNSPEC HWaddr 00-0F-CB-B2-E2-9B-00-00-00-00-00-00-00-00-00-00 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:8462 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:199 RX bytes:0 (0.0 b) TX bytes:414632 (404.9 Kb) Interrupt:10 i.e. ath0 is also present and up. But WiFi antenna is switched off and there are no WiFi network reachable. I suspect that it can cause attempt to reach local address via not active ath0. Could anyone say me how to setup ifplugd in such case to prevent activating ath0 in case of network absence? Thanks in advance. Best regards, Vladislav Titov _______________________________________________ arch mailing list [email protected] http://archlinux.org/mailman/listinfo/arch _______________________________________________ arch mailing list [email protected] http://archlinux.org/mailman/listinfo/arch
