Installing totem-2.16.1 with USE="-nsplugin", still causes the plugins to get written to /usr/lib/nsbrowser/plugins. From a recent compilation: ./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-vanity --disable-gtk --with-dbus --with-hal --enable-nautilus --disable-lirc --disable-nvtv --disable-mozilla --enable-gstreamer=yes MOZILLA_PLUGINDIR=/usr/lib/nsbrowser --disable-gtk-doc --build=i686-pc-linux-gnu checking for a BSD-compatible install... /bin/install -c during the configure phase, the following showed up: checking whether to compile the browser plugins... autodetect checking which gecko to use... firefox checking for MOZILLA_NOT_LINKED... yes checking for BROWSER_PLUGIN... yes checking for DBUS... yes checking for dbus-binding-tool... /usr/bin/dbus-binding-tool checking for xpidl... /usr/lib/mozilla-firefox/xpidl checking for xpt_link... /usr/lib/mozilla-firefox/xpt_link checking whether to enable the basic browser plugin... yes checking whether to enable the GMP browser plugin... yes checking whether to enable the Complex browser plugin... yes checking whether to enable the NarrowSpace browser plugin... yes checking whether to enable the MullY browser plugin... yes Which shows that ./configure is ignoring the --disable-mozilla flag. A quick check in the configure script shows that the real flag checked is --enable/disable-browser-plugins. It's not clear whether this affects the --with-mozilla=seamonkey/firefox or not. ./configure --help still reports the --enable/disable-mozilla flags, so there's an upstream bug in here somewhere at least... Assigning to bug-wranglers because I'm not sure whether this falls under the gnome or video herd, sorry...
Same problem here. This is not cool. :( Totem plugins suck! They crash Firefox. Must be deleted. As a side note... can I not use the plugins for some Firefox profiles and not use them for others? or block them for some sites?
Aye, indeed it does not. Sorry for the delay in addressing this bug. It has been fixed with 2.16.2-r1.
