Why so many (6) "Password Reuired" dialogs?
I am running Thunderbird on Win 8.1 with Password Manager enabled with a master password. I am also running Lightning and Provider for Google Calendar. I am accessing 3 calendars of mine plus a couple of general calendars. When I start Thunderbird I have to sign on 6 times. This seems ridiculous. Why have a Master Password if other add-0ns can't use it?
It should be a simple matter to set a flag if the user has entered a valid Master Password. If the flag is set, the add-ons should know that they can use their stored passwords without bothering the user.
What am I missing?
Выбранное решение
Hi Zenos,
First, many thanks for pointing me toward startupmaster. That's the type of behavior I was looking for.
Re: version, I am running 31.4. Last week, in an attempt to see if residue from prior installs was preventing TB from functioning correctly, I did a complete uninstall, a reboot, deletion of all TB files and profiles, another reboot then a reinstall. I came back just as I reported in my initial post. It has not been fixed
Again, thanks so very much.
Прочитайте этот ответ в контексте 👍 0Все ответы (3)
What version of Thunderbird are you using? I thought this had been fixed…
I use this add-on:
https://addons.mozilla.org/en-US/thunderbird/addon/startupmaster/
partially because it fixes the multiple prompt problem.
Выбранное решение
Hi Zenos,
First, many thanks for pointing me toward startupmaster. That's the type of behavior I was looking for.
Re: version, I am running 31.4. Last week, in an attempt to see if residue from prior installs was preventing TB from functioning correctly, I did a complete uninstall, a reboot, deletion of all TB files and profiles, another reboot then a reinstall. I came back just as I reported in my initial post. It has not been fixed
Again, thanks so very much.
Изменено
I'm having the same problem. I'm using TB 38.1.0, and Lightning. I just added the Google Calender provider and everytime I open TB and Lightning, I have a bunch of Master Password requests.
I see the add-on to stop it, but why would we have to do that? Isn't there a fix?