1907444 - Thunderbird 128 ESR. I can no longer send messages. Send windows grays out with no error message.

Status: RESOLVED INVALID

(Thunderbird :: Untriaged, defect)

Description

[Sam]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36 Edg/124.0.0.0

Steps to reproduce:

I opened a new message and inserted the recipient address, wrote the message and clicked send.

Actual results:

The message did not send. The send window stayed open. No error message.

Expected results:

Obviously, the message should have been sent normally.

Comment 1

[Vlad Lucaci, Thunderbird QA (:vlucaci)]

Hello,

I have tried to reproduce you issue with 128.0esr (20240710185639) using Windows 11 and Windows 10 but did not manage to encounter the behaviour.

Can you give us any other relevant information that would help us reproduce this issue? (using IMAP/POP3 account?, single or multiple accounts, etc). Does this only happen for you on the latest 128.0esr?

If you can still reproduce this issue with the same repro steps, it would very helpful if you could indicate the affected versions on which you are able to reproduce it-if any(besides the 128.0esr on which you have encountered it) and if time allows, help us with a regression range for this issue.
I will provide the steps necessary.

You have to determine a build that reproduces the issue. In your case it seems Thunderbird v128.0esr right?

Then you should find one that does NOT reproduce it.

Detailed steps:

a. Open Mozregression app;
b. Click "File" -> "Run a single build";
c. On the "Single Run Wizard" pop-up, "Basic configuration", select "Thunderbird" and click "Next".
d. On the "Profile selection" page, just click the "Next" button.
e. On the "Build selection" select a date (dates before 2024-06-21 to have a better chance finding one that does not reproduce the issue) from the drop-down on the left and click "Finish".
f. Now the mozregression app will open a thunderbird build of the selected date and you can use it, close it and open another. (make a note of the version that does not reproduce the issue)

You will use mozregression app to "bisect" builds that reproduce the issue by builds that do not reproduce it in search of the one build/changeset that introduced the issue, in the first place:
a. Open mozregression-gui.exe
b. Click "File" -> "Run a new bisection"
c. On "Basic configuration" screen, select "Thunderbird" and click "Next" button.
d. Skip "Profile selection" screen by the "Next" button.
e. On the Bisection wizard screen, you will need to select a build that reproduces the issue and one that does not:
e1. In the "Last known good build:" section, select "date" on the right drop-down and the date of the build you found NOT to reproduce the issue.
e2. In the "First known bad build:" section, select "date" on the right drop-down and the date of the build you found to reproduce the issue.
f. Click "Finish" to start the bisection process.
g. Builds will open one-by-one, you will need to test each one of them and see whether the issue reproduces. If it reproduces, then you need to select the "bad" button in the mozregression window and if not, you need to select the "good" button.
h. When bisection is done, you will have the information in the "Log View" section of the mozregression window; bisection may also fail due to not enough builds, but the logs can always be useful.
Copy the logs in a text file and attach it to this bug.

If there is still information you need regarding the regression process, please request information from me.
Thank you for your contribution!

Comment 2

[Sam]

IMAP with a single account.

I ran Mozregression with an older build. It worked. I tried it with the latest build, 7-9-24. That worked also. Using these builds, I had to initiate my account, and during that process, I had to click to exempt certificates several times.

I was using the default IMAP and SMTP settings that Mozregression found, including port 587 and Starttls. I then set the SMTP settings to the settings that my mail server recommended to me previously, including port 465 and SSL/TLS. That also worked with Mozregression.

Then I installed version 128ESR again with my normal profile. I could not send a message. Then I deleted the SMTP settings and added them back again. I could still not send anything. When I clicked Send, it did nothing. No error message, no indication that it was doing anything. I went back to 115.12.2 and I was able to send normally.

