Closed Bug 1906841 Opened 2 years ago Closed 2 years ago

Email drafts get sent on autosave with Snap 128 beta

Categories

(Thunderbird :: Message Compose Window, defect)

Thunderbird 128
defect

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: danilo.ciaffi, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: privacy)

Attachments

(1 file)

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:127.0) Gecko/20100101 Firefox/127.0

Steps to reproduce:

I click "Reply All" and started typing.

Actual results:

Every autosave actually sent the current draft to all recipients.

Expected results:

The message should have been saved but not sent.

Any add-ons listed in Tools > Add-ons > extensions?

Flags: needinfo?(danilo.ciaffi)
Keywords: privacy
Blocks: tb128found

(In reply to Wayne Mery (:wsmwk) from comment #1)

Any add-ons listed in Tools > Add-ons > extensions?

None

Flags: needinfo?(danilo.ciaffi)

Hello,

I have tried to reproduce your issue using the STR from the description but did not succeed using Windows11, macOS 14 and 24.04 with the affected build from 2024-07-09(20240709104114) as well as 129.0b1(20240708223515), 1280.esr(20240710185639), 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(besides the 20240709104114 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.0b1 (64-bit), 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-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!

Flags: needinfo?(danilo.ciaffi)

What type of account is it?
Have you configured the draft folder to be the outbox + the server acting on that perhaps?

Attached file Bisection logs —
(In reply to Vlad Lucaci, Thunderbird QA (:vlucaci) from comment #3) > Hello, > > I have tried to reproduce your issue using the STR from the description but did not succeed using Windows11, macOS 14 and 24.04 with the affected build from 2024-07-09(20240709104114) as well as 129.0b1(20240708223515), 1280.esr(20240710185639), 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(besides the 20240709104114 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.0b1 (64-bit), right? > > Then you should find one that does NOT reproduce it. Detailed steps: > > a. Open [Mozregression app](https://mozilla.github.io/mozregression/install.html); > 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! Hi sorry for the late reply. I tried the steps above and wasn't able to reproduce the issue on any version. It happened for four different emails across a few days, and then did not occur anymore. I checked the days and they all were in the same week, maybe some thing got weird in my installation and turning the machine off and on again (heh) over the weekend fixed it? Here are the logs: ``` ``` Thanks a lot for looking into this

(In reply to Magnus Melin [:mkmelin] from comment #4)

What type of account is it?
Have you configured the draft folder to be the outbox + the server acting on that perhaps?

There is no additional configuration on folders. The account provider is https://webmail.aruba.it/

Flags: needinfo?(danilo.ciaffi)

(In reply to danilo.ciaffi from comment #5)

Sorry, the formatting went all over the place. Anyway if that's of any relevance the version I got was the v128.0b1, and i got it from the beta channel in the ubuntu snap store.

danilo, thanks for the update. Let's call this incomplete for now. if it happens again in the future please report again.

I've not seen any recent reports of anything like this. But I had seen a report in the past - unfortunately impossible to track down, and I'm not sure it was even in bugzilla (didn't find anything https://mzl.la/4fX7yyO )

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
Summary: Email drafts get sent on autosave → Email drafts get sent on autosave with Snap 128 beta
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: