Re: [Nautilus-list] Problem with Nautilus Mozilla binding

[Brian Cameron <Brian Cameron ireland sun com>]

Nautilus Gurus:

It turns out that we discovered the following about the problem I reported
last Tuesday:

1. Nautilus requires a version of Mozilla that is later than Milestone
   18.  We were able to get the Nautilus/Mozilla bindings working using
   a build of Mozilla that was build on January 23rd.  We didn't realize
   Nautilus required a version of Mozilla more recent than Milestone 18
   until this week.
   
2. The version of Mozilla that we are using is built by a different team
   within Sun and they are building it using different versions of the
   dependant libraries (specifically glib/gtk/ORBit).  We were only
   able to get the Nautilus/Mozilla binding to work if the 
   nautilus-mozilla-content-view program is run with LD_LIBRARY_PATH
   set first to the library directory of Mozilla and then the library
   directory of Gnome.  We have a more elegant solution to this using
   the "-R" link option underway, but we know that this resolves the
   problem.
   
Anyway, after getting the above two issues resolved, Nautilus is looking
much better.

Thanks again!

Brian

> > I am running a build of Nautilus 0.8.1 built with Mozilla milestone 18
> > and running on Solaris 8.
> > 
> > I am launching the Nautilus Mozilla integration by following these steps:
> > 
> >  + When Nautilus comes up I am clicking on the "Help" tab in the
> >    left-hand area of the screen.
> >  + Then I click on "Applications->bug-buddy", although clicking on any
> >    help entry seems to have the same behavior.
> > 
> > Then the output listed in the attachment "nautilus.errors" is displayed
> > on the screen where nautilus was launched, and as this is happening the
> > main section of the Nautilus screen greys out.   Finally the program
> > hangs.  The throbber and the list of "Help" sections remain active, but
> > the rest of Nautilus stops responding to any activity.
> > 
> > I have also attached a stack trace of the "nautilus" process generated
> > by the "ptrace" program.  It seems to indicate that thread #1 Nautilus
> > is trying to receive a reply.  Lastly, I have attached a stack trace
> > of the "nautilus-mozilla-content-view" process which seems to be
> > likewise hung.  I believe this is the process that is trying to
> > talk to the "nautilus" process.  It seems to be hung in a method
> > nsAppShell::DispatchNativeEvent, called by GtkMozEmbedPrivate::LoadChrome().
> > 
> > I am working with debug compiles of both Mozilla and Nautilus, and been
> > using gdb to trace through the code (with help from the "Debugging Mozilla
> > on Linux FAQ"):
> > 
> >    http://www.mozilla.org/unix/debugging-faq.html
> > 
> > However, I am not quite familiar enough with the code to know where to
> > look from here, so any tips, workarounds, or information regarding
> > how to further diagnose or debug this situation would be much
> > appreciated.
> > 
> > Thanks!
> > 
> > Brian Cameron
> >