Closed Bug 1374111 Opened 7 years ago Closed 7 years ago

To field empty when replying to an email

Categories

(Thunderbird :: Untriaged, defect)

52 Branch
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1357284

People

(Reporter: avoura, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.96 Safari/537.36

Steps to reproduce:

When replying to an email, including Reply to All, the To field(s) are blank. I also have an address set for BCC to be put in, but that is also missing. This has been occurring since latest update to Thunderbird 52.1.1 on Linux XFCE desktop (Ubuntu Studio 16.04)


Actual results:

Email address replying to not there, BCC address that should be automatically added is missing.


Expected results:

Email address replying to should be in the To field, the assigned BCC address should be there.
Known problem, caused by add-on "Contact Photo".
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
I also have seen this problem: click on Reply All, but apparently only my automatic self-Bcc is filled in. So I get my copy, but don't immediately notice that viewing it shows "Undisclosed Recipients", and no-one else receives it.

The kicker: the sole add-on I have in TB is Lightning. Also, I'm running TB 45.8.0.

The problem has only happened twice in the past couple of months, most recently today; this is too infrequent to make running in Safe Mode a useful diagnostic.

At any rate, while "Contact Photo" may be one cause of this behavior, it is evidently not the only one, nor is it limited to release 52+.

Please let me know if I should open a new bug instead of replying to this one.
(In reply to Ruth Milner from comment #2)
> Please let me know if I should open a new bug instead of replying to this
> one.
Since this bug is closed, you'd have a to open a new bug repeating what you stated in comment #2.

However, "only happened twice in the past couple of months" doesn't sound like a problem that can be readily reproduced, so there's little chance of fixing anything unless you can find a reproducible case. Also, TB 45.x has come to the end of its lifetime, so we will only fix problems in TB 52 now.
I understand that it would be unreasonable to expect TB45 to be fixed, or that such a sporadic bug should be immediately hunted down and killed.

I posted my response primarily to provide additional information which demonstrates that the current assumptions about when the problem occurs are incomplete. It isn't only a result of whatever changed in TB52, and it isn't only due to the "Contact Photo" add-on.

This occurred at work, and we're about to deploy 52.2.1. If I see the problem again after that happens, I'll post a new bug and include these additional details.

Thank you.
You need to log in before you can comment on or make changes to this bug.