To clarify: Does this issue appear in the live installer, or in the OEM installer on first run? (I suspect it's the latter)

Did you consider reporting this issue to GNOME as well?

@mladen.pejakovic As far as I know when installed (like on debian with the non-free firmware-atheros package) the firmware is loaded into a volatile memory of the wireless card. Volatile memory requires power to maintain the stored information. So when you restart, the firmware remains, when you shut down, wait a bit and then start your system the firmware is lost.

@stefannagy, that's interesting, I did use ArchBang (Arch based live system) before installing Parabola. And after leaving the laptop shutdown overnight, bluetooth is now not working.

This just got fixed in the most recent round of upgrades.

@mladen.pejakovic Did you restart into Parabola from a distro with the firmware installed?

This looks like the same issue I'm having. My system uses English, so from the shell:

Does it look like this? If so, it's probably the same issue reported at https://forums.puri.sm/t/terrible-graphic-distortions-in-pureos/3612

Turned out not to be a problem with PureOS. After I played a bit with VBox settings the issue was resolved. I activated 3D acceleration, increased video memory to 128MB, upped usable RAM to 3GB and gave permission to use 2 CPU cores.

I am currently on Parabola GNU/Linux which is a Libre distro. Bluetooth working fine on Librem 15v3.

You are right. I created a new task: https://tracker.pureos.net/T538

I get massive CPU activity and a black VBox screen.

I experienced the same problem. After finding this thread and plugging in "pureos" as username on my VirtualBox running on Ubuntu I get massive CPU activity and a black VBox screen.

My new RAM is CT16G4SFD824A C16FE
My old RAM was CT16G4SFD8213 C16FH1

Since this was just mentioned again, I need feedback here... Go, or no go?
/me is for dropping it (at least temporarily).

is this a possible relation too https://tracker.pureos.net/T530

possible relation too
https://forums.puri.sm/t/battery-drain-while-suspended/2726/10
and by extension
https://tracker.pureos.net/T419

This is a meta-issue spawned from T534#9657

as you wish.

It is a package manager. You can use it to install a .snap file (snap package) that you have downloaded by some other means, or that you have built yourself locally:

There should be no Mozilla or Firefox references in PureBrowser. This will obviously lead to confusion.

What is the purpose of snapd other than to download packages from external sources?

Thanks for clarifying.

Knowledgeable users will already understand that PureBrowser is a privacy-respecting fork of Firefox (i.e. based on Mozilla technologies). But I suspect (untested) that an everyday user would wonder:

Can you please elaborate how a reference to Mozilla in a Mozilla-based product can lead to confusion?

I've reassigned this to myself to post these steps on the https://tracker.pureos.net/w/troubleshooting/ page.

Looking forward to the fix! Created https://tracker.pureos.net/T534 for the Mozilla logo issue.

For the record: This issue was fixed by favoring DuckDuckGo over other search engines for all locale regions.

This issue is solved since release 52.9.0esr-1pureos3, uploaded to landing today August 8th.

@d3vid Reference to Mozilla in upper right corner is (at best) a different issue than this one: Please file separately if you believe that should be somehow addressed as well.

This issue is solved since release 52.9.0esr-1pureos3, uploaded to landing today July 8th.

This issue is solved since release 52.9.0esr-1pureos3, uploaded to landing today July 8th.

@james.rufer This issue tracks PureBrowser advertising itself as Firefox on the Start page.

Thanks for sharing. I do believe, however, that wiki is a better medium for sharing best practices than an issue tracker.

@EchedeyLR thanks - that is indeed an idea worth considering (and testing if results are decent or inadequate).

Status in Debian is tracked at https://wiki.debian.org/FingerForce

I proposed this for your idea: "Other solution could be that your self-hosted searx instance only uses free search engines like gigablast (just allowed) and findx (not allowed yet)."

@EchedeyLR seems there is some miscommunication here: I really appreciate your input and simply added some additional data points.

Look, I'm sorry I wasted your time, but arguing is not mine, in fact, I do not like it. I will limit myself to report the technical problems that I find in PureOS and I will also report the solutions that I find if I find them, and if not, avoid using it.

Anyway, read all my message.

I have not denied it, i just said "Personally, i have not found ads on FindX search, it could be because i am using adblock plus... then, the adverts should be easily lockable."

FindX is not _personalised_ ads but search-term-based ads - for now only shopping-related: https://www.activateprivacy.com/how-private-search-engines-make-money/

Mmm, Gigablast should run without js, it has another options to show banned results, you can add your own domains to the crawl queue but, his code is a bit outdated.

@EchedeyLR Please see above (sorry, forgot to mention your nick before).

Thanks for pointing to FindX and GigaBlast.

php-facedetect is available in Debian unstable, but was removed from Debian testing (which PureOS derive from) some months ago, as (vaguely, in the news section in the middle) indicated at https://tracker.debian.org/pkg/php-facedetect. The cause is that the package is weakly maintained in Debian - specifically it needs its maintainer contact address updated since the switch from Alioth to Salsa as main development environment in Debian.

Why are you deleting the package every time?

Because I'm not changing the version number.

Maybe the "language packs" could exist in the repository even before the installer is fixed so that non English speaking people would have a way to add their language graphically through the Software app?

This T299 is now a meta-issue tracking the various ways that Mozilla addons service is getting promoted, and the main issue of the integrated addons support using Mozilla by default is now tracked at T305.

@d3vid The promotion of Mozilla addons service via Home screen is now tracked in separate issue T532.

In T526#9520, @chris.lamb wrote:

Why are you deleting the package every time? That does not seem the usual approach or at least it has never been required before.

This issue is solved since release 52.9.0esr-1pureos2 (see T247), uploaded to landing on July 5th (and likely entering green ~10 days later).

This issue is solved since release 52.9.0esr-1pureos2, uploaded to landing on July 5th (and likely entering green ~10 days later).

@james.rufer yes, I did not mean to imply that this issue is not still open (the status in this very issue tracker is "open"). I only meant to ensure that if you had some additional information, that I then did in fact understand what that was.

Why are you deleting the package every time? That does not seem the usual approach or at least it has never been required before.

Oops, I had a typo in my watch file so now I need to delete the whole package, including the previous comments. :(

New clamav release 0.100.1+dfsg-1pureos1 uploaded just now should fix this issue (when it enters green in ~10 days).

Thanks, just uploaded the new version there, should be visible in a few minutes. Both packages should be visible - I fixed the "-+" from the version number, so it's not the same version, so both should?.. be there at the same time.