After upgrade to 78.11.0, unable to add ANY add-on [involves Linux-Distro Fedora]
Categories
(Thunderbird :: Add-Ons: General, defect)
Tracking
(Not tracked)
People
(Reporter: douglasroyer, Unassigned)
Details
Attachments
(1 file)
26.32 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:89.0) Gecko/20100101 Firefox/89.0
Steps to reproduce:
After fedora updated my thunderbird. Thunderbird hung. I started with a new ~/.thunderbird directory. Now I am unable to add ANY add-on. The pop-up window shows the permission box (Cancel/Add) buttons do NOTHING.
The pop-up never reacts to Add or Cancel. And there is no way to close the pop-up, until I exit Thunderbird.
I have tried several add-on's they all fail to install.
Actual results:
I can no longer add any add-on to thunderbird.
This happened several months ago to version 68. Then after I restarted thunderbird, everything worked.
I can not find any bug or search result where anyone else has this problem.
Expected results:
The "Add" button should add the add-on, then close the window.
The "Cancel" button should close the window.
Comment 1•4 years ago
|
||
WFM on Win10, 78.11.0 (32-bit), did not hang after installing Lightning Calendar Tabs. But reported against Linux Distro Fedora.
Doug, this sounds like a problem caused by the Fedora Distro version of Thunderbird, which is not maintained by Thunderbird.
If you download and install the original from thunderbird.net, you should not experience this problem.
Updated•4 years ago
|
Reporter | ||
Comment 2•4 years ago
|
||
Thanks, but did not fix the problem.
I did a dnf remove thunderbird.
Then download from the thunderbird.net page (https://download.mozilla.org/?product=thunderbird-78.11.0-SSL&os=linux64&lang=en-US)
and ran the un-tar'd thunderbird.
Same problem. No change.
Fedora 34
uname -a
Linux anddev 5.12.9-300.fc34.x86_64 #1 SMP Thu Jun 3 13:51:40 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Reporter | ||
Comment 3•4 years ago
|
||
Firefox 89.0 does the same thing.
Comment 4•4 years ago
|
||
Must be something special on your system.
Did you try in a fresh profile (start with -p)
Comment 5•4 years ago
|
||
This might be related to added support for enterprise policies. IIRC we added missing policies regarding add-ons very late in TB78. Maybe you had experimented with add-on policies like:
https://github.com/thundernest/policy-templates#extensionsettings
Since they did not work in early TB78, you may have not removed them. After support was added in late TB78, they are now preventing add-on installs. Could that be it? Policies apply to all profiles, so even starting with a fresh profile does not resolve the issue. The policies have to be removed.
Updated•4 years ago
|
Updated•3 years ago
|
Description
•