-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"this.view.dbView is null" with TorBirdy #19
Comments
I could reproduce the following: I could not reproduce any change if extended logging is on or off. I have now created another beta version, can you please try this one if you see the "this.view.dbView is null" error again? |
Using 0.9.9.3 beta 1 (not 2), with TorBirdy installed, and no folder selected, I am (and was) unable to reproduce the "this.view.dbView is null" error (the report quoted above refers to version 0.9.9.2). Do you want me to test beta 2 nevertheless? |
That's strange (like everything arround this bug)... |
Tested:
|
Thanks. Released via 0.9.9.3 (may take some time until it is reviewed and accepted by Mozilla). |
I splitted this issue out of #18 from tomreyn:
If I then start TB again using my default locale (i.e. without the LANG=C), AutoArchive Reloaded again shows up as "null" on the extension list. However, it now shows with a properly localized description text, and I can access its (properly localized) preferences menu as well.
Trying to do an auto-archiving run results in this message written to error log, though:
12.9.2016, 21:58:42 - AutoarchiveReloaded - ERROR: TypeError: this.view.dbView is null; Source: 'chrome://messenger/content/folderDisplay.js'; Line: 1449; code: (new TypeError("this.view.dbView is null", "chrome://messenger/content/folderDisplay.js", 1449)); stack: FolderDisplayWidget_hintAboutToDeleteMessages@chrome://messenger/content/folderDisplay.js:1449:5 FolderDisplayWidget_hintMassMoveStarting@chrome://messenger/content/folderDisplay.js:1465:5 BatchMessageMover.prototype.archiveMessages@chrome://messenger/content/mailWindowOverlay.js:1628:5 AutoarchiveReloadedOverlay.SearchListener.prototype.archiveMessages@chrome://autoarchivereloaded/content/overlay.js:304:9 AutoarchiveReloadedOverlay.SearchListener.prototype.onSearchDone@chrome://autoarchivereloaded/content/overlay.js:386:18
Update: On a repeat run (with the extensions' own logging to file enabled), auto-archiving actually works.
The text was updated successfully, but these errors were encountered: