Ko tenda hembiapoite sa’ivéta oñemba’apokuévo hese hembiapo porãve hag̃ua. Peteĩ jehaipyre nomoĩporãiramo ne apañuái ha eporanduséramo, roguerekohína ore nepytyvõ rekoha ikatútava ndeykeko @FirefoxSupport Twitter-pe ha avei /r/firefox Reddit-pe.

Avatar for Username

Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

Ko téma oñeñongatúma. Ejapo porandu pyahu eikotevẽramo pytyvõ.

Shockwave Player shown as vulnerable but updated 3X & Flash Player up to date.

  • 1 Mbohovái
  • 2 oguereko ko apañuãi
  • 21 Hecha
  • Mbohovái ipaháva teeter

teeter
teeter
more options

Plugin Status loaded in Firefox. It showed both Adobe Flash Player and Adobe Shockwave Player as vulnerable. Updating Adobe Flasy Player to Shockwave Flash 22.0.0.292 seemed to work and show it uptodate but Adobe Shockwave Player remained vulnerable. I keep going to the link to update Adobe Shockwave Player, but after I do I still get the vulnerable designation (after refreshing). I have tried to uninstall and reinstall. I have restarted Firefox, although it doesn't say I need to. I'm wondering if this is a problem that Adobe changed the name. Or that the two are synonymous now. Martha Teeter

Plugin Status loaded in Firefox. It showed both Adobe Flash Player and Adobe Shockwave Player as vulnerable. Updating Adobe Flasy Player to Shockwave Flash 22.0.0.292 seemed to work and show it uptodate but Adobe Shockwave Player remained vulnerable. I keep going to the link to update Adobe Shockwave Player, but after I do I still get the vulnerable designation (after refreshing). I have tried to uninstall and reinstall. I have restarted Firefox, although it doesn't say I need to. I'm wondering if this is a problem that Adobe changed the name. Or that the two are synonymous now. Martha Teeter
Mba’erechaha japyhypyre oñondivegua

Opaite Mbohovái (1)

teeter
teeter Porandu apoha
more options

I meant 22.0.0.192. Well in looking for support, I refreshed Firefox. And now the problem seems to have disappeared. No vulnerable Adobe Shockwave Flash.