Comments (6)
4ch1m
commented on June 15, 2024
Can't reproduce.
Works for me.
Which OS (version)?
Which add-on version?
Which other add-ons are active?
What does the console log look like?
from mozext.
spalinger
commented on June 15, 2024
91.0.3 64-Bit
Windows 10 Pro 21H1
Add-ons: Minimize on Close, Monterail Dark, Provider for CalDAV & CardDAV, Signature Switch (2.8.0), TbSync, LookOut
Clicking "Write" for a new email
ExtensionError: No such native application signatureswitch 7 ExtensionUtils.jsm:58:5
ExtensionError resource://gre/modules/ExtensionUtils.jsm:58
startupPromise resource://gre/modules/NativeMessaging.jsm:83
Clicking "Send"
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIEditor.getInlineSpellChecker] MsgComposeCommands.js:401
shortly after (not reoccurring after clicking Send again)
Prompter: internal dialogs not available in this context. Falling back to window prompt. Prompter.jsm:1084
set modalType resource://gre/modules/Prompter.jsm:1084
ModalPrompter resource://gre/modules/Prompter.jsm:1040
getPrompt resource://gre/modules/Prompter.jsm:65
CompleteGenericSendMessage chrome://messenger/content/messengercompose/MsgComposeCommands.js:4874
GenericSendMessage chrome://messenger/content/messengercompose/MsgComposeCommands.js:4810
AutoSave chrome://messenger/content/messengercompose/MsgComposeCommands.js:8942
Uncaught
Exception { name: "NS_ERROR_FAILURE", message: "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIEditor.getInlineSpellChecker]", result: 2147500037, filename: "chrome://messenger/content/messengercompose/MsgComposeCommands.js", lineNumber: 401, columnNumber: 0, data: null, stack: "updateEditableFields@chrome://messenger/content/messengercompose/MsgComposeCommands.js:401:38\nToggleWindowLock@chrome://messenger/content/messengercompose/MsgComposeCommands.js:2654:23\nComposeProcessDone@chrome://messenger/content/messengercompose/MsgComposeCommands.js:680:21\n_doFcc2/<@resource:///modules/MessageSend.jsm:962:12\nnotify@resource://gre/modules/Timer.jsm:62:17\n", location: XPCWrappedNative_NoHelper }
MsgComposeCommands.js:401
updateEditableFields chrome://messenger/content/messengercompose/MsgComposeCommands.js:401
ToggleWindowLock chrome://messenger/content/messengercompose/MsgComposeCommands.js:2654
ComposeProcessDone chrome://messenger/content/messengercompose/MsgComposeCommands.js:680
_doFcc2 resource:///modules/MessageSend.jsm:962
notify resource://gre/modules/Timer.jsm:62
<Provider> does not support changing `store` on the fly. It is most likely that you see this error because you updated to Redux 2.x and React Redux 2.x which no longer hot reload reducers automatically. See https://github.com/reactjs/react-redux/releases/tag/v2.0.0 for the migration instructions. react-redux.js:881:13
Redux 3
React 38
renderApp resource://devtools/client/webconsole/webconsole-wrapper.js:41
init resource://devtools/client/webconsole/webconsole-wrapper.js:121
init resource://devtools/client/webconsole/webconsole-wrapper.js:85
_initializer resource://devtools/client/webconsole/webconsole-ui.js:162
Disabling just Signature Switch and after clicking on Write (sometimes too while Signature Switch is enabled):
Uncaught
Exception { name: "NS_ERROR_FAILURE", message: "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIEditor.getInlineSpellChecker]", result: 2147500037, filename: "chrome://messenger/content/messengercompose/MsgComposeCommands.js", lineNumber: 401, columnNumber: 0, data: null, stack: "updateEditableFields@chrome://messenger/content/messengercompose/MsgComposeCommands.js:401:38\nComposeFieldsReady@chrome://messenger/content/messengercompose/MsgComposeCommands.js:2739:23\nNotifyComposeFieldsReady@chrome://messenger/content/messengercompose/MsgComposeCommands.js:461:5\nInitEditor@chrome://messenger/content/messengercompose/MsgComposeCommands.js:9242:15\nobserve@chrome://messenger/content/messengercompose/MsgComposeCommands.js:3803:9\n", location: XPCWrappedNative_NoHelper }
MsgComposeCommands.js:401
updateEditableFields chrome://messenger/content/messengercompose/MsgComposeCommands.js:401
ComposeFieldsReady chrome://messenger/content/messengercompose/MsgComposeCommands.js:2739
NotifyComposeFieldsReady chrome://messenger/content/messengercompose/MsgComposeCommands.js:461
InitEditor chrome://messenger/content/messengercompose/MsgComposeCommands.js:9242
observe chrome://messenger/content/messengercompose/MsgComposeCommands.js:3803
from mozext.
spalinger
commented on June 15, 2024
I did not uninstall Thunderbird 78 before installing Thunderbird 91.
from mozext.
AurelioSilver
commented on June 15, 2024
Similar issue. Updated from 78 to 91.0.3. Sending mails does not work. You click on send and nothing happens.
One note: I think it worked after the initial installation, but stopped after Signature Switch asked for extended permissions. After I granted these, the issue occurred. Only disabling this add-on in the Add-on dialog of TB, fixes this issue.
Windows 10 Pro (19043), 64bit
Thunderbird: 91.0.3 64-Bit
TbSync (also tried to disable this)
Provider für Exchange ActiveSync (also tried to disable this)
Console output: Last line is, when you press send.
Exception { name: "NS_ERROR_FAILURE", message: "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIEditor.getInlineSpellChecker]", result: 2147500037, filename: "chrome://messenger/content/messengercompose/MsgComposeCommands.js", lineNumber: 401, columnNumber: 0, data: null, stack: "updateEditableFields@chrome://messenger/content/messengercompose/MsgComposeCommands.js:401:38\nComposeFieldsReady@chrome://messenger/content/messengercompose/MsgComposeCommands.js:2739:23\nNotifyComposeFieldsReady@chrome://messenger/content/messengercompose/MsgComposeCommands.js:461:5\nInitEditor@chrome://messenger/content/messengercompose/MsgComposeCommands.js:9242:15\nobserve@chrome://messenger/content/messengercompose/MsgComposeCommands.js:3803:9\n", location: XPCWrappedNative_NoHelper }
MsgComposeCommands.js:401
updateEditableFields chrome://messenger/content/messengercompose/MsgComposeCommands.js:401
ComposeFieldsReady chrome://messenger/content/messengercompose/MsgComposeCommands.js:2739
NotifyComposeFieldsReady chrome://messenger/content/messengercompose/MsgComposeCommands.js:461
InitEditor chrome://messenger/content/messengercompose/MsgComposeCommands.js:9242
observe chrome://messenger/content/messengercompose/MsgComposeCommands.js:3803
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIAutoCompleteInput.popup] LoginManagerChild.jsm:194
observe resource://gre/modules/LoginManagerChild.jsm:194
addressInputOnBlur chrome://messenger/content/messengercompose/addressingWidgetOverlay.js:1030
onblur chrome://messenger/content/messengercompose/messengercompose.xhtml:1
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIEditor.getInlineSpellChecker]
Console output, when Addon is disabled. Sending works.
Uncaught
Exception { name: "NS_ERROR_FAILURE", message: "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIEditor.getInlineSpellChecker]", result: 2147500037, filename: "chrome://messenger/content/messengercompose/MsgComposeCommands.js", lineNumber: 401, columnNumber: 0, data: null, stack: "updateEditableFields@chrome://messenger/content/messengercompose/MsgComposeCommands.js:401:38\nComposeFieldsReady@chrome://messenger/content/messengercompose/MsgComposeCommands.js:2739:23\nNotifyComposeFieldsReady@chrome://messenger/content/messengercompose/MsgComposeCommands.js:461:5\nInitEditor@chrome://messenger/content/messengercompose/MsgComposeCommands.js:9242:15\nobserve@chrome://messenger/content/messengercompose/MsgComposeCommands.js:3803:9\n", location: XPCWrappedNative_NoHelper }
MsgComposeCommands.js:401
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIAutoCompleteInput.popup] LoginManagerChild.jsm:194
observe resource://gre/modules/LoginManagerChild.jsm:194
onPopupClick chrome://global/content/elements/autocomplete-popup.js:236
handleEvent chrome://global/content/elements/autocomplete-popup.js:85
Prompter: internal dialogs not available in this context. Falling back to window prompt. Prompter.jsm:1084
set modalType resource://gre/modules/Prompter.jsm:1084
ModalPrompter resource://gre/modules/Prompter.jsm:1040
getPrompt resource://gre/modules/Prompter.jsm:65
CompleteGenericSendMessage chrome://messenger/content/messengercompose/MsgComposeCommands.js:4874
GenericSendMessage chrome://messenger/content/messengercompose/MsgComposeCommands.js:4810
SendMessage chrome://messenger/content/messengercompose/MsgComposeCommands.js:5329
doCommand chrome://messenger/content/messengercompose/MsgComposeCommands.js:948
doCommand chrome://messenger/content/messengercompose/MsgComposeCommands.js:1126
goDoCommand chrome://global/content/globalOverlay.js:123
oncommand chrome://messenger/content/messengercompose/messengercompose.xhtml:1
Uncaught
Exception { name: "NS_ERROR_FAILURE", message: "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIEditor.getInlineSpellChecker]", result: 2147500037, filename: "chrome://messenger/content/messengercompose/MsgComposeCommands.js", lineNumber: 401, columnNumber: 0, data: null, stack: "updateEditableFields@chrome://messenger/content/messengercompose/MsgComposeCommands.js:401:38\nToggleWindowLock@chrome://messenger/content/messengercompose/MsgComposeCommands.js:2654:23\nComposeProcessDone@chrome://messenger/content/messengercompose/MsgComposeCommands.js:680:21\n_doFcc2/<@resource:///modules/MessageSend.jsm:962:12\nnotify@resource://gre/modules/Timer.jsm:62:17\n", location: XPCWrappedNative_NoHelper }
MsgComposeCommands.js:401
updateEditableFields chrome://messenger/content/messengercompose/MsgComposeCommands.js:401
ToggleWindowLock chrome://messenger/content/messengercompose/MsgComposeCommands.js:2654
ComposeProcessDone chrome://messenger/content/messengercompose/MsgComposeCommands.js:680
_doFcc2 resource:///modules/MessageSend.jsm:962
notify resource://gre/modules/Timer.jsm:62
from mozext.
AurelioSilver
commented on June 15, 2024
Seems Thunderbird version 91.1.0 fixed that... anybody else can confirm?
from mozext.
spalinger
commented on June 15, 2024
I can confirm, sending is possible again.
Clicking write still gives me the same errors as written above, but no functionality loss is apparent.
from mozext.
Related Issues (20)
- Feature request: Auto switch only when all recepients match with a domain HOT 2
- Switching a signature deletes all existing text HOT 3
- Signature Switch ate my mail HOT 1
- Visual separator added by default HOT 1
- Editor for plaintext signature uses proportional font HOT 4
- White/blank menu from the second invocation of Signature Switch in a composer window HOT 3
- Support removing signatures when switching to identities without a signature assigned
- Signature Switch's Fortune Cookie text file import munges accented characters in ANSI-Encoded text files. HOT 1
- Native messaging from URL HOT 4
- Signature Switch: remove the -- seperator and newline for plain text emails HOT 5
- Default signature is not applied (regexps in application rules could help) HOT 2
- Signature Switch (ME): Doesn't work in TB 102 beta, the future TB 102 ESR HOT 1
- Automatic signature switching for replies stopped working. HOT 1
- Reading recipient Field
- [New feature] List of allowed signatures per identity HOT 1
- Suggestion for cosmetic improvement HOT 3
- About dark theme (not an issue) HOT 7
- assign signature to identity
- Auto switch only when all recepients match with a domain not working
- Waiver of "--" HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from mozext.