[SRU] Authentication constantly re-requested for Google

[Ads20000]

[Impact]

A recent server-side change with google e-mail accounts (gmail) means that thunderbird consistently fails to authenticate, prompting for the user's e-mail address and password over and over, without ever succeeding.
This has been fixed upstream and is tracked by https://bugzilla.mozilla.org/show_bug.cgi?id=1592407.

[Test Case]

In a clean environment, launch thunderbird and add an existing gmail account.
Thunderbird should auto-detect all the relevant parameters, and then an external webview should pop up to prompt for your e-mail address (it's not auto-filled, that's a separate issue that's also known upstream) and your password. After filling this in and authorizing thunderbird to access your e-mails, your account should be set up and thunderbird should start fetching e-mails from your inbox. Instead it fails to authenticate and displays the authentication pop up again.

[Regression Potential]

Low, as this is an official upstream point release that addresses only this regression (see https://www.thunderbird.net/en-US/thunderbird/60.9.1/releasenotes/).
The fix is minimal and self-contained (https://hg.mozilla.org/releases/comm-esr60/rev/56b6d1b50647143c25efe642b37b02f65f9c4343), if the bug is indeed confirmed to be fixed then it should be safe.

[Original Bug Description]

When I use Thunderbird, it keeps failing to connect with my Google (Gmail) accounts. It keeps asking for authentication via the web portal, I seem to successfully give Thunderbird authentication, but no messages come in and, soon afterwards, the web portal comes up asking for login again.

I am using OAuth2 (so this ( https://support.mozilla.org/en-US/questions/1201406 ) doesn't help.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: thunderbird 1:60.9.0+build1-0ubuntu0.19.04.1
ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: adam 3444 F.... pulseaudio
 /dev/snd/pcmC0D0p: adam 3444 F...m pulseaudio
BuildID: 20191007090404
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 30 14:56:50 2019
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite)
InstallationDate: Installed on 2017-08-03 (817 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
IpRoute:
 default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600
 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown
 169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown
 172.29.0.0/16 dev ztnfad2dd7 proto kernel scope link src 172.29.35.74
 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.11 metric 600
Locales: extensions.sqlite corrupt or missing
Plugins: Shockwave Flash - /usr/lib/browser-plugin-freshplayer-pepperflash/libfreshwrapper-flashplayer.so (browser-plugin-freshplayer-pepperflash)
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=60.9.0/20191007090404
RelatedPackageVersions: browser-plugin-freshplayer-pepperflash 0.3.9-0ubuntu4
RunningIncompatibleAddons: False
SourcePackage: thunderbird
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: Upgraded to disco on 2019-05-22 (161 days ago)
dmi.bios.date: 01/21/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: G1ETB0WW (2.70 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2347GU8
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrG1ETB0WW(2.70):bd01/21/2016:svnLENOVO:pn2347GU8:pvrThinkPadT430:rvnLENOVO:rn2347GU8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T430
dmi.product.name: 2347GU8
dmi.product.sku: LENOVO_MT_2347
dmi.product.version: ThinkPad T430
dmi.sys.vendor: LENOVO

[Ka-adm0n-v1 (ka-adm0n-v1)]

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

Steps to reproduce:

Clean install Thunderbird 68.2
- Add Gmail account
- Fill in Google Authentication popup window and allow app
- Fails at next window

Actual results:

Email is not synced at all

Warning saying:
Unable to log in at server. Probably wrong configuration, username or password

Password & username is correct

Expected results:

Login should Continue and account should start syncing email

[Ka-adm0n-v1 (ka-adm0n-v1)]

Tried older versions and latest Thunderbird beta 71 with the same results
Maybe Google has changed something with their OAuth2 requirements ?

Also should note the email is not auto-filled in the Google login popup (this used to be auto-filled)

[Ka-adm0n-v1 (ka-adm0n-v1)]

Created attachment 9105051
Log from login process

[Wls220spring (wls220spring)]

I test creating my Google IMAP account and Comcast POP3 account with every release candidate. I had no problem creating the accounts when testing the 68.2 candidate on Ubuntu 18.04.2 LTS. I still have that test profile and I can get mail on the account.

After seeing this bug report in my Gmail Bugzilla folder, I tested my 68.2 with a test profile on both Windows 10 and Ubuntu, and can reproduce the problem.

[Wls220spring (wls220spring)]

I just tested creating the account with a new test profile using 71.0b1 on Ubuntu 18.04.3 LTS and can reproduce.

I don't recall seeing the dialogs from Google that appear now when testing release candidates.

[Jorg K (jorgk)]

No changes in that area between TB 70 beta 4 and TB 71 beta 1. Does it still work with TB 68?

[Jorg K (jorgk)]

*** Bug 1592269 has been marked as a duplicate of this bug. ***

[Jorg K (jorgk)]

Sorry, you said 68.2.0. Hmm, looks like Google finally tightened the screw. Magnus and Andrei, do you know anything about this?

[Wls220spring (wls220spring)]

Created attachment 9105072
gmailerrorlog.txt

Creating an account in 68.2 with a test profile. No.

The user would normally get a dialog window with the email address already filled in and all they had to do was click "Next" to get to the dialog window to enter the password. Now I have to fill in my email or phone number.
Entering the email address and clicking next brings up the window to fill in the password, showing my email address and avatar associated with the account.
Typing in the password and clicking next brings up the "Mozilla Thunderbird Email wants to access your Google Account" dialog window.
Clicking the "Allow" button is where it fails.

No problem using my account in 68.2 or 70.0b1 or 72.0a1 with the production profiles on Windows 10 or Linux.

[Jorg K (jorgk)]

I've just confirmed it. After answering all the Google prompts incl. tying in a code received via SMS, the authentication fails :-( - An existing account still seems to work.

[Jorg K (jorgk)]

*** Bug 1592384 has been marked as a duplicate of this bug. ***

[Sancus (sancus)]

Yeah, I can't get gmail to auth either. The google oauth stuff looks the same to me, we still have the same authorizations we had before. There weren't any messages from Google either.

The only thing I can think of is that there is apparently a token rate limit, but it's not clear to me what that applies to, and there's no data for how many tokens we're granting per day, so I have no idea if it's even working right.

[Sancus (sancus)]

After setting mail.wizard.logging.dump to 'all' and mail.wizard.logging.console to 'all', when Thunderbird makes a request to https://www.googleapis.com/oauth2/v3/token the response is '400 bad request' with {"error": "invalid_grant", "error_description": "Malformed auth code."}

https://blog.timekit.io/google-oauth-invalid-grant-nightmare-and-how-to-fix-it-9f4efaf1da35

Googling makes it sound like it's a generic error that can apply to any number of scenarios. So I don't know. Maybe Fallen has some idea what could be going on here? Do we have Google contacts we can ask about this?

As of this moment, gmail auth is broken for all users and the error message may as well be 'something is wrong'.

[Wls220spring (wls220spring)]

I just came across this on the mozillaZine forum where the poster indicates using "normal password authentication" works.

http://forums.mozillazine.org/viewtopic.php?p=14848558#p14848558

[Sancus (sancus)]

Yes, you can set an app password using the "less secure apps" option in Google as a workaround. That won't fix the oauth bug itself, of course.

[Marco Gaiarin (marcogaio)]

I can confirm the bug, at least in 60 (i'm switching to 68 now...), 32bit, Win7.

Trouble happen if users change their password, and (i suppose) more generally on token change. If token is valid, all works as expected.

Obviously 'normal password' works if enabled on google site.

[Jorg K (jorgk)]

*** Bug 1592541 has been marked as a duplicate of this bug. ***

[Mkmelin+mozilla (mkmelin+mozilla)]

Looking at the docs at https://developers.google.com/identity/protocols/OAuth2InstalledApp we should probably update the urls as so.
```
 - "https://accounts.google.com/o/oauth2/auth",
 - "https://www.googleapis.com/oauth2/v3/token",
 + "https://accounts.google.com/o/oauth2/v2/auth",
 + "https://oauth2.googleapis.com/token",
```

Unfortunately, that doesn't help any :(

These are the relevant network requests. For the AccountChooser for whatever reason we end with a param to get sent to the legacy auth (https://accounts.google.com/signin/oauth/legacy/consent). I'd imagine that's the root of the problem.

curl 'https://accounts.google.com/o/oauth2/v2/auth?response_type=code&client_id=406964657835-aq8lmia8j95dhl1a2bvharmfk3t1hgqj.apps.googleusercontent.com&redirect_uri=http%3A%2F%2Flocalhost&scope=https%3A%2F%2Fmail.google.com%2F&login_hint=example%40gmail.com' -H 'User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:72.0) Gecko/20100101 Thunderbird/72.0a1' -H 'Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8' -H 'Accept-Language: en-US,en;q=0.5' --compressed -H 'DNT: 1' -H 'Connection: keep-alive' -H 'Upgrade-Insecure-Requests: 1'

curl 'https://accounts.google.com/signin/oauth?client_id=406964657835-aq8lmia8j95dhl1a2bvharmfk3t1hgqj.apps.googleusercontent.com&as=raOi9ApwBeyZIud8WPVzhg&<email address hidden>&destination=http://localhost&approval_state=!ChR2ZTJFaTBWQ2ZtMzhvMEVFOXhySxIfMDFiWFlJVWhNejhhOERFdWhZOThQY18xSm8zSDRSWQ%E2%88%99AJDr988AAAAAXbrIfhVE7FpoqoGhuBlX2DvLqjmU3VA6&oauthriskyscope=1&xsrfsig=ChkAeAh8T_oe9FxRgZIFTl3qVXN0iKZcn16rEg5hcHByb3ZhbF9zdGF0ZRILZGVzdGluYXRpb24SBXNvYWN1Eg9vYXV0aHJpc2t5c2NvcGU' -H 'User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:72.0) Gecko/20100101 Thunderbird/72.0a1' -H 'Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8' -H 'Accept-Language: en-US,en;q=0.5' --compressed -H 'Referer: https://accounts.google.com/o/oauth2/v2/auth?response_type=code&client_id=406964657835-aq8lmia8j95dhl1a2bvharmfk3t1hgqj.apps.googleusercontent.com&redirect_uri=http%3A%2F%2Flocalhost&scope=https%3A%2F%2Fmail.google.com%2F&login_hint=example%40gmail.com' -H 'DNT: 1' -H 'Connection: keep-alive' -H 'Cookie: OCAK=fwSdeZHWp9M0a0jvnbwWEu57NPSzYGYQXIyvq3awhbw' -H 'Upgrade-Insecure-Requests: 1' -H 'TE: Trailers'

curl 'https://accounts.google.com/signin/oauth?client_id=406964657835-aq8lmia8j95dhl1a2bvharmfk3t1hgqj.apps.googleusercontent.com&as=raOi9ApwBeyZIud8WPVzhg&<email address hidden>&destination=http://localhost&approval_state=!ChR2ZTJFaTBWQ2ZtMzhvMEVFOXhySxIfMDFiWFlJVWhNejhhOERFdWhZOThQY18xSm8zSDRSWQ%E2%88%99AJDr988AAAAAXbrIfhVE7FpoqoGhuBlX2DvLqjmU3VA6&oauthriskyscope=1&xsrfsig=ChkAeAh8T_oe9FxRgZIFTl3qVXN0iKZcn16rEg5hcHByb3ZhbF9zdGF0ZRILZGVzdGluYXRpb24SBXNvYWN1Eg9vYXV0aHJpc2t5c2NvcGU' -H 'User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:72.0) Gecko/20100101 Thunderbird/72.0a1' -H 'Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8' -H 'Accept-Language: en-US,en;q=0.5' --compressed -H 'Referer: https://accounts.google.com/o/oauth2/v2/auth?response_type=code&client_id=406964657835-aq8lmia8j95dhl1a2bvharmfk3t1hgqj.apps.googleusercontent.com&redirect_uri=http%...

[Vseerror (vseerror)]

*** Bug 1592552 has been marked as a duplicate of this bug. ***

[Vseerror (vseerror)]

*** Bug 1592585 has been marked as a duplicate of this bug. ***

[Sherman-m (sherman-m)]

For the authentication step, override the useragent and change it to Firefox.

[Vseerror (vseerror)]

*** Bug 1592590 has been marked as a duplicate of this bug. ***

[Jorg K (jorgk)]

As per comment #20 and https://github.com/kewisch/gdata-provider/issues/26#issuecomment-547994463, setting general.useragent.compatMode.firefox to true allows IMAP access again. Not tested for gData, but no reason to distrust the GitHub post.

[Pnul (pnul)]

I tested the workaround with gData for Calendar and it worked as expected.

[Marco Gaiarin (marcogaio)]

I confirm too, workaround work!
(tested win32 60.9.0 version)

[Jorg K (jorgk)]

Created attachment 9105309
1592407-github-fix.patch

As far as I can tell, this works. I claim no merit, all I did was copy/paste.

[Richard Leger (richard-leger)]

Jorg, would Bug 1592342 depends on this bug?

[Jorg K (jorgk)]

*** Bug 1592342 has been marked as a duplicate of this bug. ***

[Jorg K (jorgk)]

Thanks, Richard, also for writing up the nice summary over in bug 1592342. We can collect the duplicates here.

[Thee-chicago-wolf (thee-chicago-wolf)]

A bit off the wagon but wanted to mention it in case anyone else found this bug and is on TB 70.0b4 with Lightning+Provider for Google Calendar 70.b4. Flipping general.useragent.compatMode.firefox=true on TB 70.0b4 has *totally* resolve a weird stuttering / lagging / slowness issue I've been experiencing ever since moving to 70.0b and now my work machine is snappy and responsive again. Sorry for the noise.

[Jorg K (jorgk)]

Comment on attachment 9105309
1592407-github-fix.patch

:KWan suggested to use dlob <email address hidden> an author from
https://github.com/kewisch/gdata-provider/commit/216481167586897b5e0949617aca1ee482e5c105.patch

[Jorg K (jorgk)]

And more comments from IRC:
20:48:13 - Fallen: I'd recommend to use https://developer.mozilla.org/en-US/docs/Web/API/URLSearchParams in the Thunderbird patch
20:50:29 - pmorris has left the room (Quit: Ping timeout: 121 seconds).
20:50:59 - Fallen: Something like let url = new URL(aData); let params = new URLSearchParams((url.search || url.hash).substr(1)); and then use params.get("code") instead of results.code
20:51:29 - Fallen: possibly find out if they are using the hash or the search part of the url and then just use the right thing
20:52:24 - Fallen: Maybe a Cu.importGlobalProperties for URL and/or URLSearchParams

[Mkmelin+mozilla (mkmelin+mozilla)]

Comment on attachment 9105309
1592407-github-fix.patch

Review of attachment 9105309:
-----------------------------------------------------------------

This indeed works, and it's a small fix. We can do other improvements later

[Pulsebot (pulsebot)]

Pushed by <email address hidden>:
https://hg.mozilla.org/comm-central/rev/57532519642e
Port OAuth2 decoding fix from gData add-on. r=mkmelin DONTBUILD

[Jorg K (jorgk)]

TB 71 beta 2:
https://hg.mozilla.org/releases/comm-beta/rev/e4607a1592d21563c3daa8ea441519b63fb5ba62

[Jorg K (jorgk)]

TB 68.2.1 ESR:
https://hg.mozilla.org/releases/comm-esr68/rev/afe823a25c03b91217ff767b360f14e289f3671d

[Jorg K (jorgk)]

TB 60.9.1 ESR:
https://hg.mozilla.org/releases/comm-esr60/rev/56b6d1b50647143c25efe642b37b02f65f9c4343

[Jorg K (jorgk)]

Seems to be working in the 68.2.1 build.

[Mkmelin+mozilla (mkmelin+mozilla)]

Does someone remember if the email (user) used to get pre-filled properly? (It's not atm.)

When testing this fix we should remember to check the other providers too are working.

[G-lists (g-lists)]

(In reply to Magnus Melin [:mkmelin] from comment #38)
> Does someone remember if the email (user) used to get pre-filled properly? (It's not atm.)

It is filled in automatically, if the workaround as proposed in comments #20, #22 and #29 is done. I believe to remember that it has been done automatically before Google's recent change, Is I noticed that now I had to check for the user as I do have multiple accounts.

[Jorg K (jorgk)]

*** Bug 1592940 has been marked as a duplicate of this bug. ***

[Wls220spring (wls220spring)]

*** Bug 1593076 has been marked as a duplicate of this bug. ***

[Wls220spring (wls220spring)]

*** Bug 1593081 has been marked as a duplicate of this bug. ***

[Mozilla-bugzilla-f (mozilla-bugzilla-f)]

(In reply to Magnus Melin [:mkmelin] from comment #38)
> Does someone remember if the email (user) used to get pre-filled properly? (It's not atm.)
>
> When testing this fix we should remember to check the other providers too are working.

FWIW, in 68.2.0, it *is* possible to set up a new Yahoo! Mail account with OAuth, and the username is prefilled in the web login popup.

[Jorg K (jorgk)]

You misunderstood: We wanted to test whether TB 68.2.1 with the modification affected OAuth2 authentication of Yahoo, Yandex or others. Apparently that's not the case.

[Mozilla-bugzilla-f (mozilla-bugzilla-f)]

No, I didn't misunderstand. I was just giving a data point that freshly setting up a Yahoo! Mail account with OAuth *did* work in 68.2.0, and the account name was prefilled, unlike with Gmail. The fact that I wasn't talking about 68.2.1 is why I led with "FWIW". Glad to hear the change for Google didn't break Yahoo! or others.

[Steven Maude (stevenmaude)]

It's a known bug in Thunderbird. It's fixed in the latest 68.2.1 release: see https://www.thunderbird.net/en-US/thunderbird/68.2.1/releasenotes/

In the meantime, until a version of Thunderbird with the fix is available for Ubuntu, there's a Mozilla support thread: https://support.mozilla.org/en-US/questions/1271710 that in turn points to this GitHub issue: https://github.com/kewisch/gdata-provider/issues/26#issuecomment-547994463 (whew!) that finally (whew!) suggests:

"Changing "general.useragent.compatMode.firefox" preference to true fixes the issue, google authentication works again."

[Z-bugzilla (z-bugzilla)]

Why is 60.9.1 not released? From a supporters point of view you should not force the upgrade from 60.* to 68.* in this context.

[Vseerror (vseerror)]

(In reply to Alex Ihrig from comment #46)
> Why is 60.9.1 not released? From a supporters point of view you should not force the upgrade from 60.* to 68.* in this context.

Good questions.
a) we're not forcing updates. we're using the normal update process.
b) we're not doing 60.9.1 as a first choice because what if something goes wrong with that update, or it is insuficient to fix the issue? 68 is a better platform from which to iterate
c) we planned to update users from 60 to 68 anyway

[Mozilla-bugzilla-f (mozilla-bugzilla-f)]

Nevertheless, since 68.x breaks compatibility with so many extensions, many of which will never be updated, it would be a nice gesture to release a 60.9.1, given how severely Gmail and Google Calendar are broken on all prior versions. You wouldn't have to rejigger the update process that's already set to lift people up to the 68.x branch; you could simply make 60.9.1 available under https://archive.mozilla.org/pub/thunderbird/releases/ for those who know to look there.

Of the 5 add-ons that I use:
* 1 was updated (I haven't yet had time to test it).
* 1 was reimplemented as a separate MailExtension by a different author (again, haven't yet had time to test the new version to confirm everything still works).
* 1 was apparently updated to the new packaging requirements, but doesn't actually function.
* 2 seem to have been abandoned by their authors and there's a good chance they'll never be updated or reimplemented.

So with only 2 out of 5 of my add-ons (at least theoretically) working, it'd be nice to be able to keep a working version of 60.x around, and just be aware not to view untrusted emails with it, since it won't be getting any more security updates.

[Jorg K (jorgk)]

Out of interest: List those five add-ons.

[Sebastien Bacher (seb128)]

The TB 68 update is being worked on that should address this issue

[defaria (andrew-defaria)]

(In reply to Wayne Mery (:wsmwk) from comment #47)
> (In reply to Alex Ihrig from comment #46)
> > Why is 60.9.1 not released? From a supporters point of view you should not force the upgrade from 60.* to 68.* in this context.
>
> Good questions.
> a) we're not forcing updates. we're using the normal update process.
> b) we're not doing 60.9.1 as a first choice because what if something goes wrong with that update, or it is insuficient to fix the issue? 68 is a better platform from which to iterate
> c) we planned to update users from 60 to 68 anyway

You seemed to have forced the update on me! I woke up this morning to a computer that had Thunderbird 60.x running and a dialog box saying to click here to restart Thunderbird with this new (broken) version of Thunderbird. I didn't ask for this ergo I was forced!

Note I had been running the new Thunderbird (68) on a laptop but not my desktop. I was not impressed. Many extensions were broken so I was waiting for them to be updated and working before I would update my desktop but you (thunderbird not you Dan) forced this update on me. Now I'll try to downgrade to 69.0b4...

[defaria (andrew-defaria)]

Ugh, tried 69.0b4 and it screwed up my entire thunderbird installation! Now I have to recover. Thanks guys!

[Anjeyelf (anjeyelf)]

In 'Options' > 'Update':
I have selected 'Check for updates, but let me choose whether to install them'
Thunderbird does as expected. I see a pop up saying there is a new update and asking if I want to update.

If you have the 'Automatically install updates' option selected - note this is selected by default - then Thunderbird will auto update at the appropriate time. You would then prompted to restart.

What do you mean by 'this new (broken) version' ? Do you only mean you are using addons created by various users/authors and those addons are not working ?
If yes, then Thunderbird is not broken. You may discover many addons can be updated / some are in the pipline / some issues can be fixed by alternative ways. Suggest you ask a question in the Support Forum to see if something can be done.

Or
are you refering to the bug discussed in this bug report which claims the update has fixed?
Are you using the up to date addon: Provider for Google Calendar version 68.0
What issue are you experiencing with the Imap gmail account?

[Jorg K (jorgk)]

(In reply to Andrew DeFaria from comment #50)
> Many extensions were broken so I was waiting for them to be updated and working before I would update my desktop but you (thunderbird not you Dan) forced this update on me. Now I'll try to downgrade to 69.0b4...

Extension authors "only" had about half a year time to update their extensions. IMHO, what isn't updated by now should be considered unmaintained and not fit for use any more.

I really don't understand why after an undesired automated upgrade from 60 to 68 you'd go even further and install a 69 beta 4 version. And then blame others for that "screw up".

[defaria (andrew-defaria)]

It's a loss of functionality nonetheless. In this instance my entire calendar is inoperable! I didn't ask for that so yes I tried to go to a version that might have a chance of getting my functionality back. There was a post that hinted that that 69.01b might work. When I went to the download area I saw 69.04b so I tried that. What I ended up with was a bare-bones installation - no email accounts, no add-ons, nothing.

Have you ever heard of the saying "If it ain't broke then don't fix it"? This wasn't broken until you broke it. And there appears to be no (simple) way back. I didn't ask for my email client of some 17 years to break so horribly. In fact, I was purposely avoiding it by testing it out on another system (laptop). I didn't even get a chance to say "Thanks but no thanks, I'll stay with what is working". AFAICT I was forced into this so Dan's statement of not forcing updates is, AFAICT, false. I've been using Thunderbird since before it was Thunderbird. Yes there are times when add-ons fail to work initially but never has it been this broken WRT Add-Ons in the 17 years I've been using Thunderbird.

And by broke, I do not mean just the add-ons. Granted Google Provider seems busted with OAuth. Google Provider keeps asking me to log in and afterward does nothing but ask me again so yes that's this bug here. I have Version 68 of Google Provider.

What I meant by my environment being screwed up is that when run Thunderbird shows me a basic setup, no accounts, no add-ons, nothing. I'm coming to find out it seems to have created a blank profile instead of using my existing one. But my existing one was still there so using the ProfileManager I was able to log in with the correct profile and I'm cleaning that up.

[Jorg K (jorgk)]

"Google Provider" is a 3rd-party add-on that hasn't been updated to work with the new Google OAuth2 scheme. Complain to its author:
https://addons.thunderbird.net/en-GB/thunderbird/addon/provider-for-google-calendar/
https://github.com/kewisch/gdata-provider/

In certain upgrade situations it can happen that TB doesn't recognise your existing profile and creates a new one. You can select the profile want in the profile manager or via "Help > Troubleshooting Information", about:profiles. We're working on improving that.

To my knowledge, Thunderbird's Calender Lightning will work in any version you install.

For security reasons we must eventually discontinue old versions and migrate users to the new supported version. The update from 60 to 68 has been a bit bumpy for some users which we regret.

[Vseerror (vseerror)]

*** Bug 1594008 has been marked as a duplicate of this bug. ***

[Z-bugzilla (z-bugzilla)]

(In reply to Andrew DeFaria from comment #54)
> And by broke, I do not mean just the add-ons. Granted Google Provider seems busted with OAuth. Google Provider keeps asking me to log in and afterward does nothing but ask me again so yes that's this bug here. I have Version 68 of Google Provider.

1.) Users should also complain to Google, if there are always technical details changed without specific announcement (to the affected users). This would also be Google's task to inform users - not just developers.
2.) Google Provider must be updated to version 68.2.1, to have the bug in the addon fixed.

> What I meant by my environment being screwed up is that when run Thunderbird shows me a basic setup, no accounts, no add-ons, nothing. I'm coming to find out it seems to have created a blank profile instead of using my existing one. But my existing one was still there so using the ProfileManager I was able to log in with the correct profile and I'm cleaning that up.

That's the bad UX, when we force users to do a major upgrade instead of providing a small bugfix update to 60.9.1 (which is now available today - thanks!).

[Unicorn-consulting (unicorn-consulting)]

(In reply to Andrew DeFaria from comment #54)

> Have you ever heard of the saying "If it ain't broke then don't fix it"? This wasn't broken until you broke it. And there appears to be no (simple) way back. I didn't ask for my email client of some 17 years to break so horribly. In fact, I was purposely avoiding it by testing it out on another system (laptop). I didn't even get a chance to say "Thanks but no thanks, I'll stay with what is working". AFAICT I was forced into this so Dan's statement of not forcing updates is, AFAICT, false. I've been using Thunderbird since before it was Thunderbird. Yes there are times when add-ons fail to work initially but never has it been this broken WRT Add-Ons in the 17 years I've been using Thunderbird.

I do not see your reply to Anje on your settings. Was the update contrary to your settings? This is a very core question that has been glossed over.

> What I meant by my environment being screwed up is that when run Thunderbird shows me a basic setup, no accounts, no add-ons, nothing. I'm coming to find out it seems to have created a blank profile instead of using my existing one. But my existing one was still there so using the ProfileManager I was able to log in with the correct profile and I'm cleaning that up.

That is called profile per install and is the "new" way things are done, thank you Mozilla core developers.

[Mozilla-bugzilla-f (mozilla-bugzilla-f)]

(In reply to Jorg K (GMT+2) from comment #49)
> Out of interest: List those five add-ons.

I intentionally did not list them because I prefer not to give out exact details of my configuration when posting under my real name, particularly for pieces of software that are likely to get no more security updates. However, if you want to send me a private message, I'll give you the list.

(In reply to Andrew DeFaria from comment #50)
> Many extensions were broken so I was waiting for them to be updated and working before I would update my desktop but you (thunderbird not you Dan) forced this update on me.

(In reply to Andrew DeFaria from comment #54)
> AFAICT I was forced into this so Dan's statement of not forcing updates is, AFAICT, false.

Andrew, I'm afraid you've got me confused with someone else. Note that the From information for each comment is in a header, not a footer.

(In reply to Jorg K (GMT+2) from comment #53)
> Extension authors "only" had about half a year time to update their extensions. IMHO, what isn't updated by now should be considered unmaintained and not fit for use any more.

"Unmaintained" and "not fit for use any more" are not synonymous. Many Firefox and Thunderbird add-ons have continued working properly for years after their last update. Also, the Thunderbird ecosystem is a lot smaller than the Firefox one, so chances are much greater of a particular specialized add-on being the only one that implements a particular bit of functionality, thus there is a greater chance of needing to rely on a piece of software that hasn't been updated lately. And only a small minority of Thunderbird add-ons have the potential for network-facing security holes, so the argument against continuing to use unmaintained software for security reasons doesn't apply to most of them.

(In reply to Alex Ihrig from comment #57)
> That's the bad UX, when we force users to do a major upgrade instead of providing a small bugfix update to 60.9.1 (which is now available today - thanks!).

Oh! Thanks for the heads-up on that, Alex! I see that not only was it made available under https://archive.mozilla.org/pub/thunderbird/releases/60.9.1/ as I was suggesting, but doing an update in 60.9.0 now updates to 60.9.1 instead of 68.2.0. Very cool; thanks, guys!

(In reply to Matt from comment #58)
> > What I meant by my environment being screwed up is that when run Thunderbird shows me a basic setup, no accounts, no add-ons, nothing. I'm coming to find out it seems to have created a blank profile instead of using my existing one. But my existing one was still there so using the ProfileManager I was able to log in with the correct profile and I'm cleaning that up.
>
> That is called profile per install and is the "new" way things are done, thank you Mozilla core developers.

Ugh, and it doesn't even ask you at install-time if you want to go with your old settings or a fresh profile, the way that such software as the Nvidia drivers, VLC, etc. does it? What a horrendously hostile user experience.

[Vseerror (vseerror)]

60.9.1 is released

[Devschrott (devschrott)]

i'm still (or better: recently) having the bug (pretty sure it's the one?)

"auth error while connecting to imap.gmail.com"

never had it before, it just started seemingly yesterday.
please someone help, almost none of my mail adresses work, what can i do? compatmode.firefox had no effect

[Richard Leger (richard-leger)]

devschrott,
Which version of TB and Google Provider are you using?

[dj_segfault (djsegfault)]

I updated to Thunderbird 68.2.1, Lightning 68.2.1, and Provider for Google Calendar 68.2.1, which are the latest available to me under Ubuntu, and I still have the problem. After the google login, and I click Allow, I get the "Locate your calendar" dialog box, with no calendars in it. The debugging console says:
`[Exception... "null" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: resource://gdata-provider/modules/gdataSession.jsm :: login/authFailed< :: line 284" data: no] gdataSession.jsm:284:33`

Note when I tried this in the official release 60.9.0 I got a different error:
`[HTTP/2.0 400 Bad Request 92ms]
Lightning:[calGoogleSession] Authentication failure: {
  "error": "invalid_grant",
  "error_description": "Malformed auth code."
} gdataSession.jsm:272
[Exception... "invalid_grant" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: resource://gdata-provider/modules/gdataSession.jsm :: login/authFailed< :: line 274" data: no]`

Note that I was able to log into google/gmail in my browser with the exact same credentials (as in copied/pasted so I know they were identical to what I tried in Lightning

[dj_segfault (djsegfault)]

(In reply to David Kramer from comment #63)
> I updated to Thunderbird 68.2.1, Lightning 68.2.1, and Provider for Google Calendar 68.2.1, which are the latest available to me under Ubuntu, and I still have the problem. After the google login, and I click Allow, I get the "Locate your calendar" dialog box, with no calendars in it. The debugging console says:
`Lightning: [calGoogleSession] Authentication failure: undefined gdataSession.jsm:282
[Exception... "null" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: resource://gdata-provider/modules/gdataSession.jsm :: login/authFailed< :: line 284" data: no] gdataSession.jsm:284:33`
>
> Note when I tried this in the official release 60.9.0 I got a different error:
> `[HTTP/2.0 400 Bad Request 92ms]
> Lightning:[calGoogleSession] Authentication failure: {
> "error": "invalid_grant",
> "error_description": "Malformed auth code."
> } gdataSession.jsm:272
> [Exception... "invalid_grant" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: resource://gdata-provider/modules/gdataSession.jsm :: login/authFailed< :: line 274" data: no]`
>
> Note that I was able to log into google/gmail in my browser with the exact same credentials (as in copied/pasted so I know they were identical to what I tried in Lightning

[Jorg K (jorgk)]

The easy thing first: TB 60.9.0 will not work (but TB 60.9.1 will).

We just found out that some distributions may have built "Provider for Google Calendar" from the wrong repository :-(

The correct add-on can be obtained here: https://addons.thunderbird.net/en-GB/thunderbird/addon/provider-for-google-calendar/

It's also called 68.2.1 but is may be different. If you're able to open/unpack the XPI file which is just a ZIP file, check the following file:
Open modules/OAuth2.jsm and check line 26: Do you have the working version which reads: `result[key] = decodeURIComponent(value);` ?

[Axel99092 (axel99092)]

But TB 60.9.0 say that provider_for_google_calendar-68.2.1-tb.xpi is not compatible with TB 60.9.0 and cannot be installed.

[defaria (andrew-defaria)]

I've backtracked to TB 60.9.1. When running 60.9.1 I was able to "update" Provider for Google Calendar and it works. The add on says it's version 4.4.2.

I'm gonna stay here on 60.9.x until this blows over.

[dj_segfault (djsegfault)]

(In reply to Jorg K (GMT+2) from comment #65)
> The easy thing first: TB 60.9.0 will not work (but TB 60.9.1 will).
>
> We just found out that some distributions may have built "Provider for Google Calendar" from the wrong repository :-(
>
> The correct add-on can be obtained here: https://addons.thunderbird.net/en-GB/thunderbird/addon/provider-for-google-calendar/
>
> It's also called 68.2.1 but is may be different. If you're able to open/unpack the XPI file which is just a ZIP file, check the following file:
> Open modules/OAuth2.jsm and check line 26: Do you have the working version which reads: `result[key] = decodeURIComponent(value);` ?

Yes, my version has that line.

[Jorg K (jorgk)]

> Yes, my version has that line.

Then it should work. That version of the add-on came from the distro?

[dj_segfault (djsegfault)]

(In reply to Jorg K (GMT+2) from comment #69)
> > Yes, my version has that line.
>
> Then it should work. That version of the add-on came from the distro?

No, I added it through the in app "Manage your extensions". Ubuntu doesn't have the Thunderbird extensions as .deb files

[Llh-n (llh-n)]

(In reply to paul from comment #23)
> I tested the workaround with gData for Calendar and it worked as expected.

Confirmed! /Lars

[Timo Jyrinki (timo-jyrinki)]

Reflecting current status per series, adjust as needed.

The upstream bug says fixed in 68.2.1, which is currently in proposed for eoan and bionic.

[Olivier Tilloy (osomon)]

Thanks for triaging Timo.

[dj_segfault (djsegfault)]

(In reply to llh from comment #71)
> (In reply to paul from comment #23)
> > I tested the workaround with gData for Calendar and it worked as expected.
>
> Confirmed! /Lars

What is this workaround you mention? I'm still stuck

[Jorg K (jorgk)]

First of all, TB 68.2.1 with gData 68.2.1 installed from https://addons.thunderbird.net/en-GB/thunderbird/addon/provider-for-google-calendar/ should work. The workaround is described in comment #22.

[Jeremy Winick (winickjr)]

I know this is fixed in Thunderbird 69.0.1 and 68.2. can this be put into
the repository for Ubuntu 16.04 LTS?
Jeremy

On Tue, Nov 19, 2019, 10:41 PM Olivier Tilloy <email address hidden>
wrote:

> ** Changed in: thunderbird (Ubuntu Xenial)
> Status: In Progress => Fix Committed
>
> ** Changed in: thunderbird (Ubuntu Disco)
> Status: In Progress => Fix Committed
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1852540).
> https://bugs.launchpad.net/bugs/1850651
>
> Title:
> Authentication constantly re-requested for Google
>
> Status in Mozilla Thunderbird:
> Fix Released
> Status in thunderbird package in Ubuntu:
> Fix Released
> Status in thunderbird source package in Xenial:
> Fix Committed
> Status in thunderbird source package in Bionic:
> Fix Committed
> Status in thunderbird source package in Disco:
> Fix Committed
> Status in thunderbird source package in Eoan:
> Fix Committed
> Status in thunderbird source package in Focal:
> Fix Released
>
> Bug description:
> When I use Thunderbird, it keeps failing to connect with my Google
> (Gmail) accounts. It keeps asking for authentication via the web
> portal, I seem to successfully give Thunderbird authentication, but no
> messages come in and, soon afterwards, the web portal comes up asking
> for login again.
>
> I am using OAuth2 (so this ( https://support.mozilla.org/en-
> US/questions/1201406 ) doesn't help.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 19.04
> Package: thunderbird 1:60.9.0+build1-0ubuntu0.19.04.1
> ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
> Uname: Linux 5.0.0-32-generic x86_64
> AddonCompatCheckDisabled: False
> ApportVersion: 2.20.10-0ubuntu27.1
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: adam 3444 F.... pulseaudio
> /dev/snd/pcmC0D0p: adam 3444 F...m pulseaudio
> BuildID: 20191007090404
> Channel: Unavailable
> CurrentDesktop: ubuntu:GNOME
> Date: Wed Oct 30 14:56:50 2019
> Extensions: extensions.sqlite corrupt or missing
> ForcedLayersAccel: False
> IfupdownConfig:
> # interfaces(5) file used by ifup(8) and ifdown(8)
> auto lo
> iface lo inet loopback
> IncompatibleExtensions: Unavailable (corrupt or non-existant
> compatibility.ini or extensions.sqlite)
> InstallationDate: Installed on 2017-08-03 (817 days ago)
> InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
> IpRoute:
> default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600
> 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown
> 169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown
> 172.29.0.0/16 dev ztnfad2dd7 proto kernel scope link src 172.29.35.74
> 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.11
> metric 600
> Locales: extensions.sqlite corrupt or missing
> Plugins: Shockwave Flash -
> /usr/lib/browser-plugin-freshplayer-pepperflash/libfreshwrapper-flashplayer.so
> (browser-plugin-freshplayer-pepperflash)
> PrefSources: prefs.js
> Profiles: Profile0 (Default) - LastVersion=60.9....

[Olivier Tilloy (osomon)]

Yes it will, I am working on it.

[Mkmelin+mozilla (mkmelin+mozilla)]

For posterity: the data that needed to be different was "4/" vs. "4%2F" for the code parameter. It needed to be the latter now. Presumably there was no slash in the code earlier so it would have worked without decoding.

[Vseerror (vseerror)]

*** Bug 1597938 has been marked as a duplicate of this bug. ***

[Timo Aaltonen (tjaalton)]

Hello Ads20000, or anyone else affected,

Accepted thunderbird into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/thunderbird/1:60.9.1+build1-0ubuntu0.19.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Timo Aaltonen (tjaalton)]

Hello Ads20000, or anyone else affected,

Accepted thunderbird into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/thunderbird/1:60.9.1+build1-0ubuntu0.16.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Gyula (gyulank)]

But I wrote that I downloaded the newest version and that is working.
Just i need to open from extracted folder. I wrote for the Ubuntu
replace this version in 20.04 because this builded version is wrong. So
now I need to download and try an older version too?

2019. 11. 29. 12:52 keltezéssel, Timo Aaltonen írta:.
> Hello Ads20000, or anyone else affected,
>
> Accepted thunderbird into xenial-proposed. The package will build now
> and be available at
> https://launchpad.net/ubuntu/+source/thunderbird/1:60.9.1+build1-0ubuntu0.16.04.1
> in a few hours, and then in the -proposed repository.
>
> Please help us by testing this new package. See
> https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
> to enable and use -proposed. Your feedback will aid us getting this
> update out to other Ubuntu users.
>
> If this package fixes the bug for you, please add a comment to this bug,
> mentioning the version of the package you tested and change the tag from
> verification-needed-xenial to verification-done-xenial. If it does not
> fix the bug for you, please add a comment stating that, and change the
> tag to verification-failed-xenial. In either case, without details of
> your testing we will not be able to proceed.
>
> Further information regarding the verification process can be found at
> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
> advance for helping!
>
> N.B. The updated package will be released to -updates after the bug(s)
> fixed by this package have been verified and the package has been in
> -proposed for a minimum of 7 days.
>
> ** Changed in: thunderbird (Ubuntu Xenial)
> Status: In Progress => Fix Committed
>
> ** Tags added: verification-needed-xenial
>

[Olivier Tilloy (osomon)]

Gyula, in duplicate bug #1854440, you wrote that version 60.3.0 in Ubuntu 20.04 isn't working. There is no such version in Ubuntu 20.04. If you're using the official Ubuntu repositories and have updated your system, you should have version 68.2.2 (https://launchpad.net/ubuntu/+source/thunderbird/1:68.2.2+build1-0ubuntu1).

[Gyula (gyulank)]

I updating manual several times a day. And other interesting thing is
that installed the vlc and in the softwares the vlc is unchecked.

2019. 12. 01. 12:18 keltezéssel, Olivier Tilloy írta:
> Gyula, in duplicate bug #1854440, you wrote that version 60.3.0 in
> Ubuntu 20.04 isn't working. There is no such version in Ubuntu 20.04. If
> you're using the official Ubuntu repositories and have updated your
> system, you should have version 68.2.2
> (https://launchpad.net/ubuntu/+source/thunderbird/1:68.2.2+build1-0ubuntu1).
>

[Olivier Tilloy (osomon)]

Gyula, it appears you're using the snap version of thunderbird. The edge channel has version 68.2.2, which you can switch to with:

    snap refresh thunderbird --edge

[Łukasz Zemczak (sil2100)]

Hello Ads20000, or anyone else affected,

Accepted cargo into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cargo/0.37.0-3ubuntu1~19.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Łukasz Zemczak (sil2100)]

Hello Ads20000, or anyone else affected,

Accepted cargo into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cargo/0.37.0-3ubuntu1~16.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted thunderbird (1:60.9.1+build1-0ubuntu0.19.04.1) for disco have finished running.
The following regressions have been reported in tests triggered by the package:

enigmail/2:2.0.9+ds1-2 (i386, arm64, amd64, ppc64el, armhf)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/disco/update_excuses.html#thunderbird

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Gyula (gyulank)]

Befaore I got your messages I reinstalled the thunderbird in synaptic.
Interesting reinstalled because the synapric wrote that the newest was
installed. But after reinstalled I have the newest version and it's
working. But in Software center stay the old version if I searching.

2019. 12. 04. 2:55 keltezéssel, Ubuntu SRU Bot írta:
> All autopkgtests for the newly accepted thunderbird (1:60.9.1+build1-0ubuntu0.19.04.1) for disco have finished running.
> The following regressions have been reported in tests triggered by the package:
>
> enigmail/2:2.0.9+ds1-2 (i386, arm64, amd64, ppc64el, armhf)
>
>
> Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
>
> https://people.canonical.com/~ubuntu-archive/proposed-
> migration/disco/update_excuses.html#thunderbird
>
> [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
>
> Thank you!
>

[Juan Jose Pablos (cheche)]

please revert my last change... I was searching if this was released for 16.04 and clicked by mistake.

[Timo Jyrinki (timo-jyrinki)]

bionic (18.04 LTS) was fixed mid-January, disco (19.04) and xenial (16.04 LTS) have the updated versions (minor fix version https://www.thunderbird.net/en-US/thunderbird/60.9.1/releasenotes/) still stuck in proposed since end of November.

[Olivier Tilloy (osomon)]

Tested in a fully up-to-date xenial amd64 VM. I verified that the version currently in xenial-updates (1:60.9.0+build1-0ubuntu0.16.04.2) exhibits the problem. I then enabled xenial-proposed, installed the thunderbird update (1:60.9.1+build1-0ubuntu0.16.04.1) and verified that the problem is fixed.

I'm sorry this fell off my radar and remained there lingering for so long.

[Łukasz Zemczak (sil2100)]

The verification of the Stable Release Update for thunderbird has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package thunderbird - 1:60.9.1+build1-0ubuntu0.16.04.1

---------------
thunderbird (1:60.9.1+build1-0ubuntu0.16.04.1) xenial; urgency=medium

  * New upstream stable release (60.9.1build1) (LP: #1850651)

 -- Olivier Tilloy <email address hidden> Tue, 19 Nov 2019 17:26:46 +0100

[Vseerror (vseerror)]

*** Bug 1616470 has been marked as a duplicate of this bug. ***

[Alexmyspam1 (alexmyspam1)]

try this scheduling API https://onsched.com/