You are not logged in.

#1 2005-04-08 02:28:37

nam1000
Member
Registered: 2005-04-08
Posts: 20

Gnome 2.10 (partial) freeze

I'm running Gnome 2.10, which I think is a very good release. It's been working ok for about a week. Since yesterday menu, panel applets and nautilus refuse to start. No further indication when started from CLI. Could this be due to gnome-session? or dbus/hal?

I don't whether an odd Firefox 1.0.2 freeze is related to this (when adding attachment to email) - this freeze seems to be unique to Arch (not having it on Slackware), and started happening at about the same time than the problem above.

any thoughts on how to fix the problem(s)?

Offline

#2 2005-04-08 04:10:22

nam1000
Member
Registered: 2005-04-08
Posts: 20

Re: Gnome 2.10 (partial) freeze

Nautilus starts again when I kill off dhcpcd; now I've no idea what kind of bug this can be... any help?

Offline

#3 2005-04-08 08:17:42

iphitus
Forum Fellow
From: Melbourne, Australia
Registered: 2004-10-09
Posts: 4,927

Re: Gnome 2.10 (partial) freeze

Make sure that your loopback is being enabled. Check your /etc/rc.conf

Offline

#4 2005-04-10 21:40:39

nam1000
Member
Registered: 2005-04-08
Posts: 20

Re: Gnome 2.10 (partial) freeze

It appears that my loopback interface IS enabled. This is becoming weirder and weirder... still looking anyway.

Offline

#5 2005-04-11 20:26:50

nam1000
Member
Registered: 2005-04-08
Posts: 20

Re: Gnome 2.10 (partial) freeze

I thought my loopback was enabled, but it wasn't (I was fooled by ifconfig's output, which did list "lo", overlooking the fact that the loopkack inet address was missing). This is because I had inadvertedly removed the "network" daemon in rc.conf. It has solved the Gnome problem.

It has also solved the Firefox problem, which was indeed related. There's a post in this forum about Firefox crashing when loopback is missing.

Thanks folks.

Offline

Board footer

Powered by FluxBB