Correspondents column in message list blank after switching between folders
Categories
(Thunderbird :: Folder and Message Lists, defect)
Tracking
(thunderbird_esr102+ affected)
People
(Reporter: tim, Unassigned)
References
()
Details
(Keywords: regression, regressionwindow-wanted, Whiteboard: [problem resolves itself after a while/restart])
Attachments
(2 files, 2 obsolete files)
Correspondents column in Thunderbird 102.3.0
Steps to reproduce:
Upgraded to version 102.3.0, and then switched from one folder to another one.
Actual results:
The correspondents column in the message list is blank.
Expected results:
The correspondents column should have the name/email address of the sender or recipient of each message.
Same problem here since the update to Thunderbird 102.3.0. At startup, entries are still briefly displayed in the Correspondents column, but then they disappear (except for emails I sent to myself).
When I copy the profile to a portable version of Thunderbird 102.2.2, the Correspondents column is displayed normally again.
Attached are two screenshots showing the differences in both versions.
Same problem since upgrade today; also happens with the "From" column.
This bug was also reported here: bug 1791966
It should be fixed quickly, because it severely affects working with Thunderbird.
|
||
Comment 9•3 years ago
|
||
I cannot reproduce this. And even if I knew the cause, no capability to fix.
Does this issue reproduce after Help > Troubleshoot mode?
|
||
Comment 10•3 years ago
|
||
| workaround | ||
I downgraded back to 102.2.2 and the issue went away. There is definitely something wrong with 102.3.0.
|
||
Comment 11•3 years ago
|
||
Not the most useful comment, but I too have seen this with TB 102.3.0 on both my home PC (on Windows 11 Pro) and work PC (on Windows 10 Pro) separately.
|
|
||
Comment 12•3 years ago
|
||
(In reply to UsedJeans from comment #10)
I downgraded back to 102.2.2 and the issue went away. There is definitely something wrong with 102.3.0.
This is very helpful. We therefore know the problem is likely caused by one of these uplifted patches to 102.3.0.
|
|
||
Updated•3 years ago
|
|
|
||
Updated•3 years ago
|
|
Reporter | |
Comment 13•3 years ago
|
||
I also downgraded to 102.2.2 which resolved the issue on my 2 PCs, but have upgraded to 102.3.0 again on both of them, and the issue is no longer present.
|
|
||
Comment 14•3 years ago
|
||
Hi Tim,
That's useful to know. Does the issue still remain resolved after browsing through your folders a bit and receive new messages?
I ask as I found that the issue didn't occur immediately after updating to 102.3.0, and 100% remember seeing a mixture of populated and unpopulated values for this column in my inbox before it always became unpopulated. The issue may return to you shortly, perhaps after receiving some more emails.
|
|
Reporter | |
Comment 15•3 years ago
|
||
When I had the issue, there was a single message in one of my inboxes that did not have a blank Correspondents column. I have sent and received emails since upgrading to 102.3.0 again, and the issue has not reoccurred so far.
|
||
Comment 16•3 years ago
|
||
Problem stopped happening after quitting then restarting Thunderbird . . . previously when I quit and restarted whatever folder I was in would load properly upon restarting, but as soon as I switched to another folder the "from" column would be blank for that folder any folders I navigated to from then on. But on this restart, everything seems back to normal. Did not downgrade and update/problem started with update to 102.3.0 then disappeared this morning.
|
||
Comment 17•3 years ago
|
||
Downgrading to 102.2.2 also "solved" the problem for me. Because of Tim's comment I then tried the update to 102.3.0 and the problem indeed seems to be gone until now. This is really a strange bug.
|
|
||
Comment 18•3 years ago
|
||
As per jdquirke my home installation has suddenly resolved this issue by itself. I too did not attempt any downgrade then upgrade back up to 102.3.0, just left it as is.
|
||
Updated•3 years ago
|
|
||
Comment 20•3 years ago
|
||
Probably something to do with bug 1782725, although I don't know why. It would be interesting to see what happens if the user changes mail.displayname.version but I suspect for most the problem has gone away now.
Description
•