Bug 181300 - www-client/opera-9.21: Wrong directory for netscape plugins specified (Plug-in path)
|
Bug#:
181300
|
Product: Gentoo Linux
|
Version: 2006.1
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: minor
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: jer@gentoo.org
|
Reported By: askwar@digitalprojects.com
|
|
Component: Ebuilds
|
|
|
URL:
|
|
Summary: www-client/opera-9.21: Wrong directory for netscape plugins specified (Plug-in path)
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2007-06-08 13:10 0000
|
In a freshly created profile of Opera 9.21 on a ~x86 installation, the plug-in
path has this value:
/opt/opera/lib/opera/plugins:/opt/netscape/plugins
In those directories, there are close to no plugins. It seems, that plugins for
"Mozilla" are "nowadays" installed in /usr/lib/nsbrowser/plugins. That's also
the directory which is set by the mozilla-launcher script:
--($:~)-- cat /usr/bin/firefox
#!/bin/sh
#
# Stub script to run mozilla-launcher. We used to use a symlink here
# but OOo brokenness makes it necessary to use a stub instead:
# http://bugs.gentoo.org/show_bug.cgi?id=78890
export MOZILLA_LAUNCHER=firefox
export MOZILLA_LIBDIR=/usr/lib/mozilla-firefox
export MOZ_PLUGIN_PATH=${MOZ_PLUGIN_PATH:-/usr/lib/nsbrowser/plugins}
exec /usr/libexec/mozilla-launcher "$@"
It would be better, if the preset value for the plug-in path for opera would
also include /usr/lib/nsbrowser/plugins, so that Opera picks up all the plugins
that are available to "Mozilla" as well.
--($:~)-- emerge --info
Portage 2.1.2.9 (default-linux/x86/2006.1/desktop, gcc-4.1.2, glibc-2.5-r3,
2.6.21-gentoo-r2.rtr.05-no-sched_smt.kernel-alsa i686)
=================================================================
System uname: 2.6.21-gentoo-r2.rtr.05-no-sched_smt.kernel-alsa i686 Genuine
Intel(R) CPU T2400 @ 1.83GHz
Gentoo Base System release 1.12.10
Timestamp of tree: Fri, 08 Jun 2007 05:20:01 +0000
distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632)
[disabled]
ccache version 2.4 [enabled]
dev-java/java-config: 1.3.7, 2.0.33-r1
dev-lang/python: 2.4.4-r4
dev-python/pycrypto: 2.0.1-r5
dev-util/ccache: 2.4-r7
sys-apps/sandbox: 1.2.18.1
sys-devel/autoconf: 2.13, 2.61
sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10
sys-devel/binutils: 2.17
sys-devel/gcc-config: 1.3.16
sys-devel/libtool: 1.5.23b
virtual/os-headers: 2.6.21
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-march=pentium-m -O2 -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config
/usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config"
CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf
/etc/php/apache1-php5/ext-active/ /etc/php/apache2-php5/ext-active/
/etc/php/cgi-php5/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild
/etc/terminfo"
CXXFLAGS="-march=pentium-m -O2 -pipe -fomit-frame-pointer"
DISTDIR="/Gentoo/Portage/distfiles"
EMERGE_DEFAULT_OPTS="--alphabetical"
FEATURES="ccache collision-protect distlocks metadata-transfer sandbox sfperms
strict"
GENTOO_MIRRORS=" http://ftp.heanet.ie/pub/gentoo/
http://gentoo.supp.name/
http://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ http://ftp.gentoo.or.kr/
http://ftp.uni-erlangen.de/pub/mirrors/gentoo/
http://distfiles.gentoo.org/ "
LANG="de_CH.UTF-8"
LDFLAGS="-Wl,-O1"
LINGUAS="de"
MAKEOPTS="-j3"
PKGDIR="/Gentoo/Portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress
--force --whole-file --delete --delete-after --stats --timeout=180
--exclude=/distfiles --exclude=/local --exclude=/packages
--filter=H_**/files/digest-*"
PORTAGE_TMPDIR="/Gentoo/Portage/build"
PORTDIR="/Gentoo/Portage/tree"
PORTDIR_OVERLAY="/Gentoo/Portage/local-tree/misc"
SYNC="rsync://winds03:10873/gentoo-portage"
USE="X acpi alsa berkdb bitmap-fonts cairo cdr cli cracklib crypt cups dbus dmi
dri dvd dvdr eds emboss encode fam firefox fortran gdbm gif gnome gpm gstreamer
gtk hal iconv isdnlog jpeg kde kdeenablefinal kdehiddenvisibility ldap libg++
libnotify mad midi mikmod mmx mp3 mpeg mudflap ncurses nls nptl nptlonly ogg
opengl openmp pam pcmcia pcre perl png ppds pppd python qt3 qt4 quicktime
readline reflection samba sdl session spell spl ssl tcpd truetype
truetype-fonts type1-fonts unicode vorbis wifi win32codecs x86 xine xinerama
xml xorg xv zlib" ALSA_CARDS="dummy hda-intel intel8x0 intel8x0m usb-audio
usb-usx3y" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty
extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null
plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="evdev keyboard
mouse synaptics vmmouse" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633
glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="de" USERLAND="GNU"
VIDEO_CARDS="dummy none nv nvidia vga"
Unset: CTARGET, INSTALL_MASK, LC_ALL, PORTAGE_COMPRESS,
PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
To me it looks like everything in /usr/lib/nsbrowser/plugins/ is a symlink to a
plugin in /opt/netscape/plugins/:
# ls -l /usr/lib/nsbrowser/plugins/
total 96
lrwxrwxrwx 1 root root 37 2007-01-20 04:57 flashplayer.xpt ->
/opt/netscape/plugins/flashplayer.xpt
lrwxrwxrwx 1 root root 29 2007-04-26 01:59 gxineplugin.so ->
/usr/lib/gxine/gxineplugin.so
lrwxrwxrwx 1 root root 72 2006-09-02 18:33 javaplugin.so ->
/opt/blackdown-jdk-1.4.2.03/jre/plugin/i386/mozilla/libjavaplugin_oji.so
lrwxrwxrwx 1 root root 39 2007-01-20 04:57 libflashplayer.so ->
/opt/netscape/plugins/libflashplayer.so
-rwxr-xr-x 1 root root 1122 2007-04-26 03:25 libvlcplugin.la
-rwxr-xr-x 1 root root 93540 2007-04-26 03:25 libvlcplugin.so
lrwxrwxrwx 1 root root 42 2007-03-15 05:50 mplayerplug-in-qt.so ->
/opt/netscape/plugins/mplayerplug-in-qt.so
lrwxrwxrwx 1 root root 43 2007-03-15 05:50 mplayerplug-in-qt.xpt ->
/opt/netscape/plugins/mplayerplug-in-qt.xpt
lrwxrwxrwx 1 root root 39 2007-03-15 05:50 mplayerplug-in.so ->
/opt/netscape/plugins/mplayerplug-in.so
lrwxrwxrwx 1 root root 40 2007-03-15 05:50 mplayerplug-in.xpt ->
/opt/netscape/plugins/mplayerplug-in.xpt
lrwxrwxrwx 1 root root 32 2007-02-06 07:29 nphelix.so ->
/opt/netscape/plugins/nphelix.so
lrwxrwxrwx 1 root root 33 2007-02-06 07:29 nphelix.xpt ->
/opt/netscape/plugins/nphelix.xpt
Mozilla Team: Which is the correct path to use?
(In reply to comment #1)
> To me it looks like everything in /usr/lib/nsbrowser/plugins/ is a symlink to a
> plugin in /opt/netscape/plugins/:
Not so on my systems:
ls -l /usr/lib/nsbrowser/pluginsalexander@blattli ~ $ ls -l
/usr/lib/nsbrowser/plugins
insgesamt 520
lrwxrwxrwx 1 root root 37 19. Mar 18:07 flashplayer.xpt ->
/opt/netscape/plugins/flashplayer.xpt
lrwxrwxrwx 1 root root 29 18. Mar 20:30 gxineplugin.so ->
/usr/lib/gxine/gxineplugin.so
lrwxrwxrwx 1 root root 60 20. Apr 19:54 javaplugin.so ->
//usr/share/java-config-2/nsplugin/sun-jdk-1.6-javaplugin.so
lrwxrwxrwx 1 root root 39 19. Mar 18:07 libflashplayer.so ->
/opt/netscape/plugins/libflashplayer.so
-rw-r--r-- 1 root root 42186 17. Mar 20:11 libtotem-basic-plugin.a
-rwxr-xr-x 1 root root 1360 17. Mar 20:11 libtotem-basic-plugin.la
-rwxr-xr-x 1 root root 28548 17. Mar 20:11 libtotem-basic-plugin.so
-rw-r--r-- 1 root root 167 17. Mar 20:11 libtotem-basic-plugin.xpt
-rw-r--r-- 1 root root 42114 17. Mar 20:11 libtotem-complex-plugin.a
-rwxr-xr-x 1 root root 1374 17. Mar 20:11 libtotem-complex-plugin.la
-rwxr-xr-x 1 root root 28452 17. Mar 20:11 libtotem-complex-plugin.so
-rw-r--r-- 1 root root 180 17. Mar 20:11 libtotem-complex-plugin.xpt
-rw-r--r-- 1 root root 46542 17. Mar 20:11 libtotem-gmp-plugin.a
-rwxr-xr-x 1 root root 1346 17. Mar 20:11 libtotem-gmp-plugin.la
-rwxr-xr-x 1 root root 29576 17. Mar 20:11 libtotem-gmp-plugin.so
-rw-r--r-- 1 root root 238 17. Mar 20:11 libtotem-gmp-plugin.xpt
-rw-r--r-- 1 root root 42142 17. Mar 20:11 libtotem-mully-plugin.a
-rwxr-xr-x 1 root root 1286 17. Mar 20:11 libtotem-mully-plugin.la
-rwxr-xr-x 1 root root 28340 17. Mar 20:11 libtotem-mully-plugin.so
-rw-r--r-- 1 root root 167 17. Mar 20:11 libtotem-mully-plugin.xpt
-rw-r--r-- 1 root root 42098 17. Mar 20:11 libtotem-narrowspace-plugin.a
-rwxr-xr-x 1 root root 1402 17. Mar 20:11 libtotem-narrowspace-plugin.la
-rwxr-xr-x 1 root root 28420 17. Mar 20:11 libtotem-narrowspace-plugin.so
-rw-r--r-- 1 root root 173 17. Mar 20:11 libtotem-narrowspace-plugin.xpt
-rwxr-xr-x 1 root root 1124 20. Apr 08:48 libvlcplugin.la
-rwxr-xr-x 1 root root 99128 20. Apr 08:48 libvlcplugin.so
lrwxrwxrwx 1 root root 32 18. Mar 18:04 nphelix.so ->
/opt/netscape/plugins/nphelix.so
lrwxrwxrwx 1 root root 33 18. Mar 18:04 nphelix.xpt ->
/opt/netscape/plugins/nphelix.xpt
> Mozilla Team: Which is the correct path to use?
Good question. And when you decide, please inform also all the other teams,
which have packages which have nsplugins. Eg. Java, VLC, Totem, ....
However, having a look at mozilla-launcher, it seems as if the /usr path is the
one favored.
www-client/opera-9.21-r1 applies a simple patch to add
/usr/lib/nsbrowser/plugins
to the site wide pluginpath.ini. That seems to work for me, so please test this
new ebuild and reopen this bug if you find the problem has not been properly
solved.
the file "opera-9.12-pluginpath.patch" fails on g/fbsd:
>>> Emerging (1 of 1) www-client/opera-9.23 to /
* opera-9.23-20070809.4-shared-qt.i386.freebsd-en.tar.bz2 RMD160 ;-) ...
[ ok ] * opera-9.23-20070809.4-shared-qt.i386.freebsd-en.tar.bz2
SHA1 ;-) ...
[ ok ] *
opera-9.23-20070809.4-shared-qt.i386.freebsd-en.tar.bz2 SHA256 ;-) ...
[ ok ] * opera-9.23-20070809.4-shared-qt.i386.freebsd-en.tar.bz2 size
;-) ...
[ ok ] * checking ebuild checksums ;-) ...
[ ok ] * checking auxfile
checksums ;-) ...
[ ok ]
* checking miscfile checksums ;-) ...
[ ok ] * checking
opera-9.23-20070809.4-shared-qt.i386.freebsd-en.tar.bz2 ;-) ...
[ ok ] >>> Unpacking source...
>>> Unpacking opera-9.23-20070809.4-shared-qt.i386.freebsd-en.tar.bz2 to /var/tmp/portage/www-client/opera-9.23/work
* Applying opera-9.00-install.patch ...
[ ok ] * Applying opera-9.21-pluginpath.patch ...
* Failed Patch: opera-9.21-pluginpath.patch !
* ( /usr/portage/www-client/opera/files/opera-9.21-pluginpath.patch )
*
* Include in your bugreport the contents of:
*
*
/var/tmp/portage/www-client/opera-9.23/temp/opera-9.21-pluginpath.patch-25328.out
*
* ERROR: www-client/opera-9.23 failed.
* Call stack:
* ebuild.sh, line 1654: Called dyn_unpack
* ebuild.sh, line 768: Called qa_call 'src_unpack'
* ebuild.sh, line 44: Called src_unpack
* opera-9.23.ebuild, line 63: Called epatch
'/usr/portage/www-client/opera/files/opera-9.21-pluginpath.patch'
* eutils.eclass, line 304: Called die
*
* Failed Patch: opera-9.21-pluginpath.patch!
* If you need support, post the topmost build error, and the call stack if
relevant.
* A complete build log is located at
'/var/tmp/portage/www-client/opera-9.23/temp/build.log'.
this happen because the file "ini/pluginpath.ini" seem to be different from the
one provided by the i386 tarball. i do not know why the opera-freebsd tarball
provide a different pluginpath.ini and sound me very strange.
to fix the issue we need to provide a different pluginpath patchset for freebsd
(to add /usr/lib/nsbrowser/plugins=1) and skip the patchset for i386. the
freebsd pluginpath.ini do not have the voice: /opt/netscape/plugins=1, so we do
not need to apply: /opt/netscape/plugins=2.
attached there are the ebuild patch and the pluginpath fix for g/fbsd.
Er, so basically >=www-client/opera-9.21 never emerged on x86-fbsd in the first
place? Hurrah for QA! :)
Fixed in CVS without a revision bump.
*****
Please file a new bug next time so as to not disturb all the people who
happened to be CC'd on the old bug. To make that easier, you can use the "Clone
This Bug" link, choose a new "product" and enter a proper summary and
description for the new bug, along with some relevant CCs.
*****
(In reply to comment #7)
> Er, so basically >=www-client/opera-9.21 never emerged on x86-fbsd in the first place? Hurrah for QA! :)
ehm, yes exactly :)
> *****
> Please file a new bug next time so as to not disturb all the people who
> happened to be CC'd on the old bug. To make that easier, you can use the "Clone
> This Bug" link, choose a new "product" and enter a proper summary and
> description for the new bug, along with some relevant CCs.
> *****
thank you very much for the infos, and sorry for the extra noise.