OS X Address book permission causes Thunderbird 115 to freeze on Mojave
Categories
(Thunderbird :: Address Book, defect)
Tracking
(Not tracked)
People
(Reporter: mozilla-sp, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:109.0) Gecko/20100101 Firefox/115.0
Steps to reproduce:
Open Thunderbird.
Actual results:
-
It opens to a white window and freezes with the "beach ball" wait cursor.
-
After several hours of waiting to be able to use my email, force quit Thunderbird. And try again.
-
Repeat steps 1 & 2 over and over again for two days.
-
Go into Terminal and launch Thunderbird from the command line to see any messages.
-
Notice that the last message is about Contacts.
-
Go into System Prefences and remove Thunderbird's "Contacts" permissions.
-
Open Thunderbird
-
Thunderbird opens as normal.
Expected results:
Thunderbird should have opened as normal without several hours troubleshooting.
Note: I do recall a few weeks ago wanting to integrate TB with my OS X address book, as this would be very convenient, although now that it is working again, I can't find how I did this, there doesn't appear to be an option for it. (However, TB has been working for many weeks since I last even thought about this, I haven't changed anything about my TB settings in at least a month and it just started freezing on open yesterday.)
EDIT: I believe I am on TB 115, the latest main version; I am not sure because as of this moment, while I have been typing this, it locked up again.
|
||
Updated•11 months ago
|
|
||
Comment 1•11 months ago
|
||
Sounds like a duplicate of bug 1831673
|
Reporter | |
Comment 2•11 months ago
|
||
(In reply to Wayne Mery (:wsmwk) from comment #1)
Sounds like a duplicate of bug 1831673
*** This bug has been marked as a duplicate of bug 1831673 ***
I'll trust your judgment but it doesn't sound like a duplicate to me. That bug sounds like it's talking about taking 2-3 minutes to start up. This bug is immediate startup to a blank white window, and then a permanent freeze, not just 2-3 minutes. I've let it sit up to an hour and nothing happens until I force-quit.
|
|
||
Comment 3•11 months ago
|
||
UIUI the amount of delay can vary, but you've basically done the workaround test at bug 1662759 comment 28. Though it is possible there may be more than one problem.
Description
•