Oracle Linux 7, FF 68.2 ESR, recent update to Flash 126.96.36.1993, I check in Addons that newest Flash is there (had issues a few weeks ago where I had to remove pluginreg.d…
Oracle Linux 7, FF 68.2 ESR, recent update to Flash 188.8.131.523, I check in Addons that newest Flash is there (had issues a few weeks ago where I had to remove pluginreg.dat as 184.108.40.2060 wouldn't get noticed and FF thought it was 220.127.116.11 still, complaining I had an out-of-date version), and surprise - both Flash and IcedTea aren't there.
So I confidently close FF, remove pluginreg.dat, fire FF up again - but no dice.
Check contents of pluginreg.dat, and here they are:
Generated File. Do not edit.
[HEADER] Version:0.19t:$ Arch:x86_64-gcc3:$
Funny, so I try downgrading Flash via YUM, which can't be done as Adobe promptly removes old versions from its repos. OK, so I just YUM erase Flash, only to achieve an INVALID IcedTea plugin. What?
Did I perhaps use FF 68.2 for 2 weeks without noticing the issue? Well if that's the case a downgrade to 68.1 will fix things, right? So I re-add via YUM the latest Flash plugin, but alas 68.1 still thinks that and IcedTea are INVALID.
Mumble. Well let me get the big hammer and further downgrade to FF 60.9, remove pluginreg.dat, fire FF up again and... oh. Still INVALID. Now I'm 100% sure there's something weird - but what is it?
Long story short, even creating an entirely new UNIX user and firing up FF which obviously created a new profile from scratch, it gets the same pluginreg.dat right off the bat with Flash and IcedTea plugins marked as INVALID.
So, what are the further debugging steps here as I guess I'm out of options?