Closed Bug 1838758 Opened 11 months ago Closed 11 months ago

fully manually configured account is silently deleted on Finish if no password as provided

Categories

(Thunderbird :: Account Manager, defect)

defect

Tracking

(thunderbird_esr102 unaffected, thunderbird115+ fixed)

RESOLVED FIXED
116 Branch
Tracking Status
thunderbird_esr102 --- unaffected
thunderbird115 + fixed

People

(Reporter: leftmostcat, Assigned: mkmelin)

References

(Regression)

Details

(Keywords: regression, Whiteboard: [snnot3p])

Attachments

(1 file)

I can reproduce this consistently with the following steps:

  1. Open account creation screen (either in new profile or from Account Settings page)
  2. Manually configure an IMAP+SMTP account and select Done

At this point, it's possible to open the Account Settings page and see that the account is present and to open the message list and see the account, with emails being downloaded.

  1. Select Finish on the account setup page

The account will still be present in Account Settings, but its name will have changed, all server settings will have been wiped, and it is no longer visible in the message list.

Oh I see, it doesn't happen if you first find something and then manually change. Only if you go directly to manual.

Assignee: nobody → mkmelin+mozilla
Summary: Newly-created account is silently deleted on Finish → fully manually configured account is silently deleted on Finish
Whiteboard: [snnot3p]

For the bug to reproduce you must leave the password field blank.

Summary: fully manually configured account is silently deleted on Finish → fully manually configured account is silently deleted on Finish if no password as provided

There were cases where the temporary server was removed but not nulled out. Since it was not nulled out in those cases,
"onunload" handling removed a matching server which we did want to keep.

This occurred since no verification of password will take place if none was provided (and not OAuth2).
Normally after verification a proper cleanup step would take place, but since there was not verification,
this.server was left non-null.

Status: NEW → ASSIGNED
Target Milestone: --- → 116 Branch

Pushed by mkmelin@iki.fi:
https://hg.mozilla.org/comm-central/rev/37c3a52795c5
Use centralized cleanup() in config verifier. r=leftmostcat

Status: ASSIGNED → RESOLVED
Closed: 11 months ago
Resolution: --- → FIXED

Comment on attachment 9339452 [details]
Bug 1838758 - Use centralized cleanup() in config verifier. r=leftmostcat

[Approval Request Comment]
Regression caused by (bug #): bug 1788086
User impact if declined: in the given case, the just set up account would instantly be removed
Testing completed (on c-c, etc.): c-c
Risk to taking this patch (and alternatives if risky): it's well understood and should be safe

Attachment #9339452 - Flags: approval-comm-beta?

Comment on attachment 9339452 [details]
Bug 1838758 - Use centralized cleanup() in config verifier. r=leftmostcat

[Triage Comment]
Approved for beta

Attachment #9339452 - Flags: approval-comm-beta? → approval-comm-beta+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: