As per the summary. Attaching a debug stacktrace. This happens reliably.
Created attachment 13670 [details] gdb debug stacktrace of SIGABRT
This did not occur with 102.6.0.
It's worse than I thought. The crash occurs whenever new IMAP mail comes in, so TB will crash without any user interaction. It will also crash if you try to switch to the IMAP Inbox folder even if there are no unread messages there.
Summary: TB crashes if you attempt to switch to an IMAP Inbox with an unread message => TB crashes if you attempt to switch to an IMAP Inbox
That is strange. I use thunderbird-102.7.1.1 (testing) on mga8 with several IMAP accounts, no problem... Hm... One difference, they are "offline IMAP" so stored locally too, but sync using IMAP. Have you tried this thunderbird version on mga8 with that IMAP account? Bug 31438 - Thunderbird 102.7.1
CC: (none) => fri
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=31438
I have used this IMAP account throughout the MGA8 cycle in cauldron (which is all I usually run) without a problem. A comment above indicates that 102.7.0 had a regression in MS 365 support (which this account is), but with oAuth2 it has been working right along. Did 102.7.1 claim to fix the regression ?
I don't know if this makes a difference, but the .thunderbird directory used for this is an NFS mount. It lives on a desktop machine, but I access it from a laptop (been doing this for years).
(In reply to Frank Griffin from comment #5) > Did 102.7.1 claim to fix the regression ? https://www.thunderbird.net/en-US/thunderbird/102.7.1/releasenotes/
(In reply to sturmvogel from comment #7) > (In reply to Frank Griffin from comment #5) > > Did 102.7.1 claim to fix the regression ? > https://www.thunderbird.net/en-US/thunderbird/102.7.1/releasenotes/ Thanks, but that doesn't seem to be a match. A failure to authenticate would cause a popup message, and it would affect more than just Inbox.
Fixed with 102.7.1.2 !
Resolution: (none) => FIXEDStatus: NEW => RESOLVED