Your message dated Thu, 17 Dec 2015 19:41:38 +0000
with message-id <20151217194138.ga24...@master.debian.org>
and subject line flashplugin-nonfree: Downloaded and installed flashplugin is
not picked up by browsers
has caused the Debian Bug report #803597,
regarding flashplugin-nonfree: Downloaded and installed flashplugin is not
picked up by browsers
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
803597: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803597
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: flashplugin-nonfree
Version: 1:3.6.1+b1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
When installing flashplugin-nonfree neither Iceweasel nor Chromium will list
the plugin as part of the installed browser plugins, and neither browser will
be able to play any flash content on sites that make use of it. For Iceweasel
this can be worked around by creating a 'symlink' to help the browser out, for
chromium I have not yet found the right/magic symlink path (or it may not be as
simple).
The flashplugin-nonfree package provides an 'alternative' for:
/usr/lib/mozilla/plugins/flash-mozilla.so
Which points into the /etc/alternatives tree and ultimately the chain leads to
/usr/lib/flashplugin-nonfree/libflashplayer.so
Unfortunately, while this setup enables the use of 'alternative'
implementations of libflashplayer.so, it also means that by
default the user must manually create symlinks in the /usr/lib hierarchy. So,
by default the flash player plugin does not
actually 'work' out of the 'box' when flashplugin-nonfree is installed --
making this package unusable by default.
This is because browsers do not look for a 'flash-mozilla' but for a
'libflashplayer' library.
One can fix this manually for Iceweasel/Firefox by creating a symlink at
/usr/lib/firefox-addons/plugins/libflashplayer.so
pointing to /usr/lib/mozilla/plugins/flash-mozilla.so
Presumably there ought to be a similar workaround for Chromium but so far I
have been unable to find one that works.
Please consider redesigning the set of symlinks installed to make sure that the
libflashplayer.so is found by browsers looking for it (as libflashplayer.so),
or at least clarify that the user must manually create necessary symlinks in
/usr/lib themselves during installation.
-- System Information:
Debian Release: stretch/sid
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
For Chromium, see pepperflashplugin-nonfree instead. For Iceweasel, the parts
"by default the user must manually create symlinks" and further reasoning are
not correct. I just tested again on jessie and stretch: works out of the box.
--- End Message ---
