unable launch release version 78 on profile from nightly 87
Categories
(Thunderbird :: Untriaged, defect)
Tracking
(Not tracked)
People
(Reporter: adrien.monteleone, Unassigned)
Details
(Whiteboard: [support])
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.0.2 Safari/605.1.15
Steps to reproduce:
Nightly crashes and won't even launch due to Code Signature problems. (see bug 1690118) I decided to drop back to a freshly downloaded and installed release version until this is resolved.
Actual results:
I get the error message that my profile was created on an older version and I need to quit or create a new profile.
Expected results:
Thunderbird should not break profiles against the current release version, certainly not without warning when testing beta and nightly. The linked help page in the error message discusses a change that was made as of v68, but I'm way past that. (https://support.mozilla.org/en-US/kb/unable-launch-older-version-profile) There is no indication on that page that another breakpoint was created after v78.
|
||
Comment 1•5 years ago
|
||
Did you follow the instruction to allow a downgrade and it isn't working?
Note: Downgrade protection can be overridden by launching Thunderbird through the command line with the --allow-downgrade parameter.
That is found in the Dedicated profile per Thunderbird installation link in the first paragraph of the support article you mention.
|
Reporter | |
Comment 2•5 years ago
|
||
Thanks, sorry I missed that originally. I managed to get it working by copying over the compatability.ini file from the profile generated by v78 into the profile from v87. Then v78 opened the newer profile without complaining or any apparent destruction of data or preferences. (I have a back up of course) I'm happy with it as-is, but if you need me to test using the official override, I can do so. I guess then, I'd change this to an Enhancement Request to add a button to that dialog to offer a Downgrade option up front with appropriate warnings of course. As well, that more info... page should be upgraded to show a list of profile breakpoints, or at least indicate if simply every version after 68 will encounter this issue. The page appears to mean that this is only a problem at the v68 breakpoint.
|
|
||
Updated•5 years ago
|
Description
•