User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_5) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.1.1 Safari/605.1.15

Steps to reproduce:

If you un-check Paragraph format, when you open Thunderbird, particularly after an update, the box returns to checked. The value is not saved version. 68.10.0

Actual results:

checkmark returns after restarting Thunderbird

Expected results:

Value should have been saved as a preference and remained un-checked. This has been going on for quite a long time.

Worksforme on Win10, 68.10.0 (32-Bit) (preserves unchecked value across app restarts), but I haven't checked the update scenario.

Confirming based on two user reports.

Wfm on Win 10 for each of 68.10.0 (32-bit) and 78.0.1 (64-bit). However, both reports concur that this bug involves the updating process.

Ancient issue in 68, please do your homework and find the dupe which has a solution as well.

(In reply to Jorg K (CEST = GMT+2) from comment #4)

Ancient issue in 68, please do your homework and find the dupe which has a solution as well.

Can you clarify what the 'solution' is? From a UI\UX perspective, the only actual solution would be for TB not to break users' preferences (which the software continues to do). If I understand your comments there correctly, the problem can be temporarily mitigated by manually editing text in a javascript file? Is that the standard of usability that TB development holds itself to?

Well, as you can see in bug 1489976, there is a migration problem, most likely related to the upgrade of an SQLite database. Yes, the issue that individual users have reported can be "fixed" by manually edit a pref or the corresponding pref file. You have a few choices:

• Fix your issue the way I suggested
• Start a discussion about the TB standard of usability
• Come onboard (it's open source) and try to find out where in the ancient past that database got corrupted and why the migration fails.

Or just accept the standard answer for profile corruption: Please start on a new profile and you won't have a problem.

(In reply to Jorg K (CEST = GMT+2) from comment #7)

Well, as you can see in bug 1489976, there is a migration problem, most likely related to the upgrade of an SQLite database. Yes, the issue that individual users have reported can be "fixed" by manually edit a pref or the corresponding pref file. You have a few choices:

• Fix your issue the way I suggested
• Start a discussion about the TB standard of usability
• Come onboard (it's open source) and try to find out where in the ancient past that database got corrupted and why the migration fails.

Or just accept the standard answer for profile corruption: Please start on a new profile and you won't have a problem.

Thanks for your time.

And there is a support article referenced in the other bug, maybe that has further hints, I haven't looked.