Ublock origin update4/11/2023 ![]() webext-ublock-origin_1.19.0 solves the problem. beginning of T272 for brief hints on that just tested installing webext-ublock-origin_1.19.0+dfsg-2_all.deb from bullseye in a new image of PureOS Amber in a VM. The inability to remove uBlock Origin independently of PureBrowser is a management decision which I personally disagree with but have obeyed (see e.g. where you came along) helps is to know if also packaged-for-PureOS versions solve it.įor further (beyond what has already been established here by now, which is appreciated) sharing and discussing and comparing _workarounds_ mixing PureOS with outside-of-PureOS code I recommend to do so at where others might appreciate such details. To spell it out for you, it has already been identified that newer-than-packaged-for-PureOS versions of uBlock Origin seem to solve this issue, and what then (i.e. I don't need or asked for apology, only inform what is helping. Thanks also for your lesser related notes, including vague references to your and my age (you win the pissing contest when including your Fortran experience even if "behind" by ~11 years on linux - more power to you). I appreciate your politeness and apologize for any of my testiness about remaining on-focus. ![]() ![]() While everything I report may not be totally on focus, I strongly believe, and hope, it will help in solving any problems using ublock-origin in the PureOS environment. Furthermore, ublock then behaved as it did prior to the latest update of purebrowser to version 68.0.02-1pureos3, in remaining enabled after exiting and reopening the browser and in filtering as it should. I then installed webext-ublock-origin-1.22.0 from GNU FSF and this did put ublock in the list of enabled addons. This failed to put ublock origin in the list of enabled extensions at about:addons I then did apt-clean followed by apt install purebrowser which then reinstalled the two!! packages I had purged. I then did apt purge webext-ublock-origin, which for some reason not clear to me also removed purebrowser-68.0.2-1pureos3 as well as version 1.18.4+dfsg-2 of ublock, the same version I installed previously from amber. required to false from their defaiult of true.Īlthough off-focus, this allowed me to finally uninstall privacy-badger, not from within purebrowser, but using apt purge webext-privacy-badger. I think you should pay attention, as you have, to what I report for two reasons I have been solving (and causing) programming problems since likely before you were born, and I have solved the problems I initially told you about.īefore starting, I set in about:config and xpinstall.whitelist. I apologize for not providing more information about version numbers, but not for going off-focus. I joined this thread because I had two problems I thought were related to the subject matter. Purebrowser presented what seemed to be Firefox home page with quick links to stuff like facebook, and the icon for the Firefox account (see the first picture bellow).īellow are the pictures of the different steps of this process In this process i did noticed other things that i do not know if they are normal: Just reloading the about:config page after enabling Firefox compatibility mode, and then reloading the about.addons page. So i retraced my steps by doing the process again from an image in GNOME Boxes.ġ - did a sudo apt update & sudo apt dist-upgrade, only update available was purebrowser 68.0.2esr-1pureos3Ģ - launched purebrowser, uBlock Origin was not availableģ - Followed this tutorial to enable Firefox compatibility mode so i can install addons: firefox_compat_modeĤ - reloaded the addons page, from that point on i was able to install more addonsĪll these steps in Purebrowser were done without closing it and launching it again. what is probably more interesting is what you did in-between: Did you start PureBrowser while the addon was removed?
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |