[CLUE-Tech] Sawfish cores (or why is Gnome so borked)?

[Jed S. Baer]

Hi Folks.

Periodically, when I'm feeling insufficiently frustrated I guess, I fire
up the Gnome desktop, just to see if I can find anything to recommend it.
Last time I did, I fiddled with a few minor things, and exited normally.
I've been running Sawfish as the WM for Gnome for quite a while.

But, I've been back in the sane world of Fvwm2 for a bit. But today, I
thought I'd start Gnome and fix a few things, when I noticed some graphic
files in incorrect location (not important) while doing directory
maintenance.

So, Gnome takes a while to fire up, and starts without a WM, with a couple
messages about my panel app as well. I can't reset to Sawfish in the
control center. It times out after 10 seconds. If I open a terminal, and
try to start Sawfish from the command line, it cores. I think it cores
when trying to start it from Gnome, too.

Now, in the mean time, the only Gtk/Gnome things I run are Pan, Sylpheed,
and Galeon. But I've been able to run the Gnome desktop before, after
running these programs.

The problem occurs, now, whether I start Gnome from runlevel 5 or 3.

The only other thing I did was remove ~/Xrootenv.0 -- a file which the
Xserver command files remove, AFAICT, anyway, if you start X in some
certain way. A web search shows Xrootenv.0 as being a "garbage" file
created by AnotherLevel, and I couldn't find any references to it WRT
Sawfish.

I see nothing suggestive in ~/.xsession-errors.

I'm running Gnome 1.4, on a RH7.1 system.

I guess I'll try removing the .sawfish dir tree. Any other thoughts on
what to look for?

TIA.
jed
-- 
"Those who expect to reap the blessings of freedom must, like men,
 undergo the fatigue of supporting it."
 - Thomas Paine