On 9/21/22 11:31, Lew Wolfgang wrote:
On 9/17/22 13:31, David C. Rankin wrote:
On 9/17/22 13:24, Carlos E. R. wrote:
Only the software development engineers know for certain what needs to be protected and backed up. The TB update process/software should preserve and backup all user data before proceeding with an irreversible upgrade.
Even if they do, there is no way to revert the process once the admin upgraded the code.
Imagine my F'ing surprise when Mozilla asked me test 102-beta on the CPU use issue, damn glad I backup up my TB directory before that. When I was done, I just wiped the TB directory and restored from the backup and went back to TB 91 -- that works.
The biggest rub is there is NO WARNING. There should at least be a notice and (yes/no) prompt to the user explaining the irrevocable change that is about to occur.
It happened to me two days ago without warning! It scrambled my saved messages to some degree, but worse, it broke Smartcard S/MIME encryption. I can decrypt existing messages, but encrypting new ones fails.
I'm screwed! I'm having to use Outlook!!
Update: I couldn't abide the thought of having to use Outlook, and having the feeling that the S/MIME bug won't be fixed anytime soon, I managed to pull a backup from right before the Thunderbird upgrade to 102. I then went back to TB-91 and locked it in place. I can encrypt again now, and my 32-GB of decades of saved messages is whole, except for the last two days, which is okay. Regards, Lew