User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0.1) Gecko/20100101 Firefox/6.0.1 Build ID: 20110830092941 Steps to reproduce: Thunderbird 3.1.12 Under the administrator account, selected Help -> Check for Updates. Actual results: Big fancy splashy dialog asking whether I want to update to 6.0. None of the 3 options were for TB 3.1.13. Expected results: The update must be to 3.1.13. TB 6.0 destroyed my .msf index files. See Bug 682588. Also Bug 682721 nee Bug 682731 et seq. The Mozilla Foundation Security Advisory 2011-34 indicates that Thunderbird 3.1.13 fixes the problem: https://www.mozilla.org/security/announce/2011/mfsa2011-34.html Bug 682927 indicates the problem is fixed in the common core product, but doesn't mention TB 3.1.13.
Severity: normal → critical
Depends on: 682927
We are a bit late on the 3.1.13 release wait a few more hours (tops 12) and it will be available.
(In reply to william.allen.simpson from comment #0) > The update must be to 3.1.13. TB 6.0 destroyed my .msf index files. See Bug > 682588. Also Bug 682721 nee Bug 682731 et seq. That is a different issue, please don't confuse bugs with multiple issues. > The Mozilla Foundation Security Advisory 2011-34 indicates that Thunderbird > 3.1.13 fixes the problem: > https://www.mozilla.org/security/announce/2011/mfsa2011-34.html Yes, we're working on actively releasing it at the moment, this is a one-off because the issue was already public, we pushed the security announcement out before we had the releases so that the public could know about the issue and where it will be fixed. > Bug 682927 indicates the problem is fixed in the common core product, but > doesn't mention TB 3.1.13. The release notes will have links to that bug, the announcement references it is affected and says it is fixed in 3.1.13. If you really want to check you can compare gecko versions with what it says in that bug.
Status: UNCONFIRMED → NEW
Ever confirmed: true
This is on the update channel now.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.