Thanks to Birin Sanchez for this work around, tested here with a slightly later version 6.0.5-2, and functioned as expected.

Please note the following append for LibreOffice Calc not starting (sigh).

I have a brandnew Librem 13 and installed the newest available PureOS version. Updated it in full and now it doesn't boot in normal or recovery mode, so I suppose it will be quite easy to replicate this issue..

I did experience the same kernel panic as described above with brand new laptop at several occasion:

reporting bugs is not an accurate science - it is highly appreciated that you filed a report when only suspecting a potential issue here, @Wayne !

I do not think there is a problem with either DuckDuckGo, without a more information, or the Purism Forums.

Looking at GNOME's Screenshot with Strace I don't see a call to external networking resources. Running this command;

@Wayne yes I meant to suggest that you file an issue (here on tracker.debian.net, not in the forum) about our forum triggering warnings about fingerprinting.

@jonas.smedegaard, if you meant for me to do so, I do not mind opening a new task for the Purism Forums. I think, however, others are better equipped to do so and would have more detailed debug information to write in the comments. But is it necessary? Part of my point was that indications from CanvasBlocker and others are not necessarily showing that anything nefarious is happening, though it may be worth noting.

DuckDuckGo is using jQuery functions that check canvas size. Are they actually tracking users? I would prefer not to jump to conclusions here. This makes me skeptical: https://www.reddit.com/r/privacy/comments/ad4h0u/duckduckgo_now_fingerprinting_visitors/

The video mentions specifically a couple of items;

1. Tor browser launcher not installed on device at default. (16:33)
2. httpseverywhere not isntalled (16:59)
3. Google is the default search engine (17:32)
4. Does using the default Wayland build change settings in the browser (comments re: 13:33)

Thanks for those details, @Wayne!

Here is another data point on fingerprinting in DuckDuckGo.

DuckDuckGo is no longer privacy-protecting: https://forums.whonix.org/t/duckduckgo-now-fingerprinting-visitors/6497/1

Thanks Wayne, I'm glad to hear you're not dead in the water. Thank you for your patience as well. Sadly I didn't have time to drill down and find out more about the situation with dependencies yesterday, I hope to try and get some clarity on this today, but no guarantees as its a weekend. :-)

Thanks. I understand now.

In T666#12337, @Wayne wrote:

I do not understand your last statement.

I don't know how many releases of python there were like that but I can't imagine many.

I do not understand your last statement.

@jeremiah.foster Yes, this is one of the possible use cases.

apt show hplip

shows, among other dependencies, this line;

wget, python3 (<< 3.7), xz-utils, python3 (>= 3.6~),

which seems to imply you won't be able to install this unless your python is higher or equal to version 3.6.* but not 3.7. I don't know how many releases of python there were like that but I can't imagine many.

Having an acceptance criteria (AC) in the issue might help, we can put it in the Description. Having an agreed upon "Definition of Done" is also useful and you've provided an example of DoD we can use, when the issue is in Green.

Just for the sake of clarity, you want to install PureOS on USB attached drive? So you're looking to have a persistent version of PureOS on the USB drive?

I just completed a bluetooth transfer of a photograph from my Pixel to the Librem 13 v3.

I did an apt update and installed a new deb -- firmware-atheros -- and that helped the situation. I have Debian repos enabled, not sure if firmware-atheros is in PureOS repos.

I can confirm this, seeing similar issue.

[   18.375949] usb 1-3: firmware: failed to load ar3k/AthrBT_0x11020100.dfu (-2)
[   18.375954] usb 1-3: Direct firmware load for ar3k/AthrBT_0x11020100.dfu failed with error -2
[   18.375956] Bluetooth: Loading patch file failed
[   18.375964] ath3k: probe of 1-3:1.0 failed with error -2

Done. This was satisfying, not having to deal with the build of this beast it great!

Thank you.

Yes, that would be my advice. You can do a dist-upgrade anyway and try and fix your system if it gets in a misconfigured state, but that can be time consuming and difficult. Usually with ten days or so that type of package conflict goes away as new software and bug fixes come into the repos.

So, there is a kernel panic because the kernel can't seem to find a file system to mount. How did you install GNOME? Did you use a USB stick or an ISO or similar? Or are you using apt-get or some other means?

The Librem's have a version that I think represents the physical device on the back, one of my Librems says "Librem 13, version 3." If you want to find the software version, or version of the overall OS, try this command (you may have to install inxi);

$ inxi -Fxrz

Which on my system produces;

System:    Host: sigmund Kernel: 4.18.0-2-amd64 x86_64 bits: 64 compiler: gcc v: 7.3.0 Console: tty 1 Distro: PureOS 
           base: Debian buster/sid 
Machine:   Type: Laptop System: Purism product: Librem 13 v3 v: 3.0 serial: <filter> 
           Mobo: Purism model: Librem 13 v3 v: 3.0 serial: <filter> BIOS: coreboot v: 4.7-Purism-4 date: 03/20/2018 
Repos:     Active apt repos in: /etc/apt/sources.list 
           1: deb https://repo.puri.sm/pureos green main
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian stretch main contrib non-free
           2: deb-src http://deb.debian.org/debian stretch main contrib non-free
           3: deb http://deb.debian.org/debian stretch-updates main contrib non-free
           4: deb-src http://deb.debian.org/debian stretch-updates main contrib non-free
           5: deb http://security.debian.org/ stretch/updates main contrib non-free
           6: deb-src http://security.debian.org/ stretch/updates main contrib non-free

You can see from output above that I'm running a 4.18 kernel. My distro is PureOS based on Debian Buster / Sid (so testing) and that my repos are PureOS 'green' mixed with Debian stretch. In the "Machine:" line I note that coreboot version is 4.78-Purism-4 from 03/20/2018. PureOS "green" may be a rolling release which means that the userland packages (and kernel potentially) are updated continually.

I believe @kyle.rankin mentioned systems were shipping with the June release due to issues, but this was a month ago. How can I check the version shipped on my unit?

I think the problem in general is that python3 was upgraded to 3.7 and several packages are dependent on python3 being less than 3.7. (Note the "Depends" line above. hplip also shows python3<<3.7 if one runs apt show on it.) I have the same problem with apparmor-utils and opened a new task, not having previously looked at this one. I noticed hplip--I don't use it to my knowledge--was also uninstalled for me on 12/20. This was the same update with python3 going to 3.7. Unfortunately, I am dependent on a Purism-modified package for python3-libapparmor. (The one in buster shows python3 << 3.8 as the dependency.)

Same problem? https://tracker.pureos.net/T657

Seems that website doesUser-Aagent sniffing.

I think that the version of PureBrowser you showed there is quite old. I wonder if we need to discuss with the distributor about updating the software on the devices? I propose we bring this to a Production / QC meeting.

Is this a duplicate of https://tracker.pureos.net/T595?

Confirm. Since PureBorwser identifies itself as PureBrowser, instead of Firefox, the addons site thinks you are not using Firefox and won't let you install extensions.

Firefox developer version (redish color) vs PureBrowser (greenish), side by side, loading the same page on PureOS

Is there any chance we'd have the UEFI support in PureOS 8.0 Release?

I'm going to go ahead and wontfix this as most of the changes are not appropriate to Debian and should be handled another way anyway, not via a "config package".

Link dump:

@kyle.rankin Okaley, so what's the next step here? This should have hit PureOS by now :)

Pinged upstream bug: https://gitlab.com/lamby/osinfo-db/merge_requests/1#note_127118132

Pinged Debian bug...

Okay, thx. I tried it because I did not want retainet packages. Then should I wait theses packages can be upgraded without theses conflicts?