We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

ค้นหาฝ่ายสนับสนุน

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.

เรียนรู้เพิ่มเติม

firefox won't open after checking for add-on updates

  • 2 การตอบกลับ
  • 1 คนมีปัญหานี้
  • 10 ครั้งที่ดู
  • ตอบกลับล่าสุดโดย alan_r

more options

Hi

i am having problems with Add-ons checking for updates. 

The first problem is that in add-on manager, even though i have it set to automatically update add-ons, it has no history of finding any and it's failure to find a new version of a plug-in meant pdfs weren't opening see full details here ... https://support.mozilla.com/en-US/questions/829011

The problem i am now having is that when i manually check for updates in Add-Ons manager, it pauses for a few seconds, and completes it's task by saying it hasn't found anything. If i then close Firefox, i can't open Firefox again until i go into task manager and kill the process. It says it's already running and i have to close it first?!

Hi i am having problems with Add-ons checking for updates. The first problem is that in add-on manager, even though i have it set to automatically update add-ons, it has no history of finding any and it's failure to find a new version of a plug-in meant pdfs weren't opening see full details here ... https://support.mozilla.com/en-US/questions/829011 The problem i am now having is that when i manually check for updates in Add-Ons manager, it pauses for a few seconds, and completes it's task by saying it hasn't found anything. If i then close Firefox, i can't open Firefox again until i go into task manager and kill the process. It says it's already running and i have to close it first?!

การตอบกลับทั้งหมด (2)

more options

can't believe that i was the only person to have the problem, but no replies whatsoever suggest i was. have now upgraded to 5.0 where the problem has not yet reoccurred.

more options

Partial answer here(only a few away from this one) -

https://support.mozilla.com/en-US/questions/829011