For some time my thunderbird occasionally emits quite annoying error message that another operation is in progress. It seems it is blocking itself. I have been running multiple thunderbird instances concurrently on _different_ machines. My home is local on encrypted disk, it is not shared in any way. I have few folders configured to be compacted and dropped automatically. But this error happens in rows. It tells me for one folder, I click okay. It says another folder cannot be compacted too. Then it follows with 3-7 repeats, which are quite annoying. Please help me finding a reason for this. I tried running thunderbird from terminal to see what it is writing. Unfortunately no error message were printed there. Reproducible: Sometimes Steps to Reproduce: 1. have thunderbird configured for gmail account 2. have a lot of mail folders for separate mailing lists 3. have it running few hours. Actual Results: Quite annoying error message saying the operation could not be done. Expected Results: Some kind of locking is done on each folder. Folder operations should have some jitter randomized, so they should not clash if I have multiple thunderbird instances connected to the same account.
Created attachment 1975286 [details] retention policy
Created attachment 1975287 [details] account general information
Created attachment 1975288 [details] operation in progress message
Created attachment 1975289 [details] synchronization & storage panel
Frankly that's beyond our scope here - please report it at bugzilla.mozilla.org to thunderbird component. Thanks.
I guess bug https://bugzilla.mozilla.org/show_bug.cgi?id=288896 is relevant here. I haven't found existing bug for compact operation specifically. Issue https://bugzilla.mozilla.org/show_bug.cgi?id=1757181 seems to be similar. But I have filled https://bugzilla.mozilla.org/show_bug.cgi?id=1867762 as a new bug, because not existing bug seemed to report exactly this.
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.