Closed Bug 1710259 Opened 5 years ago Closed 4 years ago

can’t delete folder in localhost email account without sync

Categories

(Thunderbird :: Folder and Message Lists, defect)

x86_64
Linux
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: Nick_Levinson, Unassigned)

References

()

Details

STR:

  1. You may not want to do this.
  2. In Tbird, select an email account that is on your localhost and that is not synchronized to an account on a remote server.
  3. In that local account, select a folder you want to delete. (If you don't have one, you can probably make one, quit Tbird, and restart Tbird.)
  4. If the folder is not empty, empty it.
  5. Context-click the folder.
  6. Delete it.

Actual result: It won't delete but will show progress indicators. If it takes more than a few seconds (maybe longer if you have a huge number of emails across all folders in the account), you may see progress indication for days, including through multiple quits and warm reboots.

Expected result: Deletion within a reasonable time.

Additional info:

A kludgy solution is at https://support.mozilla.org/en-US/questions/1334909 , but it's too geeky for mortals.

Possibly relevant: bug 533513.

Fedora 34 Linux, kept evergreen, with Tbird 78.10.1 (64-bit).

Created a folder under Local Folders. Deleted through context menu - works find. The folder went to Trash.

It didn't go to Trash for me when I was experiencing what this thread is about, although in the past a deleted folder had gone there. The long time to make progress probably means it won't go to Trash yet and maybe progress never ends so it never gets to Trash.

Does this also reproduce in version 91?

Flags: needinfo?(Nick_Levinson)

Apparently, version 91.3.0 (64-bit) on F35 works okay.

If I can set this to something like WorksForMe, I will. If I don't have that authority, please set it so.

Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Flags: needinfo?(Nick_Levinson)
Resolution: --- → INVALID
Resolution: INVALID → WORKSFORME
You need to log in before you can comment on or make changes to this bug.