search

proginosko / LeechBlockNG

LeechBlock NG (Next Generation) for Firefox is a simple productivity tool designed to block those time-wasting sites that can suck the life out of your working day. All you need to do is specify which sites to block and when to block them.
https://www.proginosko.com/leechblock/
Mozilla Public License 2.0
723 stars 66 forks source link

nothing is blocked anymore #263

Closed tsuyoshi2 closed 1 year ago

tsuyoshi2 commented 2 years ago

I'm running Debian. I have tried to use all versions of firefox and firefox-esr currently available in the Debian repositories (stable and unstable) with no luck. Cleared all data, purged Firefox and reinstalled (which necessarily required reinstalling Leechblock), removed ~/.mozilla - none of which worked.

To simplify things, I have reduced my block list to the single line:

*twitter.com

262 looks pretty similar, although I have not tried to export my options at all. Anyway, I tried to do the same things to figure out the problem.

When I try the diagnostics page, I get:

====== Block Set 1 BLOCK: https://twitter.com

When I enable diagnostic mode and then open the browser console, I get:

Content Security Policy: Ignoring “'unsafe-inline'” within script-src or style-src: nonce-source or hash-source specified 3 Content Security Policy: Ignoring “'unsafe-inline'” within script-src or style-src: nonce-source or hash-source specified 11 Content Security Policy: Ignoring “'unsafe-inline'” within script-src or style-src: nonce-source or hash-source specified 2 Content Security Policy: Ignoring “'unsafe-inline'” within script-src or style-src: nonce-source or hash-source specified

But that appears to be the same thing I get with or without Leechblock.

I'm willing to try anything... but I guess in the meantime I will be going back to the /etc/hosts method of blocking things.

proginosko commented 2 years ago

Can you export your options to a file and email it to me (leechblockng@proginosko.com)?

tsuyoshi2 commented 2 years ago

OK, I have sent the options.

In the meantime I have noticed that I have another computer where Leechblock is still working. It is running an older version of Firefox (103.0). I tried copying the .deb from that computer to this one where it doesn't work and downgrading. The downgrade went through without a hitch (I am using the old version to write this comment), but still, Leechblock isn't blocking. Honestly, I don't understand how this is even possible... looking at the dependencies, it's mostly the usual GTK libraries. I checked and both are running the same version of Leechblock (1.5.1).

proginosko commented 1 year ago

Resolved.