xiaoxiaoflood / firefox-scripts

userChromeJS / autoconfig.js and extensions
Mozilla Public License 2.0
1.06k stars 88 forks source link

bootloading of unsigned addons not working now in Firefox v115.00. #264

Open MelchiorGaspar opened 1 year ago

MelchiorGaspar commented 1 year ago

https://github.com/onemen/TabMixPlus/issues/233 here is the issue on Onemen's TabedMixPlus page.. ever since I just updated Firefox to v115.0.0 today.. it will not load that addon now...

please fix asap. ty.

edit: on Windows 11 Pro (v22H2)(build 22621.1928)

TheGrave commented 1 year ago

Affects me too. Ubuntu 20.04, FF installed from official repos.

nollinvoyd commented 1 year ago

Download Manager (S3), Norwell History Tools as well

legscy

MelchiorGaspar commented 1 year ago

I get TRUE as the reply from the dev/browser console for: ChromeUtils.import('resource://gre/modules/addons/AddonSettings.jsm').AddonSettings.REQUIRE_SIGNING so the scripts are no longer working right.. lol

MelchiorGaspar commented 1 year ago

using https://github.com/xiaoxiaoflood/firefox-scripts/blob/66e896ec1514499557b64ce205104b04cdb8444a/installation-folder/config.js

seems to have fixed the issue for now..

dv8472 commented 1 year ago

Same problem with TMP & FF 115. Running Arch Linux. firefox-scripts - latest available.

using https://github.com/xiaoxiaoflood/firefox-scripts/blob/66e896ec1514499557b64ce205104b04cdb8444a/installation-folder/config.js

seems to have fixed the issue for now..

This doesn't work to me, ends up with empty FF, which is barely usable.

TheGrave commented 1 year ago

Same problem with TMP & FF 115. Running Arch Linux. firefox-scripts - latest available.

using https://github.com/xiaoxiaoflood/firefox-scripts/blob/66e896ec1514499557b64ce205104b04cdb8444a/installation-folder/config.js seems to have fixed the issue for now..

This doesn't work to me, ends up with empty FF, which is barely usable.

Same here, Ubuntu 20.04

puttesnutte commented 1 year ago

Same problem. Windows 10 Pro 22H2 19045.3155 64-bit FF 115

I get TRUE from running : ChromeUtils.import('resource://gre/modules/addons/AddonSettings.jsm').AddonSettings.REQUIRE_SIGNING in the browser console.

Using https://github.com/xiaoxiaoflood/firefox-scripts/blob/66e896ec1514499557b64ce205104b04cdb8444a/installation-folder/config.js doesn't help. It just says the xpi file is broken when trying to reinstall TMP.

blockberd commented 1 year ago

using https://github.com/xiaoxiaoflood/firefox-scripts/blob/66e896ec1514499557b64ce205104b04cdb8444a/installation-folder/config.js

seems to have fixed the issue for now..

works fine for me on Windows 10 22H2.

AuRiMaS666 commented 1 year ago

using https://github.com/xiaoxiaoflood/firefox-scripts/blob/66e896ec1514499557b64ce205104b04cdb8444a/installation-folder/config.js

seems to have fixed the issue for now..

Works for me as well on Win11 Pro 22H2. Just reinstalled the latest build of TMP and everything seems to be running as if nothing happened.

nollinvoyd commented 1 year ago

Thanks, that did it.

EDIT: I think I spoke too soon. I have it installed

s3x

And the status bar is displayed

s3

But there is no toolbar button. Only this puzzle piece context menu addition, that itself has no context menu, and has no function. Does not respond to the mouse

s3xyz

Choosing it's options, from about:addons, or from the status bar

s3xyzz

only brings this up. Again, whatever it's supposed to be, the only function there is that it can be closed.

s3xy

It does not appear in the overflow menu or the puzzle piece menu.

If the status bar is closed, it cannot be reopened. Reboot necessary.

dxzy commented 1 year ago

edit Program Files\Mozilla Firefox\config.js FF115

nollinvoyd commented 1 year ago

Sorry, my previous post I inserted the wrong image. I had intending it to be for DownloadManagerS3.

Can anyone tell me if DownloadManagerS3 id working normally?

puttesnutte commented 1 year ago

Using https://github.com/xiaoxiaoflood/firefox-scripts/blob/66e896ec1514499557b64ce205104b04cdb8444a/installation-folder/config.js DID help after all. I seem to have made some error when downloading the file the first time, and got a html-file instead. 😳

nollinvoyd commented 1 year ago

Using 66e896e/installation-folder/config.js DID help after all. I seem to have made some error when downloading the file the first time, and got a html-file instead. 😳

When I downloaded that file, and tried to open it to see what was in there, I got this, and there was no way to get inside that file. I had to "copy the raw data and create the file. Is that what you did?

config

MelchiorGaspar commented 1 year ago

@nollinvoyd
What version of Windows are you running currently where you are having this issue? you need to install a text editor like Notepad 3 or Notepad++ and associate the file type .js java-script with it Notepad++ is the easiest to install and it sets up with a open any type with NP++ then you can read the contents of the config.js as it can be run with Windows... which you don't usually want to do. in this case.

MelchiorGaspar commented 1 year ago

I just pressed the raw button and downloaded it as is

puttesnutte commented 1 year ago

I forgot how I did it the first time. The second time I just copied all of the text into an empty text file and saved that as "config.js". I use the text editor UltraEdit.

klcb2010 commented 1 year ago

using https://github.com/xiaoxiaoflood/firefox-scripts/blob/66e896ec1514499557b64ce205104b04cdb8444a/installation-folder/config.js seems to have fixed the issue for now..

works fine for me on Windows 10 22H2.

SO do i ,when i reinstall TMP(seems that must reinstall) ,it work

nollinvoyd commented 1 year ago

@nollinvoyd What version of Windows are you running currently where you are having this issue? you need to install a text editor like Notepad 3 or Notepad++ and associate the file type .js java-script with it Notepad++ is the easiest to install and it sets up with a open any type with NP++ then you can read the contents of the config.js as it can be run with Windows... which you don't usually want to do. in this case.

I have Notepad++, NoteTab Light, and EditPad. File association is not an issue here. When I copied the contents of config.js from https://github.com/xiaoxiaoflood/firefox-scripts/blob/66e896ec1514499557b64ce205104b04cdb8444a/installation-folder/config.js and manually created the config.js,, instead of downloading the file itself (which I attempted several times), it worked normally, evidenced by the fact that I also use Norwell History Tools from that collection with no problems that I can see since the updated config.js was released. Not to mention I subsequently had no difficulty opening/editing config.js.

The only reason I mentioned this was to let people know it was a corrupted file, in case they also had any such problems.

In my case, I'm the only user reporting issues with Download Manager (S3). My only conclusion is that the current s3download.xpi requires updating.

If someone out there could kindly test my theory by installing Download Manager (S3) and letting me know if their outcome was similar to mine, it would be appreciated.

MelchiorGaspar commented 1 year ago

I like NP++ too, but I have not heard of those other two.

nollinvoyd commented 1 year ago

I like NP++ too, but I have not heard of those other two.

So could you test Download Manager (S3) for me?

MelchiorGaspar commented 1 year ago

[Download Manager (S3)] has not been updated since... --> Last updated, 4 years ago (Jul 4, 2019)

best not to use it.. I tried it and didn't like it years ago..

My favorite download manager Firefox addon is [ Download Manager Tweak ] it works for Waterfox classic, a fork of the older version of Firefox before the XUL extension system was purged.. https://classic.waterfox.net/

I have created a webpage on my free Angelfire website to host that download manager addon,, https://www.angelfire.com/empire/kingdombaron/dmt.html it needs to be updated to work with xiaoxiaoflood's firefox-scripts

nollinvoyd commented 1 year ago

it needs to be updated to work with xiaoxiaoflood's firefox-scripts

How?

MelchiorGaspar commented 1 year ago

it needs to be updated to work with xiaoxiaoflood's firefox-scripts

How?

idk, I am not a Firefox addon developer. lol.

the same way the addon Tab Mix Plus was updated I guess.. I sent a copy of the addon to Onemen the dev of Tab Mix Plus.. and a donation. :D

nollinvoyd commented 1 year ago

I use the stable version of Firefox, so I guess I'll have to wait and see if it gets updated here, and it will work for me Thanks :)

MelchiorGaspar commented 1 year ago

I have both the stable version of Firefox v115.0.1 and Waterfox classic installed. I don't know how to tweak the addon so yeah.. :( most websites work in Waterfox classic except for GitHub it doesn't fully work in classic.

Lalarian commented 1 year ago

For me the config.sys makes the browser unresponsive (115 on Arch Linux). There's just the clear (tock) Ui with no possibility to enter or click anything.

117649 commented 1 year ago

For me the config.sys makes the browser unresponsive (115 on Arch Linux). There's just the clear (tock) Ui with no possibility to enter or click anything.

https://github.com/onemen/TabMixPlus/issues/233#issuecomment-1624025716

Lalarian commented 1 year ago