Thus, setting up everything from scratch with Mozregreesion worked with the latest build. However, version 128, connected to my normal Thunderbird profile, does not work. (When I went back to version 115, I restored my 115 profile from a backup, so I didn't try to run 115 with the 128 profile.)

Comment 3

[Sam]

I did another experiment that worked. I installed 128ESR with a clean profile, set all of the server settings to match 115, moved my local folders from the old profile, and set all of the settings to match 115.

I was then able to send! Problem solved. Therefore, there must have been something left over in the old profile that prevented sending email with 128. I have saved the old profile if you would like me to check something in it.

I have been a Thunderbird since Eudora was discontinued. I'm not sure that the current 115 Thunderbird profile is that old, but it certainly has evolved over many years.

Comment 4

[Wayne Mery (:wsmwk)]

Thanks for the update

Comment 5

[Sam]

Hi Wayne, I think I may have found it!

With the clean profile, send worked. However, if I change the composition toolbar, I can no longer send. I tried the following experiment three times:

1. Send a message successfully.
2. Choose customize the composition toolbar and delete "Encrypt". I can no longer send messages.
3. Choose customize composition toolbar and insert "Encrypt" in its original position. Sending messages no works.

I also tried deleting other elements on the composition toolbar. I can delete others and I can still send. Whenever I delete Encrypt, send fails, when I restore it, send works.

Comment 6

[Vlad Lucaci, Thunderbird QA (:vlucaci)]

Hello Sam,

I tried to reproduce this issue with your newly narrowed down steps to reproduce, but was still unable to.

I have removed "encrypt", I have tried with and without Composition toolbar enabled , and I can send emails without any issues.
I tried with a clean and a dirty profile, and also tried the steps above after upgrading from 115.13.0 to 128.0esr.

If you are still able to reproduce this issue, would you be so kind to help us with a regression range?

I have provided the steps for this in comment 1.

Thank you in advance!

Comment 7

[Sam]

Hi Vlad,

This is getting to be more and more weird. I just did the following tests:

I tested for this problem on my wife's computer and two computers at a neighbor. One was Windows 11 and two were Windows 10. I was not able to reproduce the problem.

I ran the regression program on my computer with the default date, 7/9/2024, and did not see the problem.

I copied my new profile to my Windows 11 laptop and I did see the problem, where the send window freezes when I do a send without "Encrypt" in the composition tool bar. With "Encrypt", I can send. Then I reloaded my old version 115 profile to the laptop. With version 128 and the old profile, I continued to see the problem.

I tried the test again on my desk computer, with the same result, not able to send without "Encrypt". Incidentally, with the frozen send window, I cannot access the composition toolbar or anything else on that window. The only thing I can do is close the window and click on Discard Changes.

One other observation. During one test, I changed the composition toolbar. Then I added a To address and Subject, but I forgot to close the customize window. I then closed the customize window, but Send was grayed out and I could not click on Send or change the To address or Subject. I had to close the window and start over.

I am totally confused. I see the problem on my two computers but not on three other machines. It is consistent on my desktop and laptop, with my old profile and with the clean profile, but the problem does not appear with the regression program. Both are standard Windows 11 machines. My wife's computer is essentially the same as mine. Windows is up to date.

Please let me know if there is something else I can do, but I'm stuck. I have gotten around the problem, by leaving the Encrypt button, so my use of Thunderbird is fine, but I'm concerned that others may run into the problem.

Sam

Comment 8

[Sam]

I experimented some more. On my laptop, I deleted the profile and started from scratch. The problem did not occur. Then I changed the settings to match my desktop profile. The problem still did not occur.

Then I added the CardBook add-on and the problem reappeared, I could not send without Encrypt on the composition toolbar. I was able to make send work by either adding Encrypt to the toolbar or by deleting CardBook.

This explains the difference between machines. I use CardBook on my desktop and laptop, but it is not used on the other machines I tested.

When I first installed 128 and CardBook, CardBook did not auto-complete addresses. It has been updated twice and now works properly, except for this interaction with TBird.

Comment 10

[Magnus Melin [:mkmelin]]

Probably due to bug 1906833