PureBrowser downgraded to 60.x, again fixing this issue.

Thanks, that's quite helpful @richard.kolla !

@jonas.smedegaard uBlock Origin is back in my PureBrowser.

PureBrowser is now downgraded to 60.x in PureOS amber.

@joao.azevedo Can I ask you to please confirm that PureBrowser as of today fixes tis issue, specifically?

Hi @tbernard - sorry I didn't ask back when this was reported which versions of PureBrowser and Ublock Origin you were using.

Thanks a ot for confirming!

This was the Purebrowser upgrade:

@jonas.smedegaard did a

...actually: @joao.azevedo please try update your system and tell me if this is still an issue on PureOS amber as of today?

Thanks for reporting this.

Which version of PureBrowser is this?

Which version of PureBrowser is this? See also T823

@jonas.smedegaard can i ask you to have a quick look in this issue description to see if this is worth investigating or if i am being silly

@Squid this issue is a clearly a duplicate of issue T814 were the cause of the problem with uBlock Origin has already been identified. And a temporary solution until the issue can be permanently resolved.

As for user notification, I suggest borrowing from how needrestart does it: Provide a purpose-specific GUI as a separate binary package, and have core package suggest either that or libnotify-bin, where the latter spews simpler notifications.

It might be documented, but since I am lousy at reading documentation here's how I'd figure it out:

@jonas.smedegaard I'm sure it was your idea :D

please describe in *words* what is the issue reported.

To test, try install debian-security-support and afterwards binutils.

@d3vid Interesting idea. We might use a similar approach as Debian package debian-security-support.

This issue is not about feature updates or enhancements.

Although most security patches have been backported to 60.x, I'm pleading against reverting to 60.x because we will be missing out on important feature updates and other enhancements.

I'm experiencing a similar issue. Bluetooth will stop working sometimes after unlocking the session / resuming from a suspend. Restarting the bluetooth daemon does not resolve the problem.

Thanks for sharing this helpful information, Becasue most of the search engine are not safe to use, many search engines save cookies of the user like google. So I always use vpn for extra protection.

@jeremiah.foster There was a time when we were concerned about including tools like pip [1] in PureOS. My understanding is that we have since decided this is not a grave or urgent concern, but we would still prefer to issue a warning when the user installs a tool like this.

{F333687}Hmm. I only know that I had been previously able to access it without issues on Chromium with uBlock Origin and HTTPS Everywhere from Google As a side note, uBlock Origin from Google was significantly more tolerant to trackers. Needless to say that I don't intend to re-install Chromium or ever again get any add-ons from Google.

An error occurred during a connection to error.woolyss.com.
This problem can sometimes be caused by disabling or refusing to accept cookies.

Fixing this awaits Debian package maintainers for firefox-esr to release their git sources for the newest bugfix release firefox-esr 60.9.0esr-1~deb10u1

@mak Could you, please, package this thing in Amber so we can move on? Much appreciated in advance.

Please respect my unsubscribing from this issue. Please don't subscribe me again.

Either this is a needless duplicate of T814 or it is a call to leadership about special-treating T814. In either case my participation is irrelevant.

In T790#15491, @EchedeyLR wrote:

I think you were writing about https://kde.org/applications/internet/org.kde.ring-kde which is the KDE version of Ring/Jami

Until recently T814 we didn't know whether it was a PureBrowser issue or a Ublock issue. I think it is fair to assume that as soon as Ublock gets re-packaged in Amber, we can close this down. Some relevant aspects have been touched upon, although not strictly related to the task. A task should never diverge from its intended purpose or duplicate another task. It is indeed easier to merge than to split although enforcing separation is not always easy or even possible.

I think you were writing about https://kde.org/applications/internet/org.kde.ring-kde which is the KDE version of Ring/Jami

sudo dpkg -i webext-ublock-origin_1.19.0+dfsg-2_all.deb
[sudo] password for squid:
(Reading database ... 152660 files and directories currently installed.)
Preparing to unpack webext-ublock-origin_1.19.0+dfsg-2_all.deb ...
Unpacking webext-ublock-origin (1.19.0+dfsg-2) over (1.18.4+dfsg-2) ...
Setting up webext-ublock-origin (1.19.0+dfsg-2) ...

