Hallo Carsten,
I tried all you wrote without success. If cert9.db and logins.json
removed all password-entries and so on must reenter (you warn for that)
but by reenter none lines added in saved passwords.
O.K. I must work and moved the old profile to a virtual machine and
begin with a blank profile on the problem-machine. So I recreate all
mailboxes, calendars, certificates step by step by coping settings and
passwords from the virtual machine. The gpg-keys I must import from a
third machine. Now I can work again.
On the third machine with a similar setup the upgrade from 102 to 115
make no problems. So I can't say what is the causal effect and we can
close the bug.
with regards
Am 09.10.23 um 21:27 schrieb Carsten Schoenert:
> Hello Andreas,
>
> On 10/9/23 20:02, Andreas Matthus wrote:
>> Hallo Carsten,
>>
>> thank you for your answer.
>> Unfortunately deleting and/or change primary password give no success.
>>
>> On javaconsole I see a difference:
>> ---snipp
>> encrypted-openpgp-passphrase.txt corruption fixed. Corrupted file
>> moved to
>> /home/andreas/.thunderbird/ys2evdnt.default/encrypted-openpgp-passphrase.txt.corrupt
>> masterpass.jsm:200:19
>> NS_ERROR_FAILURE: Component returned failure code: 0x80004005
>> (NS_ERROR_FAILURE) [nsISecretDecoderRing.encryptString]
>> _ensurePasswordCreatedAndCached
>> chrome://openpgp/content/modules/masterpass.jsm:269
>> RNP.jsm:465:15
>> NS_ERROR_FAILURE: Couldn't decrypt string crypto-SDR.sys.mjs:199
>> NS_ERROR_FAILURE: Couldn't decrypt string crypto-SDR.sys.mjs:199
>> ---snipp
>>
>> Every time I start without --safe-mode
>> encrypted-openpgp-passphrase.txt renamed to
>> encrypted-openpgp-passphrase.txt-1.corrupt,
>> encrypted-openpgp-passphrase.txt-2.corrupt and so on.
>>
>> All extensions I deleted an purged thunderbird-l10n-de, but just the
>> same result.
>
> you can try to stop Thunderbird, backup the file key4.db from your
> profile folder, than remove that file and restart Thunderbird.
>
> Thunderbird will create a new file and you should be able to set again
> a new master password.
> Other possible corrupted files are cert9.db and logins.json.
> If you remove these files you need to re-add all the passwords and
> certificates that were used! So be careful.
>
> It's long ago but we did have similar bug report in the past there
> deleting the key4.db was the solution. But you
>
> As always, please make a backup of your profile folder before doing
> any modification within the profile folder.
>