Closed Bug 1079800 Opened 10 years ago Closed 3 years ago

Threadpane should be populated again after compact

Categories

(Thunderbird :: Folder and Message Lists, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: nONoNonO, Unassigned)

References

Details

(Whiteboard: [dupeme?])

After a compact action i always end up with an empty thread pane. I have to switch to another folder and then back to the original one, before i see the new contents. It would be nice if Thunderbird would auto populate the thread pane again...
I'm pretty sure this would be a duplicate but I'm not finding said bug report. Perhaps you or someone else can find it, or confirm that I am batty.

yours is a long the lines of these, but not exactly:

bug 497804 – If "filter move" is invoked while "compact folder" is running, both "compact folder" and "filter move" silently fails, and "blank thread pane/UI hang" occurs on "move target folder"
bug 479064 – When a deleted message causes 'compact folders', the message list pane loses focus/selection and scrolls back to the top
bug 677093 – "Compact folders" when in newsgroup closes message pane and list-of-messages pane
Component: Mail Window Front End → Folder and Message Lists
Whiteboard: [dupeme?]
Maybe one of the following:
bug 209883 -  compacting folders turns messages invisible
bug 494752 - If Compact Folder is executed when "outdated msf condition" exist, Rebuild-Index clears thread pane. Restart of Tb is required to recover. ("Component returned failure code: 0x80550005 [nsIMsgFolder.updateFolder]")
(I haven't checked the error console after compacting yet...)

Onno, has this happened in the last few years, and an you reproduce today?

Flags: needinfo?(o.e.ekker)
See Also: → 494752

Hi Wayne, I haven't seen this lately and cannot reproduce at the moment, so this probably got fixed somewhere along the way...

Status: NEW → RESOLVED
Closed: 3 years ago
Flags: needinfo?(o.e.ekker)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.