Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More
This thread was archived. Please ask a new question if you need help.
Archived

Flash flagged as invalid

Firefox
vhradice replied
vhradice
vhradice

I have downloaded and installed the latest version of Flash - 11.2.202.236. When I bring up FF, flash is not in the plugins list. I looked in pluginreg.dat and found the following: [INVALID] /opt/google/talkplugin/libnpgtpo3dautoplugin.so:$ 1324412719000:$ /usr/lib64/flash-plugin/libflashplayer.so:$ 1316114519000:$ Why is the newest version of flash being flagged as Invalid? Is there a troubleshooting log created someplace where I can tell why?

I have downloaded and installed the latest version of Flash - 11.2.202.236. When I bring up FF, flash is not in the plugins list. I looked in pluginreg.dat and found the following: [INVALID] /opt/google/talkplugin/libnpgtpo3dautoplugin.so:$ 1324412719000:$ /usr/lib64/flash-plugin/libflashplayer.so:$ 1316114519000:$ Why is the newest version of flash being flagged as Invalid? Is there a troubleshooting log created someplace where I can tell why?

All Replies (3)

ideato
ideato

Delete the pluginreg.dat file in the profile folder and check it again.

see for more info: Re-initializing the plugins database


thank you

cor-el
cor-el
  • Top 25 Contributor
  • Moderator

That plugin location refers to a 64 bit version (/usr/lib64/).
Firefox is a 32 bit application and needs a link to the 32 bit Flash version.

You can check if there is a Flash plugin in /usu/lib/flash-plugin/
If not then you need to install the 32 bit version.

Modified by cor-el

vhradice
vhradice Question owner

I did some more checking. It seems that at some point, I had downloaded v4 of FF and installed it into a private directory and, over time, that copy got updated to v13. V12 was in the normal path. I deleted my copy and updated the system-wide one and now all works well.

That leaves the question of how to find out why FF flags a plugin as invalid? Is there any FF created log that lists that info?