Thank you! It's working using this config.js! If only the didn't work at making Firefox worse all the time :( Guess I'll just never update it agan.. Security isn't worth anything if the software becomes unuseable at he same time.

megamorphg commented 1 year ago

I'm getting the "could not be verified for use in Firefox and has been disabled" for all my add-ons after updating to 115... really miss Fast Tab Switcher. Any step-by-step suggestions on making this work from the latest scripts? Like, what modifications do we have to do?

purple512 commented 1 year ago

Any step-by-step suggestions on making this work from the latest scripts?

It's all covered in this thread.

  1. Right click this link, save as config.js somewhere temporary.
  2. Close Firefox. Replace C:\Program Files\Mozilla Firefox\config.js with the one you downloaded. This file is protected by UAC on a normal install so you'll need to be admin. If you copy/paste the file in Windows Explorer it should prompt you to for admin and work successfully. You can use a text editor but you'd have to launch the text editor as admin to be able to save the file.
  3. Restart Firefox. Should work. If it doesn't, invalidate the startup cache.
megamorphg commented 1 year ago

@purple512 I tried your exact steps including #3 (deleting profile's startupCache folder) and still the addons have the same message.

purple512 commented 1 year ago

@purple512 I tried your exact steps including #3 (deleting profile's startupCache folder) and still the addons have the same message.

What operating system? What Firefox version (nightly/release/etc)? The config.js linked above has been working fine for me on Windows w/Firefox 115 without issue. If you're using nightly there's a separate issue for extension signing on 117.

megamorphg commented 1 year ago

@purple512 Windows 10 + FF Release 115.0.2 (64-bit)

purple512 commented 1 year ago

@purple512 Windows 10 + FF Release 115.0.2 (64-bit)

I have no idea why it's not working for you then. Only thing I can think of is verify the contents of config.js is correct and not a browser HTML error page or some other kind of issue like that. (Someone up-thread mentioned an issue along those lines.)

megamorphg commented 1 year ago

@purple512 it's working now! I had disabled auto-update of add-ons and it seems on the next update, it updated the add-ons back to enabled. So that is a last step:

  1. Update config.js from here
  2. Delete startupCache
  3. Start FF and run check all add-ons for updates
117649 commented 1 year ago

@purple512 it's working now! I had disabled auto-update of add-ons and it seems on the next update, it updated the add-ons back to enabled. So that is a last step:

1. Update config.js from here

2. Delete startupCache

3. Start FF and run check all add-ons for updates

You can force activate the installed addons by run this in browser console or console of 'about:addons':

var ad = (await AddonManager.getAddonByID(/* string of the addon id. You can get these on 'about:addons' with devtool */));
ad.__AddonInternal__.signedState = AddonManager.SIGNEDSTATE_NOT_REQUIRED;
ad.__AddonInternal__.appDisabled = false;
ad.disable();
ad.enable();
nollinvoyd commented 1 year ago

@117649

You can force activate the installed addons by run this in browser console or console of 'about:addons':

var ad = (await AddonManager.getAddonByID(/* string of the addon id. You can get these on 'about:addons' with devtool */));
ad.__AddonInternal__.signedState = AddonManager.SIGNEDSTATE_NOT_REQUIRED;
ad.__AddonInternal__.appDisabled = false;
ad.disable();
ad.enable();

I'm nor clear on what you mean by running it in "this in browser console or console of 'about:addons':"

For instance, what do I do after I open the Browser console?

TheGrave commented 1 year ago

So 2 months since reporting this bug and firefox-scripts still not updated for Linux users? I feel offended, we are not second-hand people :D

117649 commented 1 year ago

So 2 months since reporting this bug and firefox-scripts still not updated for Linux users? I feel offended, we are not second-hand people :D

According to record it already been left unmaintained for way much longer. And after this config.js came out no other linux user report their problem is not fixable.

// skip 1st line
lockPref('xpinstall.signatures.required', false);
lockPref('extensions.install_origins.enabled', false);
lockPref("extensions.experiments.enabled", true);

try {
  const cmanifest = Cc['@mozilla.org/file/directory_service;1'].getService(Ci.nsIProperties).get('UChrm', Ci.nsIFile);
  cmanifest.append('utils');
  cmanifest.append('chrome.manifest');
  Components.manager.QueryInterface(Ci.nsIComponentRegistrar).autoRegister(cmanifest);

  const objRef = ChromeUtils.import('resource://gre/modules/addons/XPIDatabase.jsm');
  objRef.XPIDatabase.SIGNED_TYPES.delete("extension");

  Cu.import('chrome://userchromejs/content/BootstrapLoader.jsm');
} catch (ex) {};

try {
  Cu.import('chrome://userchromejs/content/userChrome.jsm');
} catch (ex) {};