The plot thickens

So if this is going to be PureOS specific then we need to discuss this with @francois because he'll have PureOS related material that I imagine we'll want to use. If it is not meant to be PureOS specific, just a generic installer, then I don't really have an opinion beyond respecting existing copyrights and trademarks. I do hope to limit any customizations to images and slides that clarify what is happening for the user. I think it should be abundantly clear that the user is installing PureOS if that is in fact what is happening.

We have other requests to Mirror in Sweden and North America

A newer version of the GNOME Software application (gnome-software and gnome-software-common) still produces this bug. I think Matthias is pointing to the fact that the issue is in python-apt and that is independent from GNOME Software.

It's a nice image, but likely ought to be replaced.

It looks like the patch was put in upstream python-apt https://metadata.ftp-master.debian.org/changelogs//main/p/python-apt/python-apt_1.8.4_changelog
It doesn't look like we bring it into PureOS however. It appears at the moment that python-apt is being rebuilt;

I can confirm that our version of GNOME-Software is about 1 year old. I'll discuss internally how we upgrade.

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

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.

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.

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

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

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

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.

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/

It is complex, I agree. The screenshots help alot. I don't think that your swap partition is in fact encrypted. One way to find out for sure is to issue this command;

I experience that behavior on occasion as well. I'll try and do some debugging since I'm interested in understanding if there's a fix.

1. You have two "resume=" targets. The UUIDs differ too. You may want to compare the two resume target disk UUIDs with what you have in /etc/fstab to make sure that the last resume= is even needed. You can use the 'disks' tool to do this.

Can you re-paste your

/etc/default/grub

file? I don't see any mention of your encrypted disks for example. I worry your grub configuration may have become corrupted somehow.

emacs26 is not available in PureOS yet or in Debian. You can download it from here: https://ftp.gnu.org/gnu/emacs/

Here is documentation on how to build a PureOS image: https://tracker.pureos.net/w/howto_build/

From the file you posted I can see that USB appears to be working;

Well, before you do, issuing the command to show the kernel ring buffer might help us. Can you test with a USB device?

touche’

Omar, can you do a

sudo dmesg -w

then plug in a USB cable connected to a device known to work and put any error messages here?

How can something be "too stable" or "too unstable"? Isn't it kind of like saying you're too pregnant? Either your pregnant, or you're not.

Also, this will need to be uncommented;

Can you paste a copy of /etc/default/grub here?

I think that you can clear this up by doing;

This is very helpful @mak, thanks. I'll read up.

Comments that were removed can be discussed in a separate issue: https://tracker.pureos.net/T722

What does

Can you paste a copy of you grub.cfg file? Either here or in a pastebin somewhere? That might help debugging the issue. You grub.cfg file likely won't have any secret info, just things like the command line to boot your system as well as the UUID of your disks.

Nope. Installing libcanberra-gtk-module and libcanberra-gtk0 doesn't help.

I can reproduce this. I also get a message "Gtk-Message: 09:43:04.539: Failed to load module 'canberra-gtk-module'" when I run this so perhaps the error is there.

I commented out "GRUB_ENABLE_CRYPTODISK=y" in/etc/default/grub then ran sudo update-grub. This stopped grub from asking me for a password.

Also, could they provide more information, like actual log files or similar? Currently it is just port numbers and IP addresses which are no evidence of anything.

Did you run

Software and Updates starts, it just fails to find a distribution template for PureOS

In the grub package in Debian there was a configuration change that PureOS inherited. That change is the addition of an enabled display of the encryption password prompt. Can you check to see if there is a "GRUB_ENABLE_CRYPTODISK=y" line in/etc/default/grub ?

These are just warnings and do not affect boot.

I agree @mak, folks can install via GNOME Software.

I'll join you @guido. Let me poke around on this to see where I can contribute to packaging. In the meantime, I'm going to see if I can't get into the build tool we're using to see if I can't nudge a couple packages into showing up in the repos.

I think there are a number of extra packages in our default image. I hope to collect a list of those and winnow down our images to improve security by limiting surface area and to limit the amount of applications we have to support.