Closed Bug 1266971 Opened 8 years ago Closed 3 years ago

File > New > Get a New Mail Account, Skip fails. "SecurityError: The operation is insecure." in accountProvisioner.js

Categories

(Thunderbird :: Account Manager, defect)

45 Branch
Unspecified
Windows 8
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: ukrainianconsular, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 6.2; rv:38.9) Gecko/20100101 Goanna/2.0 Firefox/38.9 PaleMoon/26.2.1
Build ID: 20160406090915

Steps to reproduce:

file/new/get new mail account/skip this and use my existing email 


Actual results:

(nothing happens)


Expected results:

Ability to create a new account
Works for me. Please try again in safe mode.
Workaround: File > New > Existing Mail Account.
Severity: normal → minor
Component: Untriaged → Account Manager
Summary: Bug in thunderbird v45 → File > New > Get a New Mail Account, Skip doesn't work.
safe mode/addons disabled/not working
& if i open it, console says:

Timestamp: Sat 23 4:32:39 PM Error: SecurityError: The operation is insecure. Source File: chrome://messenger/content/newmailaccount/accountProvisioner.js Line: 254
I also cannot reproduce. 

Line 254 involves
mconley@9990 252    // If we have a name stored in local storage from an earlier session,
mconley@9990 253   // populate the search field with it.
mconley@9990 254   let name = EmailAccountProvisioner.storage.getItem("name") ||
aleth@23464  255              nameElement.value;
OS: Unspecified → Windows 8
Summary: File > New > Get a New Mail Account, Skip doesn't work. → File > New > Get a New Mail Account, Skip fails. "SecurityError: The operation is insecure." in accountProvisioner.js
I can't reproduce either. The account creation wizard normally opens up.
I can reproduce the bug on Windows 7 Pro SP1 as well as Windows XP Pro SP3, and have tested it on several computers (between five and ten)

As Jorg K says, it is possible to create a new account when going through "File --> New --> Existing mail account", but I was used to add accounts from the main window, that is, clicking on the name of any already created email account -or on "Local folders"-, and then on the icon to create a new account that is displayed on the main window. After clicking this icon and then on "Skip this and use my existing email", the window to add an existing mail account should be displayed, but it isn't. Same behaviour if you click the neighbour option ("I will set up my account later" or something similar in english; sorry for not being accurate). The error logged on the debug console is the one said by ukrainianconsular.
OK, so you're not talking about
  File > New > Get new mail account
as reported in comment #0.

You're talking about left-clicking onto any account in the folder pane (incl. Local Folders) and then seeing a page on the right with "Email", "Accounts", "Advanced Features".

Now, if you click on "Create a new account" under the heading "Email" you get a panel "Welcome to Thunderbird", on there you have buttons "Skip this and use my existing email" or "I think I'll configure my account later".

These two buttons work.

The panel is in fact the same one that gets launched via the File menu.

Are you using a localised version? Which? Perhaps that has got a problem.

Please try the en-US version. You can install it in parallel, just use a custom install and select a different directory, for example C:\Program Files (x86)\Mozilla Thunderbird 45-en-US\.
Now on XP I have installed the en-US version on the same directory of my localised version (catalan), as well as on a different directory, but the issue remains
I'll paste the output of the debug console when I click the option "Create a new account" with v38.5. With this version, the issue is not present and the console shows four warnings instead of the single error shown with v45.0 . Maybe this output can be helpful to discover the reason of the issue.


Timestamp: 06/05/2016 21:24:59
Warning: JavaScript 1.6's for-each-in loops are deprecated; consider using ES6 for-of instead
Source File: chrome://messenger/content/accountcreation/sanitizeDatatypes.js
Line: 154, Column: 8
Source Code:
    for each (var allowedValue in allowedValues) 

-----------------

Timestamp: 06/05/2016 21:24:59
Warning: JavaScript 1.6's for-each-in loops are deprecated; consider using ES6 for-of instead
Source File: chrome://messenger/content/newmailaccount/accountProvisioner.js
Line: 574, Column: 8
Source Code:
    for each (let [i, provider] in Iterator(otherLangProviders)) { 

-----------------

Timestamp: 06/05/2016 21:24:59
Warning: JavaScript 1.6's for-each-in loops are deprecated; consider using ES6 for-of instead
Source File: chrome://messenger/content/newmailaccount/accountProvisioner.js
Line: 735, Column: 8
Source Code:
    for each (let [i, provider] in Iterator(returnedProviders)) { 

-----------------

Timestamp: 06/05/2016 21:24:59
Warning: JavaScript 1.6's for-each-in loops are deprecated; consider using ES6 for-of instead
Source File: chrome://messenger/content/newmailaccount/accountProvisioner.js
Line: 754, Column: 10
Source Code:
      for each (let [j, address] in Iterator(provider.addresses)) { 

-----------------

Timestamp: 06/05/2016 21:24:59
Warning: JavaScript 1.6's for-each-in loops are deprecated; consider using ES6 for-of instead
Source File: chrome://messenger/content/newmailaccount/accountProvisioner.js
Line: 810, Column: 8
Source Code:
    for each (let [i, provider] in Iterator(data)) {
(errata on my last comment: I said "four warnings", actually there are five)
Wasn't able to reproduce. 
With File -> New -> Get a new mail account, "Skip this and use my existing email" and "I think I'll configure my account later" work.
With Left-clicking onto any account -> Create a new account: Email, both buttons work
I Also have the same issue recently: https://bugzilla.mozilla.org/show_bug.cgi?id=1295069
See Also: → 1295069

Time to close this. On trunk this code was also just rewritten.

Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.