Gnome really slow.. takes 30sec to start terminal..

jinn · 2006-11-09 19:38:09

I just recently had my friend try out arch, from ubuntu as he crasched his whole system in doing a dist upgrade, and convinced him that arch rules..
He wined alot at first, of course did not want to realize facts that he was wrong and i was right, and as days passed by he slowly admitted that arch is better.

But just now, sometimes it takes 20-30 seconds when running gnome 2.16 current to start xterm, or any other program for that matter. there is no hdd or cpu activity 25 seconds, and the last 1 second when starting the program you see cpu & hdd activity.

Reading the forums suggestions were to fix the hosts file and local loopback, which have not helped other ppl, nor my friend.

my guess is:
After thinking some while, he told me it could be something with the network, as it mostly happened when he would suspend to ram the laptop and come to school, and run it (using wifi-radar with profiles for school and home).
Gnome 2.16 wants to connect to old profile settings.. and deadlocks the whole system somehow for about 20secs ..

My other guess is something with dhcpcd, if he installs dhcclient instead, will it work with arch smoothly? I mean is arch configured for dhcpcd specifically or is it replacable without hacking around to much in arch config files.

Others seems to have this problem also, those with experience let us know what you think the problem could be, or if you also get problems after suspending and changing wifi profile.

cactus · 2006-11-09 19:48:59

have him append his machine's hostname to the loopback address line in /etc/hosts.

check to see if when he moves from his home network, to his campus network..if dhcpcd pulls a new hostname from his server or something.

jinn · 2006-11-09 20:33:09

It was as we thought, dhcpcd seems to be running in the background after coming back from suspend and keeps on trying to connect somehow to the old profile, and the 30 second delay is the dhcpcd client timeout.

Setting wifi-radar to use dhclient right now, wondering if it will do better job and not letting the whole system deadlock.

devs should lookup on this. If loosing connection and wanting to dhcpcd back a new ip, I have to manually delete /etc/dhcpc/dhcpcd-wlan0.pid to be able to get dhcpcd running, this is probably the cause.

Btw, why does arch use dhcpcd instead of dhclient?

karsten · 2007-01-08 03:09:24

cactus wrote:

have him append his machine's hostname to the loopback address line in /etc/hosts.
check to see if when he moves from his home network, to his campus network..if dhcpcd pulls a new hostname from his server or something.

this worked for me, had the same problem, thanks

quetzyg · 2007-02-01 11:20:54

Same here, thanks a lot!

Arch Linux

#1 2006-11-09 19:38:09

Gnome really slow.. takes 30sec to start terminal..

#2 2006-11-09 19:48:59

Re: Gnome really slow.. takes 30sec to start terminal..

#3 2006-11-09 20:33:09

Re: Gnome really slow.. takes 30sec to start terminal..

#4 2007-01-08 03:09:24

Re: Gnome really slow.. takes 30sec to start terminal..

#5 2007-02-01 11:20:54

Re: Gnome really slow.. takes 30sec to start terminal..

Board footer