"Check for updates" tells me there is no update available for 3.6.8.
On Thursday, I did a "Check for Updates" from my dev box and found there was an update. Since I was in the middle of something, I decided I would wait until done to install the update. Many hours later, I was ready and did "Check for Updates" again. This time I got "No updates found". So, I did some searching to make sure there was indeed a 3.6.9 update released, restarted the browser (still no update found), then rebooted the computer (still no update found), tried "Check for Updates" from a couple different computers on my network (all running 3.6.8) and always get "No Update Found". Checking what appears to be the update service at aus2.mozilla.org leads me to believe "No Updates Found" is the correct response but I know it said there was an update the first time I checked. What happened? Is it possible I'm having a DNS issue and hitting an old update server?
Penyelesaian terpilih
They are investigating crash reports and have disabled the update. Bug 595242 – Please turn off the 3.5.12 and 3.6.9 updates while investigating bug 594699
Baca jawapan ini dalam konteks 👍 1All Replies (5)
There are quite a few reports of this, but I do not know what is causing it. You can download 3.6.9 from http://www.mozilla.com/ and install it on top of your current version.
There is no problem updating Firefox, the problem is just that the Firefox update service is responding to the "Check for Updates" request with a response that says there are no updates available (the xml response that was being sent back on Thursday indicating there was an update is now just coming back as an empty "update" element - <update></update>) . It's probably something pretty simple but only someone with access to the datastore being used by the update service will be able to verify and fix it. The other option (that a lot of people are hitting an old update service because of DNS or other network changes) seems unlikely.
I'm having the same problem but I'm running FF 3.6 ... so it's missed quite a few updates.
Jeff
Penyelesaian Terpilih
They are investigating crash reports and have disabled the update. Bug 595242 – Please turn off the 3.5.12 and 3.6.9 updates while investigating bug 594699
That explains it. Thanks cor-el.