Installing NodeJS = What is this about?
"One last step"
"For the extension to execute external commands" . . . . .
Web page; moz-extension://fcbd72b9-e5f2-4c73-8896-40b17e19202c
Chosen solution
It has been 3 months, and the problem came back. Even disabling FDM did not stop it, so I did more digging.
I finally discovered the problem was caused by this file; C:\Users\===user===\AppData\Roaming\Mozilla\Firefox\ Profiles\===profile===\extensions\ {93d91d5e-1272-42e3-8323-a830fe339ac5}.xpi
Removing this solved the problem. I did a web search using many engines, but could not find any information on this file.
Thanks again to everyone that tried to help.
Read this answer in context 👍 0All Replies (4)
manifest.json
{
"name": "Download with FDM (Free Download Manager)", "description": "Help you interrupts the built-in download manager to direct links to FDM", "version": "1.1.0", "manifest_version": 2, "permissions": [ "storage", "tabs", "nativeMessaging", "notifications", "downloads", "contextMenus", "https://api.github.com/repos/belaviyo/native-client/releases/latest" ], "background": { "persistent": false, "scripts": [ "config.js", "termlib_parser.js", "common.js" ] }, "browser_action": { "default_icon": { "16": "data/icons/disabled/16.png", "32": "data/icons/disabled/32.png", "64": "data/icons/disabled/64.png" } }, "icons": { "16": "data/icons/16.png", "32": "data/icons/32.png", "64": "data/icons/64.png", "128": "data/icons/128.png", "256": "data/icons/256.png" }, "options_ui": { "page": "data/options/index.html", "chrome_style": true }
}
What I don't like is getting that 'install' instruction that does not seem to work. I sent a message to FDM support but they never answered.
Hi FredMcD, the "nativeMessaging" permission is what allows the extension to interact with another program on your system. I don't know what additional functionality that would add to the extension, but if the nagging becomes too intrusive, hopefully they will provide a way to disable it.
After I removed that file, the problem has not returned. Hopefully, it will stay gone.
I wonder if it has something to do with my using FF v54 ? I will not update because I refuse to do without my add-ons.