From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830
Description of problem:
The nautilus file manager crashes (or shuts down) when I have connected to the
internet using network device control and I start mozilla. This happens only
when ppp is on, not otherwise. Also, i think it happens when there are more than
1 net accounts (using dialup modem) in 'network device control', but I'm not
sure about this.
After this crash happens, gnome cannot be restarted after logging out, even with
the root account. I have to reboot to restart gnome.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Make a brand new install or redhat linux 8.0 (I used the 'workstation' catagory.
2.Open 'neat' and create two dialup accounts using 56k modem.
3.Make a link to mozilla on the desktop by dragging the icon on the panel to the
3.Dial one of the accounts (try both is the problem can't be reproduced)
4.Open up mozilla using the link created.
Actual Results: Everything on the desktop stops responding, the panel and the
menu work though.
Expected Results: nautilus should have worked properly bhah blah blah
I'm using pentium 4 2A ghz cpu on an SIS chipset, the cpu is overclocked to 2.5
ghz but I also tried this using the default speed (2 ghz)
The Problem only occurs when I have fiddled with the startup services list. I
have disabled all services exept :
I think something disabled is causing the problem. I made a fresh install and
the problem wasn't there before i changed the services.
its got something to do with either atd, iptables or network.
nautilus/ORBit tend to get confused if your hostname changes or your
IP address changes or that kind of thing. Maybe we should file a
gnome.org bug along those lines.
Changing to MoveUpstream keyword instead of GnomeUpstream tracking bug.
sorry about the spam.
Does this still happen in fc3test3?
Red Hat Linux is no longer supported by Red Hat, Inc. If you are still
running Red Hat Linux, you are strongly advised to upgrade to a
current Fedora Core release or Red Hat Enterprise Linux or comparable.
Some information on which option may be right for you is available at
Red Hat apologizes that these issues have not been resolved yet. We do
want to make sure that no important bugs slip through the cracks.
If this issue is still present in a current Fedora Core release, please
open a new bug with the relevant information.
Closing as CANTFIX.