Closed Bug 1614892 Opened 5 years ago Closed 5 years ago

"Programming bug" reported when setting up new email account manually

Categories

(Thunderbird :: Untriaged, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: mail, Unassigned)

References

Details

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

Steps to reproduce:

This is on Ubuntu 18.04.3 LTS, Thunderbird 68.2.2 (64-bit). Cannot manually update versions, etc., as this is rolled out automatically by my company.

  1. Start thunderbird from gnome-terminal
  2. Open Preferences > Account settings
  3. Open Account Actions > Add email account
  4. Enter name, email address, password
  5. click Continue
  6. Account found (Exchange account, but am not allowed to install the Owl add-on): Click Manual config
  7. Enter config details:
  • IMAP, Port 993, (SSL/TLS alreaedy in field)
  • SMTP, 587, (STARTTLS already in field)
  • Incoming = email address, Outgoing = emtpy
  1. Click Re-test
  2. Thunderbird finds settings (Kerberos/GSSAPI)
  3. Click Done

Actual results:

I get a pop-up with "Programming bug. Assertion failed, see log."

Stack trace:

1581498080170 addons.xpi WARN Not converting unknown addon type undefined
1581498088288 addons.xpi WARN Can't get modified time of /usr/lib/thunderbird/features/wetransfer@extensions.thunderbird.net
Programming bug. Assertion failed, see log.
-- Exception object --

  • _message (string) 'Programming bug. Assertion failed, see log.'
  • stack (string) 615 chars
  • constructor (function) 4 lines
  • message (string) 'Programming bug. Assertion failed, see log.'
  • toString (function) 3 lines

-- Stack Trace --
Exception@chrome://messenger/content/accountcreation/util.js:147:3
NotReached@chrome://messenger/content/accountcreation/util.js:159:13
assert@chrome://messenger/content/accountcreation/util.js:19:11
needed@chrome://messenger/content/accountcreation/emailWizard.js:2074:5
open@chrome://messenger/content/accountcreation/emailWizard.js:2132:23
onCreate@chrome://messenger/content/accountcreation/emailWizard.js:1886:30
oncommand@chrome://messenger/content/accountcreation/emailWizard.xul:1:20
MsgAccountManager@chrome://messenger/content/accountUtils.js:290:12
oncommand@chrome://messenger/content/messenger.xul:1:1
2020-02-12 10:03:21 mail.setup ERROR Error creating account. ex=Programming bug. Assertion failed, see log., stack=Exception@chrome://messenger/content/accountcreation/util.js:147:3
NotReached@chrome://messenger/content/accountcreation/util.js:159:13
assert@chrome://messenger/content/accountcreation/util.js:19:11
needed@chrome://messenger/content/accountcreation/emailWizard.js:2074:5
open@chrome://messenger/content/accountcreation/emailWizard.js:2132:23
onCreate@chrome://messenger/content/accountcreation/emailWizard.js:1886:30
oncommand@chrome://messenger/content/accountcreation/emailWizard.xul:1:20
MsgAccountManager@chrome://messenger/content/accountUtils.js:290:12
oncommand@chrome://messenger/content/messenger.xul:1:1

Somewhat related to bug 1120089

Expected results:

The account is correctly set up.

See Also: → 1120089

Can you re-test with 68.5 (just out). There were a lot of fixes in this area since 68.2.2

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

Can you re-test with 68.5 (just out). There were a lot of fixes in this area since 68.2.2

Would love to, but I'm restricted to use what our IT dept. pushes down the install pipeline. I can ask them to update to 68.5, and will report back then.

Hi Stephen. What is your current status with retesting?

Flags: needinfo?(mail)
Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Flags: needinfo?(mail)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.