Three Monkeys, Three Typewriters, Two Days

Doesn't work on Ubuntu 5.10 either :(

Pretty sure you just have to add the compat libstdc++ library or something like that. It worked for me :-)

- A

Asa, you have to install the libstdc++ update to a vanilla RedHat 8 in order to get Firefox to even _try_ starting. Then if the update has been installed it tries to start and crashes. We've had a bug open on this since May or June, if you recall.

Asa: do you honestly think the user should have to do that?

[quote]
Doesn't work on Ubuntu 5.10 either :(
[/quote]

Both 1.5 and the nightlies work fine here on Ubuntu 5.10, weird....

In case someone cares, the crash on startup that I get is: http://talkback-public.mozilla.org/talkback/fastfind.jsp?search=2&type=iid&id=12685115

Boris, I reopened bug 187029, which has same stacktrace:
https://bugzilla.mozilla.org/show_bug.cgi?id=187029

Yeah, I saw that bug. Reopening it is probably pretty useless -- no one will ever work on it.

Somehow that rang a bell, because Firefox won't start on my work machine (SuSE 9.3), either, while SeaMonkey does.

Now that I looked at it again I see that it's a different problem, though: https://bugzilla.mozilla.org/show_bug.cgi?id=246313#c33

Try installing/upgrading just GTK+. If you don't want it to affect the rest of the system, compile the new GTK+ stack from the source then use LD_LIBRARY_PATH=/usr/local/lib

This is of course a huge pain in the butt but it'll let you find out if it's hitting a bug in an early GTK2 that was fixed in later versions (this has happened to me before).

Mike, I've tried just upgrading GTK; that really doesn't play nice with other things if I want to use an RPM -- too much stuff has GTK versions hardcoded into their dependencies... The /usr/local idea has the same problem -- RPM won't really let two separate GTK versions hang around, at least that I know of.

That said, my own builds (against GTK2 and all) work fine, both those I build on my own machine and the ones I build on the loaner Fedora Core 3 machine I have. So while this may be a bug in the GTK2 version I have, I'm having a lot of trouble hitting it _except_ with the Mozilla.org Firefox builds.