On Fri, Aug 18, 2006 at 10:21:57AM -0400, Thomas Bushnell BSG <[EMAIL PROTECTED]> wrote: > Mike Hommey <[EMAIL PROTECTED]> writes: > > > On Fri, Aug 18, 2006 at 07:55:13AM +0200, Mike Hommey <[EMAIL PROTECTED]> > > wrote: > >> Can you check at the about:config url that the javascript.enabled > >> preference is set to true ? > > > > I can confirm that disabling javascript does what you describe. Now the > > question is: what did you do to disable javascript ? Upgrade of the > > xulrunner packages can't be responsible for that (it is defined to true > > in /usr/lib/xulrunner/greprefs/all.js). Are you sure you didn't disable > > javascript from the epiphany/galeon UI ? > > I did not do anything to disable javascript, and I have confirmed that > with both galeon and epiphany the UI reports that Javascript is > enabled. > > It was the Debian galeon and epiphany maintainers who thought the bug > was in xulrunner. It does seem to be timed with your recent upload as > well, lending further credence to that claim. > > Moreover, it occurs with two entirely separate browsers that use > xulrunner and not with any that don't. > > Have you attempted to reproduce this on powerpc? Perhaps it is > architecture dependent.
I would have if I had one... I'll probably ask some DSA to install galeon on bruckner when I'll have some more time to debug this issue. Could you try with firefox 1.5.0.6 ? The codebase is the exact same, it shouldn't have a different behaviour. If it does work in firefox, can you try to overwrite /usr/lib/libmozjs.so.0d with /usr/lib/firefox/libmozjs.so and see what happens ? Thanks Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
