This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

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

Èròjà atẹ̀lélànà yii ni a ti fi pamọ́ fọ́jọ́ pípẹ́. Jọ̀wọ́ béèrè ìbéèrè titun bí o bá nílò ìrànwọ́.

Why can't I set Flash to Always Activate suddenly in Firefox 36 beta 6?

  • 3 àwọn èsì
  • 30 ní àwọn ìṣòro yìí
  • 5 views
  • Èsì tí ó kẹ́hìn lọ́wọ́ SantaFe

more options

I am running Xubuntu 14.10. As you know, Adobe is no longer offering Flash upgrades past 11.2.202.xxx, only security updates. Thus Flash is always being marked as needing to be updated. Now up to Firefox 36 beta 5, it allowed me to set always activate in the plugins section of Add-Ons. Now however, it won't let me do this & my only options are never activate or ask to activate. It is a pain in the butt to always have to say yes, and while I DO click on the Activate & remember button, some sites still pop that up from time to time.

I must also point out Firefox 35.0.1 works correctly & let's me set it to Always activate. Is this gonna be permanent, or is it temporary? And is there any way perchance Mozilla could lean on Adobe to do for Mozilla like it's doing for Google Chrome with it's pepper-flash, which works in Linux as well as windows? ;)

Okay, I know the last question is probably impossible, but had to ask.

Thanks for any help you might have to offer.

I am running Xubuntu 14.10. As you know, Adobe is no longer offering Flash upgrades past 11.2.202.xxx, only security updates. Thus Flash is always being marked as needing to be updated. Now up to Firefox 36 beta 5, it allowed me to set always activate in the plugins section of Add-Ons. Now however, it won't let me do this & my only options are never activate or ask to activate. It is a pain in the butt to always have to say yes, and while I DO click on the Activate & remember button, some sites still pop that up from time to time. I must also point out Firefox 35.0.1 works correctly & let's me set it to Always activate. Is this gonna be permanent, or is it temporary? And is there any way perchance Mozilla could lean on Adobe to do for Mozilla like it's doing for Google Chrome with it's pepper-flash, which works in Linux as well as windows? ;) Okay, I know the last question is probably impossible, but had to ask. Thanks for any help you might have to offer.

Ọ̀nà àbáyọ tí a yàn

If you run the latest Flash 11.2.202.442 version for Linux then you can ignore this. I don't think that the plugin check website takes the Linux OS into account, but merely checks the version number.

Ka ìdáhùn ni ìṣètò kíkà 👍 1

All Replies (3)

more options

Ọ̀nà àbáyọ Tí a Yàn

If you run the latest Flash 11.2.202.442 version for Linux then you can ignore this. I don't think that the plugin check website takes the Linux OS into account, but merely checks the version number.

more options

It's not the check for updates page, it's the plugins page in Add-Ons where it shows you what plugins you have installed. Like in the picture, I can have it set to Ask to activate, as it is right now, but the Always activate option is gone, so it's either ask or not. ;)

Firefox 36 beta 5 still works, as does Firefox 35.0.1. I thought maybe something went wrong when I compiled it so I downloaded the official Firefox 36 beta 6 & tried it. Same problem. Tried restarting in safe mode, same thing. 36 beta 6 won't let me set it to always activate, Firefox 35.0.1 will.

more options

Okay, it turned out to be a bad profile. I renamed my .mozilla folder to .mozilla-BU and let Firefox beta make a new one & re-installed all my extensions & themes and now it's letting me set it to always activate. ;)

Still can't figure out why it was working with the current 35.0.1 but messing up on 36 beta 6 though. Seems if you were using the same profile on both browsers that both would have the same results. Oh Well. It's solved now, so thanks for the help. ;)