Description of problem:
Got a firefox update, restarted and the mozilla firefox updated page warned me that I needed a new flash plugin. This surprised me because I update automatically from the Adobe repo. about:plugins showed version 10.0 r22, but I had flash-plugin-10.0.32.18-release.i386 installed. I removed /usr/lib/mozilla/plugins-wrapped/nswrapper_32_32.libflashplayer.so and re-ran mozilla-plugin-config and now I see version 10.0 r32. So, what's going on?
Version-Release number of selected component (if applicable):
Yes, you're right. Although the new plug-in is used an old version is shown...it looks lite the plug-in version is stored in wrapper.
Hm, the fix requires to get those informations directly from the plug-in and it's complicated by fact that the plugin is not initialized yet...
Just check the plug-ins the same way as the extensions (languages, etc.): require a re-start. That is: invoke each plugin "silently", record the version in the necessary place, re-start, check the version of each plugin.
I experienced the same problem with Fedora 12; I currently have nspluginwrapper-1.3.0-10.fc12.i686 installed. A copy of nswrapper_32_32.nppdf.so belonging to Adobe Reader 9.1 was left in place, with a copy of nppdf.so from Adobe Reader 9.3 installed at the same time. This has serious security implications if the older version remains active.
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '11'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 11's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 11 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
With the recent lash plugin update I saw this problem again.
Firefox Plugin Check will warn the user which will get confused because
yum (with friends) says all software is update to date.
A workaround could be to release nspluginwrapper update with post scripts
that refresh the wrapped plugins?
[ I have changed version Fedora 13 too]
Created attachment 427409 [details]
Should fix this issue, compares modification time between wrapped and original plug-in file.
nspluginwrapper-1.3.0-12.fc13 has been submitted as an update for Fedora 13.
*** Bug 608726 has been marked as a duplicate of this bug. ***
nspluginwrapper-1.3.0-12.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
This line of the patch looks bogus:
return(!file && !wrap && file <= wrap);
The "file <= wrap" part is only reached if both "file" and "wrap" are zero. Perhaps it was supposed to be:
return(!file && !wrap && file <= wrap);
Oops, the second time I meant:
return(file && wrap && file <= wrap);
You're right, that's the correct construction.
Created attachment 427900 [details]
nspluginwrapper-1.3.0-13.fc13 has been submitted as an update for Fedora 13.
nspluginwrapper-1.3.0-13.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
Well, I just updated:
$ rpm -qa nspluginwrapper
And I still have the same error messages and still no flash. What now?
(In reply to comment #17)
> Well, I just updated:
> $ rpm -qa nspluginwrapper
> And I still have the same error messages and still no flash. What now?
Please file a new bug for it with some closer description.