Closed Bug 1876760 Opened 2 years ago Closed 2 years ago

Thunderbird crashes upon renaming the target folder of an ongoing message moving operation

Categories

(Thunderbird :: Folder and Message Lists, defect)

Thunderbird 115
defect

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: niklas.kitzmann, Unassigned)

Details

Steps to reproduce:

Thunderbird 115.6.0 (64-bit) on Linux Mint 21.2 (Kernel: Linux 5.15.0-91-generic)

I moved (drag & drop) a large amount of emails from an IMAP-synchronized folder to a local folder. While this process was running, I changed the name of the local folder.

Local Folder, old name: "Inbox"
Attempted to change local folder name to: "Inbox (<=2020)"

Actual results:

Thunderbird immediately crashed.

Local folders present on re-opening Thunderbird after crash:
"Inbox" -- containing ~200 emails that can still be found in the original IMAP-synchronized folder.
"Inbox (e66a319b" -- containing ~1100 emails, some (but not all) of which can still be found in the original IMAP-synchronized folder.

I can't tell if any emails from the original folder have been lost.

Expected results:

Either a warning message that folder renaming during email moving operations is not possible, or the successful renaming of the folder with subsequent completion of email move.

Summary: Thunderbird crashes when I rename of a folder while moving messages to that folder → Thunderbird crashes when I rename a folder while moving messages to that folder
Summary: Thunderbird crashes when I rename a folder while moving messages to that folder → Thunderbird crashes upon renaming the target folder of an ongoing message moving operation

(In reply to Magnus Melin [:mkmelin] from comment #1)

Please provide the crash id. See https://support.mozilla.org/en-US/kb/thunderbird-crashes

Flags: needinfo?(niklas.kitzmann)
Whiteboard: [closeme 2024-02-25]

Resolved per whiteboard

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Flags: needinfo?(niklas.kitzmann)
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2024-02-25]
You need to log in before you can comment on or make changes to this bug.