Basilisk updated Topic is solved
Moderator: Basilisk-Dev
Basilisk updated
Basilisk has just been updated to 2017-12-28 which is an intermediate update i wanted to publish to get at least the Mozilla interference with the browser under control.
If you've previously tinkered with the blocklist settings etc. please revert preferences to their defaults.
Release notes: https://www.basilisk-browser.org/releasenotes.shtml
If you've previously tinkered with the blocklist settings etc. please revert preferences to their defaults.
Release notes: https://www.basilisk-browser.org/releasenotes.shtml
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
Re: Basilisk updated
unfortunately the patch let our "settings service" still making problems. There is something wrong with basilisk, as meanwhile I reactivated firefox 56 which has no blocklist settings at all.
Re: Basilisk updated
Did you reset all preferences to their defaults?
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
Re: Basilisk updated
If you're still having issues, try clearing the url from preference "services.settings.server". Disabling the extension blocklist altogether as recommended by some is not smart because it also has entries in there to prevent certain features on specific graphics drivers/hardware which are known to be problematic.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
Re: Basilisk updated
Just updated to the latest version, and I am still seeing the warnings appear for installed add-ons. I tried "refreshing" the profile, which if I'm not mistaken includes resetting all about:config preferences to their defaults. Also tried clearing the URL from services.settings.server as mentioned.
That being said, while the warnings are still appearing, the browser is no longer automatically disabling add-ons with the blocklist enabled, so that is an improvement. Thank you for the update!
That being said, while the warnings are still appearing, the browser is no longer automatically disabling add-ons with the blocklist enabled, so that is an improvement. Thank you for the update!
a.k.a. Ascrod
Linux Mint 19.3 Cinnamon (64-bit), Debian Bullseye (64-bit), Windows 7 (64-bit)
"As long as there is someone who will appreciate the work involved in the creation, the effort is time well spent." ~ Tetsuzou Kamadani, Cave Story
Linux Mint 19.3 Cinnamon (64-bit), Debian Bullseye (64-bit), Windows 7 (64-bit)
"As long as there is someone who will appreciate the work involved in the creation, the effort is time well spent." ~ Tetsuzou Kamadani, Cave Story
Re: Basilisk updated
Apparently, the warnings can be cleared by disabling and re-enabling the extensions affected.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
Re: Basilisk updated
some 6 hours ago I followed your advice and I did a reset to all the blocklist options and immediately after starting/restarting b I set extensions.blocklist.enabled to false. Since then no problems anymore. Thanks!
Anyhow I wonder that entering blocklist as search key in about:config of firefox56 results in a result set 0, null, zerso, njada. Apparently blocklist is a basilisk feature.
Anyhow I wonder that entering blocklist as search key in about:config of firefox56 results in a result set 0, null, zerso, njada. Apparently blocklist is a basilisk feature.
Last edited by dodona on 2017-12-29, 22:36, edited 1 time in total.
Re: Basilisk updated
Because following simple instructions is hard, apparently.New Tobin Paradigm wrote:Why did you disable the blocklist again...
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
Re: Basilisk updated
Moonchild wrote:
Apparently, the warnings can be cleared by disabling and re-enabling the extensions affected.
Neither of these worked for me. Anything else left to try?Moonchild wrote:
If you're still having issues, try clearing the url from preference "services.settings.server".
Last edited by ron_1 on 2017-12-30, 03:07, edited 3 times in total.
Re: Basilisk updated
My experience with Basilisk on Ubuntu, however, has been that that doesn't work.Moonchild wrote:Apparently, the warnings can be cleared by disabling and re-enabling the extensions affected.
In fact, I just tried it on the latest version. The warnings did not go away; or in some cases, they went away temporarily, but came back
In the case of Themes Menu, Add-ons Manager wouldn't let me enable; there was only a remove button.
I also want to report that on my default profile I had selected the option to "Check for updates, but let you choose whether to install them"; however Basilisk updated itself without any action on my part, so it seems that this setting doesn't quite work.
This was updating to v. 2017.12.28 from 2017.12.03 on Ubuntu 14.04.
Last edited by gracious1 on 2017-12-30, 03:43, edited 6 times in total.
20 July 1969 🌗 Apollo 11 🌓 "One small step for [a] man, one giant leap for mankind." 🚀
Re: Basilisk updated
My steps for the Extensions issues in Basilisk 2017.12.28 (64-bit) on Ubuntu 14.04
- In Terminal, enter
Code: Select all
basilisk -P --no-remote
- In Profile Manager, create new profile (and use it)
- Go to about:config and clear value of services.setting.server
- Install these add-ons from AMO or github, restarting when prompted:
- CookieKeeper
- Decentraleyes 1.3.8
- Extension Options Menu
- Privacy Badger
- Restart Manager
- QuickNote
- uBlock Origin 1.14.22
- Go to about:addons (Add-ons Manager) and observe:
- Now disable everything and observe:
- Now restart Basilisk; observe:Note the following:
- Decentraleyes & Extension Options Menu re-enabled themselves somehow and appear normal
- CookieKeeper remains disabled and has a warning
- Restart Manager & uBlock Origin re-enabled themselves somehow, and also show the warning
- QuickNote remains diabled; and its "Enable" button has disappeared, leaving only "Remove; and it has the warning.
- Go back to about:config and set extensions.blocklist.enabled to false
- Return to about:addons, and all the warning are gone, except for uBlock Origin thus:
- Now restart browser; Add-ons Manager unchanged from previous step.
- Now disable and re-enable uBlock Origin; no change.
- Now remove uBlock Origin and re-install from Github; no change.
20 July 1969 🌗 Apollo 11 🌓 "One small step for [a] man, one giant leap for mankind." 🚀
Re: Basilisk updated
gracious1,
"Check for updates, but let you choose whether to install them" works for me as expected on Linux Mint.
"Check for updates, but let you choose whether to install them" works for me as expected on Linux Mint.
Re: Basilisk updated
otherwise the mess starts again.New Tobin Paradigm wrote:Why did you disable the blocklist again...
Now we have a second signature problem too:
read more on the issuehttps://support.mozilla.org/en-US/kb/add-on-signing-in-firefox?as=u&utm_source=inproduct
Again I mention that none of the both problems happens running firefox56 with the same profile, extensions, ...
-
- Moon Magic practitioner
- Posts: 2986
- Joined: 2015-09-26, 04:51
- Location: U.S.
Re: Basilisk updated
dodona wrote:Now we have a second signature problem too...
For the second problem...
Since it's related to add-on signing, does it help if you flip the following setting in about:config to false?
Code: Select all
services.blocklist.signing.enforced
dodona wrote:Again I mention that none of the both problems happens running firefox56 with the same profile, extensions,...
1) Did you copy over your Firefox (or Pale Moon) profile to use in Basilisk?
2) What is your operating system?
If you are on Windows and did copy your profile from another browser, try using a fresh profile (from scratch) - it should get rid of the warnings.
Re: Basilisk updated
it isn't that simple. Setting ...signing.enforced has no effect. Gues it works only in fifefox nightly builds and so on.coffeebreak wrote:dodona wrote:Now we have a second signature problem too...
For the second problem...
Since it's related to add-on signing, does it help if you flip the following setting in about:config to false?Code: Select all
services.blocklist.signing.enforced
dodona wrote:Again I mention that none of the both problems happens running firefox56 with the same profile, extensions,...
Linux.coffeebreak wrote:dodona wrote: 2) What is your operating system?
If you are on Windows and did copy your profile from another browser, try using a fresh profile (from scratch) - it should get rid of the warnings.
Re: Basilisk updated
dodona wrote:it isn't that simple. Setting ...signing.enforced has no effect. Guess it works only in fifefox nightly builds and so on.coffeebreak wrote:dodona wrote:Now we have a second signature problem too...
For the second problem...
Since it's related to add-on signing, does it help if you flip the following setting in about:config to false?Code: Select all
services.blocklist.signing.enforced
coffeebreak wrote:Linux.dodona wrote: 2) What is your operating system?
Re: Basilisk updated
it isn't that simple. Setting ...signing.enforced has no effect. Guess it works only in fifefox nightly builds and so on.coffeebreak wrote:dodona wrote:Now we have a second signature problem too...
For the second problem...
Since it's related to add-on signing, does it help if you flip the following setting in about:config to false?Code: Select all
services.blocklist.signing.enforced
Linux.[coffeebreak wrote:dodona wrote: 2) What is your operating system?
Re: Basilisk updated
interesting observation.
Today from 8-18h (Central European Time), what is new years night in US, the whole blocklist.setting mess disappeared.
Then at ~ 19h a restart and immediately blocklist disabled all extensions.
It looks like a tcp communication to a blocklist service, which restarted the mess again, after it slept new years night.
BTW. conversion of web pages to the print mode don't work at all:
Failed to load article from page
Today from 8-18h (Central European Time), what is new years night in US, the whole blocklist.setting mess disappeared.
Then at ~ 19h a restart and immediately blocklist disabled all extensions.
It looks like a tcp communication to a blocklist service, which restarted the mess again, after it slept new years night.
BTW. conversion of web pages to the print mode don't work at all:
Failed to load article from page