@jonas.smedegaard Ok, just repeated the steps above. The only difference was that i did not opened purebrowser before installing the 1.19.0 package from bullseye.

Here is a screenshot:

I 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.

I think it is unlikely that anyone in Purism staff will take on the task of packaging a fork of Chromium: Our priority is on a web browser usable both on desktops and phones, and the main contender there is GNOME Browser a.k.a. Epiphany.

Neither KDE nor Gnome can make browsers because neither of the 2 communities are in the browser business. Deny it! So it makes perfect sense to re-use the code base of either Firefox or Chromium with some adjustments. That's what all sane projects are doing. If you don't want to deal with Firefox anymore, then may I suggest making ungoogled-chromium the successor PureBrowser? I'm kindly submitting to your attention the following link and all the links within the link: https://chromium.woolyss.com/ Thank you.

You (or anyone else you might convince to take on the task) are recommended to get your browser of choice packaged for Debian officially. Then if it complies also with GNU guidelines it will automatically get included with PureOS as well.

T814

Until you've got something that is good enough to replace PureBrowser, you should absolutely fix PureBrowser. I've been thinking that Falkon is underdeveloped. Well, with all due respect, GNOME Web is even more underdeveloped. Are you even using it at all? Can we please think deeply and rationally for a second? Can we please not give in to our emotions and think from a technical perspective? Please have PureBrowser fixed! Close it down if it makes you happy but I suggest you leave it on the board. Thank you.

@joao.azevedo Could you please test if installing uBlock Origin package from Debian testing on top of an up-to-date (and clean, no Mozilla or other non-PureOS-origin code added) PureOS amber install fixes this issue?

https://about.qwant.com/ +1

I've just checked GNOME Web and it is not ready for real-world usage. It is very basic and has absolutely no tracking protection whatsoever. Currently the only browser that is usable is Chromium. With Ublock from Google :-)

Thanks for hint. Yes, Metager is on GitLab: https://gitlab.metager.de/open-source/MetaGer

WebKit is in fact the same browser engine that Apple's Safari uses. https://webkitgtk.org/

@todd If we can't deal with this issue in-house, maybe we should out-source it to people who specialize in browsers. What do you think?

https://nabeards.com/posts/pureos-install/

In T710#14825, @elias wrote:

Is there any workaround for this, any way to install PureOS on a UEFI system? I would like to try PureOS on my laptop but it seems I am stuck due to this issue.

In T821#15452, @jeremiah.foster wrote:

The plan is actually to deprecate PureBrowser as Mozilla doesn't share the same goals we put forward and that makes it a lot of work to ensure that our user's privacy is protected.

Understandable and I don't intend to be rude or disrespectful. I have read other posts where this particular request appears to be parked repeatedly. I'm at a desperation point and only intend to imply the desperation and not to offend anyone or hurt anyone's feelings.

The plan is actually to deprecate PureBrowser as Mozilla doesn't share the same goals we put forward and that makes it a lot of work to ensure that our user's privacy is protected.

I don't think this is the way to request for support. Please be kind and read other issues related with your problem first.

@Badger that not was all the idea...

@EchedeyLR thanks for pointing there, but it seems nobody has evidence of fingerprinting by DDG.

Thanks for your details about PureOS.

Dear @jonas.smedegaard ,
I joined this thread because I had two problems I thought were related to the subject matter. I apologize for not providing more information about version numbers, but not for going off-focus. 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.

@emmes Which version did you install from PureOS Amber? Info should be available in /var/log/dpkg.log even if you since removed it again.

I installed three different versions of webext-ublock-origin. 1 from pureOS amber. 2 from github. 3) from gnu. In my hands, they all behaved the same as I described.

Thanks for your additional info, @emmes

emmes would like to comment on his experience with purebrowser-68.02esr from the amber repository.
I was able to install webext-ublock-origin and it initially worked as it should. After an exit and relaunch, the icon was missing from the menu toolbar and the add-on did not work. It can be made to work by going to Add-ons, disabling it and then renabling it. A second problem with purebrowser, which may or may not be related, is that once Privacy badger is installed, it cannot be uninstalled or reported.

If it is the same issue then according to that issue tracker thread it should be fixed with ublock-origin/1.18.10+dfsg-1

@joao.azevedo Yes, that could quite likely be same issue as this one!