The Librem 5 team needs a GNOME Web that ships with a list of serach engines that work on mobile and has reasonable results. We need this in GNOME Web ASAP because we'll be shipping the phone in the next couple of months, so for us this is a high priority.

@jeremiah.foster , here is the tracker issue we were talking about in the L5 team meeting today

Related Librem 5 feature: https://source.puri.sm/Librem5/use-cases/issues/25

I forgot to mention that the broken version of uuu is:
Version: 1.2.31-0+pureoslibrem5.2

I selected the default partitioning option.

The non-comments in /etc/crypttab are:

After the update-initramfs and reboot, I always get prompted to decrypt the / partition first and then prompted to decrypt the swap partition second (checked the uuid's against lsblk to determine this). This order is always preserved.

I have seen on the live installer that sometimes when I enter the passphrase a second time to confirm, the installer crashes and needs to be re-launched. This behavior happens sometimes and is not consistently reproducible but it happens frequently enough (when installing to a libvirt VM anyways) for it to be annoying, maybe ~25% of the time. Matthias thinks my issue is related to T547 so recording the behavior here.

A new image was built and I installed it (https://downloads.puri.sm/playground/2018-08-23/pureos-8.0-gnome-oem_20180823-amd64.hybrid.iso) in virt manager. After the install completed, I was prompted to reboot. Right after the reboot, I was prompted to enter the disk encryption password:

@wellton Yes, your issue appears to be due to using libreboot instead of using the image as is. I'm not sure what @mak 's plan for support of libreboot is going forward but for now to fix your issue, I'd recommend you use the https://downloads.puri.sm/live/gnome/2018-05-30/pureos-8.0-gnome-live_20180530-amd64.hybrid.iso as it is with no changes.

The md5sum of the 0426 and 0530 isos are definitely different:
452765b43d9223c7cb7fee6fbdf2357f pureos-8.0-gnome-live_20180426-amd64.hybrid.iso
7ffc352ba28b954922fe9d3739f8460b pureos-8.0-gnome-live_20180530-amd64.hybrid.iso

The issue was caused by allowing an openvpn-based vpn to start automatically on boot. The vpn config file ran /etc/openvpn/update-resolv-conf which ran /sbin/resolvconf (or exits if the resolvconf package is not installed). So in the case where the resolvconf package is not installed, there is no problem if you boot the system and stop the vpn. However, the resolvconf package was causing the default nameservers to be 192.168.237.*

Hmm.. so I have been running a script just after reboot that does some post startup things, including setting the keycodes. If I disable the running of that and reboot, then it appears that my keycodes are magically working again and I have no idea when this started working.

My systemd version is 238-4

Sorry for the late reply. I have a L13v2 with a US keyboard. After I reboot my Librem, I always do sudo setkeycodes 56 43 and that fixes the issue.

(seems I forgot to actually post this yesterday)

Since recompiling unstable packages in PureOS is recommended, is it just as easy as adding a source site to a list and then that site is polled for updates? I am assuming that these packages are auto compiled by the build system?

Another point to consider:
When implementing this we must consider that the Librem5 might have forks of important libraries with patches that are either:

• not upstream yet since they're still in review
• not in the version that is currently in Debian testing Therefore we should cater for a way to build packages on or own until we get the correct version from Debian.

Adding the full syslog error containing all of the call traces{F44013}