Re: [PATCH] Don't force gtkmozembed in the Facebook module

["Chris Rivera" <chrismrivera gmail com>]

On Mon, Mar 17, 2008 at 3:32 PM, John Stowers <john stowers gmail com> wrote:

Hmm, thats a weird combination of things working/not working. The only time I have seen something similar to what you describe is when I had ff3 and ff2 both installed and it would find the wrong run-mozilla.sh script, or something like that, I dont remember exactly.

Im sorry I cant be of more help tracking this down. If conduit works on your distribution without the wrapper script then the packagers are welcome to remove the wrapper, like I am going to recommend is done in ubuntu 8.04 conduit package -it seems to be no longer needed with ff3/gecko 1.9

The problem was that run-mozilla.sh was setting LD_LIBRARY_PATH to /usr/lib/firefox.  This was causing a crash in libxpcom, which is also shipped as part of xulrunner.  If I avoid the run-mozilla.sh script and set MOZILLA_FIVE_HOME to the xulrunner installation then the libxpcom shared libraries shipped with xulrunner are used and everything works correctly.  I would assume that since our (Novell) gtkmozembed package requires xulrunner and not firefox these are the correct versions of the libxpcom libraries to use.

I changed our conduit package to look for the xulrunner installation and set MOZILLA_FIVE_HOME instead of running conduit with run-mozilla.sh.

Whether you go with this change or not, the path in the conduit wrapper (currently FF_PATH) should probably begin with '/usr/lib*' instead of '/usr/lib'.  The current FF_PATH doesn't work for us on 64-bit systems.  I'm not sure how other distros package Firefox on 64-bit platforms though.  Thoughts?

Chris