Closed
Bug 1114626
Opened 10 years ago
Closed 3 years ago
After upgrade to 31, main panel is blank, only see chrome: Error "Unable to to add site to file:// URI whitelist: imap://<email server>:14". Cause: (capability.policy.localfilelinks.sites pref)
Categories
(Thunderbird :: Mail Window Front End, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: amartin, Unassigned)
Details
(Keywords: regression)
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/38.0.2125.111 Safari/537.36 Steps to reproduce: Users were using Thunderbird 24; it auto-updated to Thunderbird 31.3.0 Actual results: After the upgrade, existing user profile is completely inaccessible inside of Thunderbird (it is completely blank); The email, address book, message filters, and calendar sections are all blank/empty. Moving the old profile and creating a new one and re-adding all account information manually appears to work for a period of time, but after a few restarts of Thunderbird it is empty again. Many users have reproduced this same problem upgrading from 24 -> 31.3.0. As a result, all have been forced to downgrade back to 24 for the time being. Expected results: The profile should have been visible and usable after the update.
Comment 1•10 years ago
|
||
(In reply to Andrew Martin from comment #0) > Many users have reproduced this same problem upgrading from 24 -> 31.3.0. Any links to these reports?
Comment 2•10 years ago
|
||
Anything in the error console? They don't happen to use thunderbird in Japanese locale on mac?
Keywords: regression
Reporter | ||
Comment 3•10 years ago
|
||
These users are on Windows 7 and using en-US. I believe we've found the problem - message in the error console: Unable to to add site to file:// URI whitelist: imap://<email server>:143 Corresponding line in prefs.js: user_pref("capability.policy.localfilelinks.sites", "imap://<email server>:143"); Shutting down Thunderbird, deleting this line from user.js and prefs.js, and then restarting Thunderbird appears to restore the profile
Updated•10 years ago
|
Summary: Upgrade to 31 Profile Inaccessible → Upgrade to 31 Profile show blank: Unable to to add site to file:// URI whitelist: imap://<email server>:143 (capability.policy.localfilelinks.sites pref)
Updated•10 years ago
|
Severity: normal → major
Comment 4•9 years ago
|
||
check out this list http://mzl.la/1HVqCa6
Summary: Upgrade to 31 Profile show blank: Unable to to add site to file:// URI whitelist: imap://<email server>:143 (capability.policy.localfilelinks.sites pref) → Upgrade to 31 Profile show blank content, only see chrome: Error "Unable to to add site to file:// URI whitelist: imap://<email server>:14". Cause: (capability.policy.localfilelinks.sites pref)
Comment 5•8 years ago
|
||
(In reply to Andrew Martin from comment #3) > These users are on Windows 7 and using en-US. I believe we've found the > problem - message in the error console: > Unable to to add site to file:// URI whitelist: imap://<email server>:143 > > Corresponding line in prefs.js: > user_pref("capability.policy.localfilelinks.sites", "imap://<email > server>:143"); > > Shutting down Thunderbird, deleting this line from user.js and prefs.js, and > then restarting Thunderbird appears to restore the profile ... > check out this list http://mzl.la/1HVqCa6 magnus, what do you think?
Component: Untriaged → Mail Window Front End
Flags: needinfo?(mkmelin+mozilla)
OS: Linux → Windows 7
Summary: Upgrade to 31 Profile show blank content, only see chrome: Error "Unable to to add site to file:// URI whitelist: imap://<email server>:14". Cause: (capability.policy.localfilelinks.sites pref) → After upgrade to 31, main panel is blank, only see chrome: Error "Unable to to add site to file:// URI whitelist: imap://<email server>:14". Cause: (capability.policy.localfilelinks.sites pref)
Comment 7•7 years ago
|
||
(In reply to Magnus Melin from comment #6) > Might have been bug 995943. Magnus, you mean caused by? Andrew, do you still see this problem when using a current version?
Flags: needinfo?(amartin)
Comment 8•7 years ago
|
||
Not caused by, but shall we say, should be working after that.
Updated•5 years ago
|
Severity: major → normal
Updated•3 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Flags: needinfo?(amartin)
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•