This bug was forked from bug 47318, which seems likely to have been about a
different issue. In any case, bug 47318 was turning into a long complicated story
with various plot twists that left it impossible to follow. By breaking this out
I think we can achieve more clarity on it. 

cc:ing jsh because the theme problem that Victor mentions may be interesting, or
even the cause of his other problems. I suspect somebody will need to try to
debug this on Victor's machine.

Here's the (trivially edited) report from Victor:
===
I just got [a] bonobo warning and a crash with
the first_branch on RH6.2, and by the way, I had just done a; killall nautilus;
nautilus-clean; run-nautilus. I did not pass the -x argument to nautilus-clean
this time. My system is experiencing some problems with the eazel themes. I
don't know if that has anything to do with the crash and error messages, but I
thought I mentioned it. 
1. Clicked on the My Computer Icon and back arrow
2. Clicked on the Services Icon in the same directory and back arrow
Crash and error message on the console.
victor@vorlon /gnome-source/ONE_BRANCH $ killall nautilus
victor@vorlon /gnome-source/ONE_BRANCH $ nautilus-clean.sh 
nautilus-clean: Stale processes found.
nautilus-adapter:       1
nautilus-throbber:       1
victor@vorlon /gnome-source/ONE_BRANCH $ nautilus-clean.sh 
nautilus-clean: No stale processes found.
victor@vorlon /gnome-source/ONE_BRANCH $ run-nautilus

Gtk-WARNING **: Unable to locate loadable module in module_path:
"libeazel-engine.so",

Gtk-WARNING **: Unable to locate loadable module in module_path:
"libeazel-engine.so",


Bonobo-WARNING **: Exception on unrealize 'Unknown CORBA exception id:
'IDL:CORBA/COMM_FAILURE:1.0''

** WARNING **: A view failed. The UI will handle this with a dialog but this
should be debugged.



------- Additional Comments From mjs@noisehavoc.org 2001-03-08 09:44:10 ----

I can't reproduce this problem. The bug report is not even very clear on what
the problem is.

Victor: is this bug reproducible for you? Can you write up some steps that make
it happen reliably if so? Can you test this on other machines to see if this is
due to your local configuration issue? And what exactly crashed, only the
summary view or all of Nautilus?

Please assign this back to me once you can add some more info. Thanks.




------- Additional Comments From jsh@pixelslut.com 2001-03-08 12:40:20 ----

The eazel-engine error messages shouldn't make any difference (it will fall back
to the default theme. This problem was fixed in a more recent version of the
theme engine)



------- Additional Comments From victor@eazel.com 2001-03-09 09:43:45 ----

Maciej, it was a Nautilus crash, but I'm not able to reproduce this now. Here is
how it failed last time:
Preference set to Beginner (This sets the user home folder to $HOME/Nautilus
I clicked on the computer ICON and then the Back button
I clicked on the Services ICON (the one in the folder), but didn't login
Services; clicked on the Back button again and that all it
took....crash,consolemessages,bugreport...




------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-09-09 21:10 -------

The original owner (victor@eazel.com) of this bug does not have an account here.
Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.