Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#43724 - [firefox] Flashplugin is not upgraded in firefox

Attached to Project: Arch Linux
Opened by xdmx (xdmx) - Friday, 06 February 2015, 20:24 GMT
Last edited by Evangelos Foutras (foutrelis) - Monday, 23 March 2015, 05:46 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Ionut Biru (wonder)
Evangelos Foutras (foutrelis)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Since flashplugin 11.2.202.440 I've noticed a weird bug, I upgrade it to the last version, but firefox doesn't update it. I've tried to restart firefox and to reboot. The only way it worked was to remove it using pacman and install it again. Now I'm having the same issue with 11.2.202.442
   flash.png (76.5 KiB)
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Monday, 23 March 2015, 05:46 GMT
Reason for closing:  Won't fix
Additional comments about closing:  A search should quickly point to the workaround (removing pluginreg.dat). The issue doesn't seem to occur frequently enough to justify a post upgrade message.
Comment by xdmx (xdmx) - Saturday, 07 February 2015, 10:27 GMT
After some digging I've found out that it's a "known issue" https://wiki.archlinux.org/index.php/Firefox#Firefox_detects_the_wrong_version_of_my_plugin

Could it be a temporary solution adding on the flashplugin pkgbuild a check that if firefox is running then delete ~/.mozilla/firefox/some name.default/pluginreg.dat ?

At least until it's fixed upstream in firefox
Comment by Evangelos Foutras (foutrelis) - Saturday, 07 February 2015, 13:22 GMT
Touching user files is a definite no-no.

Documenting it in the wiki (the link you posted) and waiting for an upstream fix is the way to go.

We could, however, also add a post upgrade message to flashplugin that warns about this issue.
Comment by xdmx (xdmx) - Saturday, 07 February 2015, 17:12 GMT
The post upgrade message seems a good option

Loading...