Yes, the image I used is this one: pureos-8.0-gnome-oem_20180408-amd64.hybrid.iso. I even validated the sha256sum for the file, to make sure that it was downloaded correctly.

You got the image from https://downloads.puri.sm/oem/gnome/2018-04-08/ ?

I tried to use the latest ISO, and now I get the error that no kernel modules can be found when I try to run "Start installer", and the error that "/vmlinuz is missing", when I try the "Live ISO" option.

Hi Harvey,

Ah, it's on code.puri.sm. Getcha. Wfm now!

Sorry @chris.lamb. Gogs silliness. You need to be added as a collaborator to see it. Can you check now?

In T375#6988, @theodotos.andreou wrote:

https://code.puri.sm/Purism/Systems-Tasks/issues/58

It' here:

The priority on this is fine, this is a high-priority bug. After getting the debconf prompt once though, you will never see it again.
As for the config file prompt, that is a thing we can ignore for now (it's a minor annoyance regular users won't even see because PackageKit will do the right thing. It's also very tricky to resolve, we likely need to incorporate some changes in the Grub package itself).

Ok, so if the same changes ever pop up again I'll accept them (change GRUB_DISTRIBUTOR and drop GRUB_ENABLE_CRYPTODISK).

The config file change is harmless (I wonder why it's even shown), but the Debconf prompt should never have happened - this means the installer hasn't configured debconf for the GRUB package for some reason.

The reason this was fixed by forking apparmor (not including an apparmor snippet with purebrowser package) was to address generally the need of application needing access to browser to also be granted that for PureBrowser.

Since firefox-esr 52.5.0esr-1pureos2 released 2017-12-19, this issue is solved by renaming only binary package (not source package as previous), to stay closer to Deban and ease sharing our patches with Debian and other derivatives wanting to do similar.

In T363#6906, @jonas.smedegaard wrote:

Ah, it seems AppAmor contains a hardcoded list of web browsers, and needs to be educated about the existence of PureBrowser in the file

/etc/apparmor.d/abstractions/ubuntu-browsers

This was fixed since firefox-esr 52.5.3esr-1pureos2, released to PureOS landing 2018-01-21.

should be fixed in landing by now. Will keep this issue open until either someone using landing confirms, or it trickles into green and noone screams.

This issue is about following requirements defined by the GNU DFSG. Bug description is now updated to include relevant quotes from GNU FSDG.

Thanks for the update; I'll get this done as soon as I can, and report on what I find.

Thanks for confirming, @francois.

I can confirm that it is not an issue anymore on my side.

I will fork apparmor with that change...

Ah, it seems AppAmor contains a hardcoded list of web browsers, and needs to be educated about the existence of PureBrowser in the file

/etc/apparmor.d/abstractions/ubuntu-browsers

That smells like a problem with AppArmor blocking too much for Document Viewer.

Can you please try this again with the new OEM installer ISOs and report if that works successfully?

Hmm, popularity contest is not installed by default... Do you still see this issue?

Is this still an issue? I have never experienced this behavior on current PureOS.

At least in the past, we tracked all infrastructure stuff in public here as well (except for concrete machine requests), so I think having this issue here makes sense.

This should be resolved via T365 (doesn't fix the d-i problem, but still resolves the issue in PureOS since the install environment and regular PureOS environment are (almost) identical now, so touchpads work well).

Also, every one of these package managers will not download non-free stuff behind the user's back. Like APT itself or a webbrowser, it will download things only if the users has directly requested that.

This is impossible, as pretty much all of GNOME, systemd, Xorg depends on Meson, and no Rust code can be built without cargo properly at the moment.

@jonas.smedegaard We deliberately added TorBrowser this way when creating PureOS back in the day. I never liked this at all, so personally I would like to remove the package, but I am not sure if we should do that, because the decision to have it that way was done on purpose.
@zlatan.todoric should the Tor Browser package be dropped from PureOS?

Please drop our fork of torbrowser-launcher: It violates GNU FSDG in that we lack control over what code ends on our users' systems.

I believe this issue relates not to the OS we develop, but instead to the infrastructure we use for developing it - and therefore should instead be tracked at https://code.puri.sm/Purism/Systems-Tasks

This is somewhat a design choice of Wayland: One application should not be allowed to "spy" on the windows of other applications.

Calibre seems installable again now.

https://lists.puri.sm/pipermail/pureos-project/2018-April/000000.html

• Vcs-Git,
• Vcs-Browser
• Maintainer
• Uploaders
• +pureos\d in version string

I tested this on the devices I have, with no major issue, Everything is working quite well, and the remaining issues are UI things or relatively minor.
So, this task is complete now, and for all further issues with the live boot it makes sense to just have regular bugs (some already exist).
The new and final-ish image can be found at https://downloads.puri.sm/oem/gnome/2018-04-08/, the regular live images have also been rebuilt.

Hmm, Calamares doesn't set any DNS resolver, and resolv.conf is fully autogenerated on all PureOS systems. On my system, NetworkManager automatically configures a DNS server when I connect to a network.

The swap partition not-mounting issue is fixed now as well, but will a new image build (obviously) to take effect.
I will build a new image for testing next Sunday.

Hmmm it worked the second time around... on the VM. Going to test on bare metal now.

So, Calamares crashed? Please open a terminal, type pureos-installer-oem --debug and get it to the point where it crashes, then send me the terminal output.

By then I had initramfs-tools-core=0.130 0.130pureos1 installed. Then just after I've manually installed busybox-initramfs, initramfs-tools-core upgraded to 0.130pureos1 0.130pureos2.

Sorry, I mean the "Install PureOS" application that runs within the Gnome desktop crashed. By crash I mean the installer application disappeared. I will see how repeatable it all is.

What is "this application"? GNOME Initial Setup? What does crash mean, did it disappear? Can you send me your journal log (all of sudo journalctl > log.txt) in a private message?

I've had this application crash for me both when testing in a VM (at that point at the disk encryption password section) and also when trying directly on bare metal Librem 13v2, when trying to connect to wifi.

FTR, the new OEM image for testing can be found here: https://downloads.puri.sm/playground/oem/2018-04-06/
New known issue:

• swap partition is not mounted correctly with the new boot-reencryption mechanism, will be fixed in a future build

There is no officially supported net installer, and this is actually not supposed to work (or even tested).
Please install PureOS via one of the ISO images we offer on pureos.net
(there are also no plans at the moment to make a net install image work)

Hmm, which version of initramfs-tools-core do you have? That one should have pulled in busybox-initramfs and is default-installed on every PureOS installation (should be >= 0.130pureos2).
Please reopen this issue if you encounter the problem again, or are still having it. Also ensure that you are not accidentally on the landing suite of PureOS, because that's where there was a short time where the necessary dependency on busybox-initramfs didn't exist.

@zlatan.todoric LibreOffice build-depends on chromium, so this will be quite annoying.
Package is removed from PureOS now, but we will need to find a solution for LO...