Re: [Galeon-devel] Re: [Galeon-user] java crashing galeon

[J. G. B. <gar...@ho...>]

On Sun, 2002-09-22 at 21:33, Kelledin wrote:
> On Sunday 22 September 2002 08:29 pm, J. Gardner Biggs wrote:
> > Copied from the 1.3.1 dir.
> >
> > > To get more informative debug messages, you should run
> > > galeon from a terminal and see what it spits out.
> >
> > Output of galeon in terminal when it crashes:
> >
> > ** CRITICAL **: file mozilla.cpp: line 134 (gboolean
> > mozilla_preference_set (con
> > st char *, const char *)): assertion `new_value != NULL'
> > failed.
> >
> > ** CRITICAL **: file mozilla.cpp: line 134 (gboolean
> > mozilla_preference_set (con
> > st char *, const char *)): assertion `new_value != NULL'
> > failed.
> >
> > ** CRITICAL **: file mozilla.cpp: line 134 (gboolean
> > mozilla_preference_set (con
> > st char *, const char *)): assertion `new_value != NULL'
> > failed.
> >
> > ** CRITICAL **: file mozilla.cpp: line 134 (gboolean
> > mozilla_preference_set (con
> > st char *, const char *)): assertion `new_value != NULL'
> > failed.
> >
> > ** CRITICAL **: file mozilla.cpp: line 134 (gboolean
> > mozilla_preference_set (con
> > st char *, const char *)): assertion `new_value != NULL'
> > failed.
> >
> > ** CRITICAL **: file mozilla.cpp: line 134 (gboolean
> > mozilla_preference_set (con
> > st char *, const char *)): assertion `new_value != NULL'
> > failed. INTERNAL ERROR on Browser End: Exec of "java_vm"
> > failed: 2 <
> > System error?:: No such file or directory
> > Gdk-ERROR **: Fatal IO error 9 (Bad file descriptor) on X
> > server :0.0. INTERNAL ERROR on Browser End: Could not read ack
> > from browser System error?:: Resource temporarily unavailable
> 
> It needs to be symlinked.  This is the exact problem that comes 
> up when it isn't.  The reason why it comes up like this has to 
> do with the plugin's method of groping for the java_vm 
> executable.
> 

Thanks for the help! now it works.  I was just lazy when the new mozilla
1.0.1 came out a few weeks ago and just copied the symlink into the
/usr/lib/mozilla-1.0.1/plugins dir.  Well of course it didn't copy the
"link" but the actual plugin file.


> When the plugin file is dlopen'd by Galeon/Mozilla, it tries to 
> figure out the location where it originally resided 
> (/opt/java/jre/plugin/i386/ns610/libjavaplugin_oji140.so on my 
> system).  If it's symlinked, it's smart enough to figure that 
> out and trace down its original directory path (the path where 
> it first existed when j2re was installed).  Otherwise it assumes 
> that it's actually sitting in its original path (which is 
> usually wrong, but there's not much else it can do).
> 
> Whatever it decides its original path is, it gropes for the 
> java_vm executable relative to that directory 
> path--"../../../bin/java_vm", to be exact.  That means if you 
> copy the plugin to /usr/lib/mozilla/plugins instead of 
> symlinking it, it expects java_vm to be /usr/bin/java_vm.
> 
> -- 
> Kelledin
> "If a server crashes in a server farm and no one pings it, does 
> it still cost four figures to fix?"
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Galeon-devel mailing list
> Gal...@li...
> https://lists.sourceforge.net/lists/listinfo/galeon-devel
-- 
J. Gardner Biggs <gar...@ho...>