@mak I tested GNOME OEM https://downloads.pureos.net/amber/oem/gnome/2020-07-18/ on baremetal

Selected "swap with hibernation", and also selected to have full disk encryption.

After the installation was completed rebooted a few times, and updated initramfs, just to mess with the /boot files. Rebooted 3 times. LUKS worked every time.

To reply to your questions:

Does the image boot cleanly?

Yes,

Does the OEM installer work?

Yes it acts as expected.

Does the OEM initial setup work as expected?

Yes it worked as expected

Does the respective desktop function as expected?
Any noticeable bugs/regressions?

I did not noticed any regressions

In addition for this image, please look out for:

Any issue with the installation process?

No

Can you get the OEM initial setup to accept an invalid username? (uppercase letters, etc.?)

No I was not able to make a the initial setup accept a username with a uppercase letter.

One note on the UX, the patched version of the initial setup, does not allow the setup to proceed if the user tries to use an uppercase in the username but it does not provide the user an error message explaining why he cannot proceed.

Maybe we could consider in a next release adding to the text of that page of the setup a sentence like: "Use only lowercase letters for your username", so that the user has some explanation on why he cannot proceed

But the Live image and the Plasma image still need testing

also I would add @richard.kolla and @mladen to this issue. As they might want to make tests as well

OEM GNOME

Does the image boot cleanly?

Yes

Does the OEM installer work?

Seems to

Does the OEM initial setup work as expected?

Won't boot.

Any noticeable bugs/regressions?

I erase the disk, install on my SATA SSD with the bootloader going to the MBR of the same drive. Can't boot from the coreboot 4.12-2 boot menu. Will need to confirm with Carlsbad what settings they use when installing PureOS OEM and use those same settings to test.

In T919#17068, @richard.kolla wrote:

[...]

Does the OEM initial setup work as expected?

Won't boot.

Any noticeable bugs/regressions?

I erase the disk, install on my SATA SSD with the bootloader going to the MBR of the same drive. Can't boot from the coreboot 4.12-2 boot menu. Will need to confirm with Carlsbad what settings they use when installing PureOS OEM and use those same settings to test.

Does this work with the old image we currently use, or is this broken there as well? In any case, quite concerning of booting after the OEM setup fails - do you get any error message, if so, which one?

@all but especially @richard.kolla : Can you please test the 2020-07-22 image? There were now functional changes, only minor bugfixes from Debian and security fixes (so I expect everything to still work as before).

@mak Tested 2020-07-22 OEM on my Librem Mini. It installs and boots just fine!

Only bug is that during the install, you can select encryption but will allow you to proceed without entering a passphrase.

And a follow up. When the disk has partitions on it, the installer won't allow you to select 'Erase Disk'. I have to install gparted to delete the partitions before the 'Erase Disk' option is available. Don't know if this is a bug or on purpose.

The image has been updated to incorporate the latest security fixed for a bunch of vulnerabilities in GRUB (less relevant for us if /boot is verified anyway, but still good to have, especially for custom installations).

I'll be able to test this next saturday

Nice! If nobody vetoes this image until next Monday/Tuesday, I will send this image to the factory and marketing people - we really have to update the default image, and especially that OEM username issue is causing very frequent support issues, so it has to go (not to mention the huge amount of security fixes that newer PureOS releases contain and that just aren't there yet with the current images).

Ran GNOME OEM on my LMv1 and GNOME Live on L15v4:

Does the image boot cleanly?

Both yes

Does the Live installer work?

Yes but doesn't seem to boot from PureBoot

Does the OEM installer work?

Yes no issues

Does the OEM initial setup work as expected?

Yes

Does the respective desktop function as expected?

Yes

Any noticeable bugs/regressions?

GNOME Live was installed onto second SSD of L15v4 running PureBoot B13. PureBoot see's the second SSD but won't show any of the /boot files in the OS Boot Menu. That is even after running both os-prober & update-grub from my main install.

In addition for this image, please look out for:

Any issue with the installation process?

None

Can you get the OEM initial setup to accept an invalid username? (uppercase letters, etc.?)

Didn't try but can if asked to.