Your message dated Tue, 3 Jan 2012 09:34:16 +0100
with message-id <[email protected]>
and subject line #620154: not fixed
has caused the Debian Bug report #620154,
regarding chromium: Flash plug-in was blocked, out of date
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 [email protected]
immediately.)
--
620154: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620154
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chromium
Version: 10.0.648.204~r79063-1
Severity: normal
I keep getting a warning that the flash plug-in was blocked. Is there a
workaround for this?
-- System Information:
Debian Release: wheezy/sid
APT prefers oldstable
APT policy: (500, 'oldstable'), (500, 'unstable'), (500, 'testing'), (500,
'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages chromium depends on:
ii chromium-inspect 10.0.648.204~r79063-1 page inspector for the chromium br
ii libasound2 1.0.23-2.1 shared library for ALSA applicatio
ii libbz2-1.0 1.0.5-6 high-quality block-sorting file co
ii libc6 2.11.2-11 Embedded GNU C Library: Shared lib
ii libcairo2 1.10.2-6 The Cairo 2D vector graphics libra
ii libcups2 1.4.6-3 Common UNIX Printing System(tm) -
ii libdbus-1-3 1.4.6-1 simple interprocess messaging syst
ii libdbus-glib-1-2 0.92-1 simple interprocess messaging syst
ii libevent-1.4-2 1.4.13-stable-1 An asynchronous event notification
ii libexpat1 2.0.1-7 XML parsing C library - runtime li
ii libfontconfig1 2.8.0-2.1 generic font configuration library
ii libfreetype6 2.4.4-1 FreeType 2 font engine, shared lib
ii libgcc1 1:4.6.0-1 GCC support library
ii libgconf2-4 2.28.1-6 GNOME configuration database syste
ii libgcrypt11 1.4.6-5 LGPL Crypto library - runtime libr
ii libgdk-pixbuf2.0 2.22.1-1+sid1 GDK Pixbuf library
ii libglib2.0-0 2.28.4-1 The GLib library of C routines
ii libgtk2.0-0 2.24.3-1~sid1 The GTK+ graphical user interface
ii libicu44 4.4.2-2 International Components for Unico
ii libjpeg62 6b1-1 The Independent JPEG Group's JPEG
ii libnspr4-0d 4.8.7-2 NetScape Portable Runtime Library
ii libnss3-1d 3.12.9.with.ckbi.1.82-1 Network Security Service libraries
ii libpango1.0-0 1.28.3-5 Layout and rendering of internatio
ii libpng12-0 1.2.44-2 PNG library - runtime
ii libspeex1 1.2~rc1-1 The Speex codec runtime library
ii libstdc++6 4.6.0-1 The GNU Standard C++ Library v3
ii libvpx0 0.9.6-1 VP8 video codec (shared library)
ii libx11-6 2:1.4.2-1 X11 client-side library
ii libxdamage1 1:1.1.3-1 X11 damaged region extension libra
ii libxext6 2:1.2.0-2 X11 miscellaneous extension librar
ii libxml2 2.7.8.dfsg-2 GNOME XML library
ii libxrender1 1:0.9.6-1 X Rendering Extension client libra
ii libxslt1.1 1.1.26-7 XSLT 1.0 processing library - runt
ii libxss1 1:1.2.1-1 X11 Screen Saver extension library
ii libxtst6 2:1.2.0-1 X11 Testing -- Record extension li
ii xdg-utils 1.1.0~rc1-2 desktop integration utilities from
ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime
chromium recommends no packages.
Versions of packages chromium suggests:
pn chromium-l10n <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
reopen 620154 =
found 620154 16.0.912.63~r113337-1
thanks
Le dimanche, 1 janvier 2012 17.51:59, Giuseppe Iuculano a écrit :
> Version: 16.0.912.63~r113337-1
>
> this should be fixed now, please reopen it if necessary
Hi Giuseppe,
I disagree that #620154 is fixed. As far as I understand it, this bug is about
two things:
a) The flashplugin is blocked even when no upgrade of the version installed by
flashplugin-nonfree is available;
b) The URL that the warning points to is Adobe's, even when the flashplugin
was installed trough flashplugin-nonfree.
I would consider this bug fixed when the warning would hint the user about
running `# update-flashplugin-nonfree --install` instead of pointing to
adobe.com.
Cheers,
OdyX
--- End Message ---