1907792 - Send doesn't work for me in version 128.0.

Status: RESOLVED DUPLICATE of bug 1906833

(Thunderbird :: Untriaged, defect)

Description

[wrhenshaw99]

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

Steps to reproduce:

I composed a message and clicked on Send.

Actual results:

Nothing happended. I tried this 4 or 5 times in different accounts. Always the same result.

Expected results:

The message should have been sent

Comment 1

[wrhenshaw99]

This happened right after updaing from 115.12.2 to 128.0. I reverted to 115.12.2 and Send worked just fine.

Comment 2

[Ramona Gavrilescu]

Hello,

I have tried to reproduce your issue using the STR from the description but did not succeed, the email gets sent and copied to Sent folder without any issue.
I used Win10 and Win11, on TB 128.0esr(20240703144221), 128.0(20240703144221), 128.0b4(20240624182435) and 115.13.0(20240709183211).

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 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.

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-14 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 3

[Corey Bryant]

This may be the same as bug 1907444.

Comment 4

[wrhenshaw99]

I am the OP on this bub. I can confirm that bug 1907444 is exactly what is happening to me as well. Why is that bug closed?

Comment 5

[wrhenshaw99]

Ramona,

Due to this problem I reverted to TB 115.12.2 last night. Do I have to have 128 installed to do this regression testing? If that is the case I need TB to be working so I don't want to install 128 again.

Bill

Comment 6

[Wayne Mery (:wsmwk)]

(In reply to wrhenshaw99 from comment #4)

I am the OP on this bub. I can confirm that bug 1907444 is exactly what is happening to me as well. Why is that bug closed?

See bug 1907444 comment 8.

If you had not tested 128 with Help > Troubleshoot mode then I suspect we will end up closing this.

Comment 7

[wrhenshaw99]

How would I have known to test with Help > Troubleshoot. I updated to the 128 assuming it would be what I would be using. I wasn't "testing" it.

I am dependent on a working Thunderbird. I can't really re-install 128 which isn't working for me and be without TB for any length of time.

It is a shame that multiple people are having this same problem and yet their issues are being closed.

TB has really gone downhill in my estimation.

Comment 8

[wrhenshaw99]

Wayne,

I just saw a posting in alt.comp.software.thunderbird which indicates that the other issue, 1907444, was caused by Cardbook. I thought it was related to not having Encrypt in the composition toolbar which I have never had. I notice that that posting was by "Wayne". Is that you?

In any case, I also use Cardbook so if that is the cause I apologize for saying Thunderbird has gone downhill. I was just upset over the possible cloing of the issue because I hadn't tested with Help > Troubleshoot which I couldn't have known to use.

Sorry,
Bill

Comment 9

[Wayne Mery (:wsmwk)]

That is me. Since you indicate using cardbook I think we can assume these bugs are the same.

If you are using the Guided submit form https://bugzilla.mozilla.org/enter_bug.cgi?product=Thunderbird&format=guided unfortunately the fine print https://bugzilla.mozilla.org/page.cgi?id=bug-writing.html does not mention Troubleshoot Mode. But it is considered best practice.

I am dependent on a working Thunderbird. I can't really re-install 128 which isn't working for me and be without TB for any length of time.

The beauty of Troubleshoot Mode is it is very quick and easy to do. Now we know :)

Comment 10

[Corey Bryant]

This is getting fixed in bug 1906833