Thank you for the quick review & validation! :-)

This isn't actually a high priority issue, as it's only a visual/terminology thing. Will need input from the marketing team though, I think we canonically only call PureOS "PureOS" and not mention Linux (internally, GNU/Linux is used for PureOS though, so this may need to be changed).

It would be possible to alter the word Linux by GNU/Linux?

Hello @mak , Yes, the installation Finish all right =) I used iso 2019-05-01, its in my production notebook. Congratulations for your project. see...

This is resolved starting with the 2019-05-01 image builds.
Thanks for reporting this issue!
Since the installer changes are extensive this time, it would be awesome if you could test the new image and verify that the issue is gone. New images will become available on https://downloads.puri.sm/live/gnome/2019-05-01/ shortly.

To avoid packaging a third-party extension with PureOS, a solution I propose is to include the following about:config value string to PureBrowser:

Yes. That's the one I am following.

Are you following these instructions: https://tracker.pureos.net/w/installation_guide/live_system_installation/ ?

With support by email I was able to boot with a live cd and backup my files, although some of them in my home directory couldn't be backed up due to lacking permission. After doing that and panicking less a bit, I provided the content of the crypttab file to Mladen and he suggested to comment

My understanding is swap re-encryption enabled on reboot provides a higher level of security while losing the functionality you describe, namely resume after hibernate.

I too get "secure connection failed" in PureBrowser. I don't know why that happens. I downloaded the certificate but I see no apparent issues with the cert.

I think what is happening is that it is looking for the old key on your old drive and not finding it. (Hence the message: "No key available with this passphrase"). Is there anyway you can re-insert your old drive and then copy the contents over to the new disk? Alternatively, you may be able to inform cryptsetup about your new disk.

@jeremiah.foster Hello! I tested again (up-to-date libraries as in your comment) and still get the error.

In T347#11724, @mladen wrote:

Wiki entry for TorBrowser: https://tracker.pureos.net/w/pureos/tips/torbrowser/

I Will redirect the index (page web) from https://pureos.net.br/ to https://pureos.net .

Thanks, no problem, I understand perfectly I'm waiting so that in the future we can have a pureos.net here in Brazil.

Hi David,

Hi wellton. Thanks for mirroring. I understand that downloads from our official sources can be slow. We are in the process of setting up mirrors worldwide and would love to add yours as a potential partnering mirror. However we have not developed a fully complete policy with regard to mirroring. At this time the feeling is that Purism would prefer that the 'pureos.net' name wasn't included in your mirror URL if at all possible. It seems to imply that yours is an 'official' mirror and ought to get 'official' support.

webrtc progress: https://blogs.gnome.org/tsaunier/2018/07/31/webkitgtk-and-wpe-gains-webrtc-support-back/

That's because of the 'su $user' command that's in there. Root doesn't have to type the user's password but a regular user (even the same user) does.

Hi @jeremiah.foster and @mak , I downloaded iso 04-22 (pureos-8.0-gnome-live_20190422-amd64.hybrid.iso) from link and not working.

At least I haven't partitioned the USB drive. :}

Yes, ENV{ID_VENDOR} is what we'd want, as ID_VENDOR is being set in an environment variable that gets passed along to these udev rules. I was just flagging that in your udevadm output it had set ID_VENDOR (via ATTRS{ID_VENDOR}) to Nitrokey.

The script does work when it runs by itself (always worth asking :-)

Based on this:

The format of the udev rule in the file itself may be the issue, I'm still trying to determine. Nitrokey offers packages: https://www.nitrokey.com/download/debian I'm going to see if they provide any inspiration.

The udev rule doesn't work in either machine; neither the L13v3 or L15v3. With regard to identifying the device, I'm included dmesg output (which I've not found super helpful) and udevadm output (which is better.)

So to get this straight, the udev rule works with your particular Librem Key on one laptop but not another? I wonder if for some reason the ID_VENDOR value changed from "Nitrokey" to something else in newer revisions of the Librem Key.

The rules file is in the right location (/etc/udev/rules.d) and it gets read according to systemd-udev:

Apr 23 10:02:36 slate systemd-udevd[386]: Reading rules file: /etc/udev/rules.d/85-libremkey.rules

The gnome-screensaver-lock works well. I cannot get the udev rule to be discovered on my L15v3 however. There is some information on this available on the Nitrokey from upstream where they publish their own udev rules but that fails to work for me as well.

@jeremiah.foster Please (not only update description but also) make a comment elaborating why you consider DuckDuckGo is really tracking users.

Eww, I don't think I have addressed this yet. Thanks for the issue report!

There is a new version of Calamares out and I wonder if this is still an issue? @hayder could you let us know if this bug is still open?

Thanks for reporting this issue. There is another new build, can you try that one: https://downloads.puri.sm/oem/gnome/2019-04-22/

Wow, what a marvel. now it worked 100% in ISO 2019-04-19. thank you.

emacs25 seems to only exist as a transitional binary package to emacs-gtk in PureOS:

emacs25    | 25.2+1-6+b2   | landing    | arm64
emacs25    | 25.2+1-6+b3   | landing    | amd64
emacs25    | 1:26.1+1-3.2  | green      | all
emacs25    | 1:26.1+1-3.2  | landing    | all
emacs25    | 1:26.1+1-3.2  | purple     | all

There appears to be some cruft in landing, but that has a lower version number so shouldn't be easily installable.
Are you sure this is still an issue?