On Fri, Oct 17, 2008 at 10:53:00AM +0200, Erwin Rennert wrote: > On 10/16/2008 08:16 PM, Mike Hommey wrote: >> On Thu, Oct 16, 2008 at 09:42:35AM +0200, Erwin Rennert wrote: >>> On 10/15/2008 08:21 AM, Mike Hommey wrote: (...) >>>> MOZILLA_DISABLE_PLUGINS=1 iceweasel >>> Mike, this is excellent news. Thakns for your effort! >>> >>> Indeed iceweasel still crashes with the plugins but not when they >>> are disabled with this command. >>> >>> Hmm. Now this means that I have somehow overlooked a few plugins >>> (and I was sure I had removed them *all*). >> >> That definitely sounds good news to me :) Could you try to >> investigate which one is responsible for this, so that others could >> try to remove it, too ? >> > > Well, it appears to have been the j2re1.4.2 from blackdown that was > linked to /etc/alternatives/mozilla-javaplugin.so that was linked to > /usr/lib/mozilla/plugins/libjavaplugin.so > > At the same time I had a /usr/lib/iceweasel/plugins/libjavaplugin.so > pointing to /usr/lib/gcj-4.3-90/libgcjwebplugin.so The latter is in > place again but does not appear in the about:plugins list of plugins. > > How come iceweasel still uses plugins in /usr/lib/mozilla/plugins/ ?
Because it's a canonical place to put plugins > And how come it mattered even though I had deactivated java in the > preferences? Because plugins are still loaded even when disabled. That's something that sucks in the mozilla plugins model, and something the MOZILLA_DISABLE_PLUGINS variable we added alleviates. Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
