I think it is unlikely that anyone in Purism staff will take on the task of packaging a fork of Chromium: Our priority is on a web browser usable both on desktops and phones, and the main contender there is GNOME Browser a.k.a. Epiphany.

@jeremiah.foster It seems to me that the issue of using a self-signed certrificate is orthogonal to the issue reported here.

In this case;

I would investigate further because we quote 4k 30Hz output on the v4 Librem Laptops and we can't if they seem to be tied down to 1920x1080p output.

Still no update from the command-not-found repo, and no progress on T638 so far, so I guess removing command-not-found altogether is the best solution for now 🤷

Yes, I think you're right. We'll discuss this and assign internally.

Between this and the subtask added by Jeremiah, is this a hardware issue or software issue?

E-mail below from customer having issues outputting more the 1080p on his Librem 13v4. Not running PureOS but similar issues. E-mailed back and forth a bit and he ended up running his monitor at 1080p and is no longer having issues.

Did you check the hashsums on the USB drive for the image?

When I surf to the https://giantitp.com I get this message, which seems to point to some serious misconfiguration;

First test image created: https://cloud.docker.com/repository/docker/miahfost/pureos

If you run "Self-Test" from GNOME Disks then I do not see any other course but to try another disk. If your device is still under warranty contact Purism support, we'll handle there. (I see that your laptop is Librem.)

@mladen any other suggestions?
I could try with an even newer version of the kernel, like 5.2.9, would that make sense?

I found Guido's pureos.sh script upstream: https://github.com/agx/debuerreotype/blob/pureos/pureos.sh

• use https://github.com/debuerreotype/debuerreotype/pull/63
• then s.th. like (just a quick hack):

@guido If you were to outline the steps you took for creating the 'green' docker image, I could follow that and put them into a pureos.sh script to submit upstream. I'm also setting this up to be automated.

@mladen I already ran the Disks disk check utility (see comment Aug 13) and the disk is OK.
Ran it again, still OK.

This may indicate that your disk is failing. Start a live media (PureOS or Ubuntu) and check it for errors:

@mladen I just installed Ubuntu 19.04, sporting kernel version 5.0.0-25 and the issue persists!! The laptop fails to boot intermittently, the only difference is that the following error message is displayed before the panic stack trace

error: failure reading sector 0x802 from `hd0'

negative, the issue occurs with 4.19.0-5 (See my comment above from Aug 13)

@louis This means you are not using the latest live PureOS install ISO, which probably has this issue fixed.

@mladen could you please provide details regarding what I'm doing wrong exactly?
Are you expecting 4.19.0-5 to not be affected by this issue, or the opposite?

@louis You are doing something wrong, 2019-07-14 live ISO version has 4.19.0-5 kernel version.

I already tried with that exact version of live PureOS, and the same problem occurs.

I can only suggest that you try with live PureOS, download the latest version from here please: http://downloads.puri.sm/live/gnome/2019-07-14/

https://tracker.pureos.net/T298 May be useful here as well.

Nope, only one, which is the 128 GB SATA SSD that came with the laptop.

That URL looks good and has some good resources. It also fits with my understanding of EDID and KMS.

Do you have two disks in your laptop?

@mladen I just tried reinstalling with the latest OEM ISO as you suggested, and the issue persists. Configuration was the same (swap with hibernate, disk encryption enabled).

So if it's pulling the wrong info from the EDID then we need to find a way to override it. I found this link https://wiki.archlinux.org/index.php/kernel_mode_setting#Forcing_modes_and_EDID and will delve into it later.

@louis I suggest that you use the latest ISO image: http://downloads.puri.sm/oem/gnome/2019-07-14/

So I reinstalled PureOS on the Librem13v4 again using the OEM usb key, and this time went for a apt full-upgrade directly, and the issue still occurs. I also tried installing PureOS using the live version and no swap, and after the installation, the problem occurs at every boot, without the couple minutes hanging time. Finally, I tried installing with the live version and hibernate swap (I think it's the default option when installing from the OEM usb key), and the behaviour is the same as originally (happens 30-40% of the time).

In T809#15183, @richard.kolla wrote:

PureOS defaults to Wayland and has for sometime as per my testing of old ISOs. Both the customer and myself are using Wayland. He tried X.org and got the same result he said.

There is a way at least find the capabilities of your graphics card to see if the card support's your screen's resolution;

PureOS defaults to Wayland and has for sometime as per my testing of old ISOs. Both the customer and myself are using Wayland. He tried X.org and got the same result he said.

reportbug is a debian-native package. This means its only meant to work with Debian. We'd have to do code refactoring for PureOS.

PureOS does allow for various screen resolutions as shown by the screen shot above. I configured my 34" screen via GNOME Display. I am running x11.

I'm closing this issue since Lollypop is now packaged for PureOS. I'm going to work with others on the team to see about integrating into CI/CD for L5. If there are any issues with the PureOS version of Lollypop for the Librem laptops, please open another issue. Thanks!

I cannot reproduce here with lollypop 1.1.4.11

@user22492 Is this with the PureOS package?

getting this error when running it

@omar.aboulhosn , we decided to work upstream with GNOME and so we don't want to promote PureOS by trying to re-invent the wheel with the hope that PureOS will be installed on a few more Thinkpads.

@mladen I reproduced the bug again while booting in verbose mode. The system sometimes hangs at Loading Linux 4.19.0-5-amd64, sometimes at Loading initial ramdisk.... Then after a couple minutes, the following line is shown:

error: failure reading sector 0x802 from `hd0'

and then the stack trace described above.

https://lists.puri.sm/pipermail/pureos-changes/2019-August/000411.html
Package is making its way into PureOS

Thanks a lot gusnan! :D

I just really wish there is more than just theming in their secret sauce. :D

Good link Adrien. I read the links to Tobias's article and to Sam's blog! Valid argument but whatever our competitor is doing, it's working (ok, minus the theming :)

They also have broken many apps by doing so: https://stopthemingmy.app/.

I don't know, at the very least the background should relate to 'Privacy and Security', even if not branded. Other than the menu options that show the switches off, *any* Linux operating system will run on our hardware.

GNOME itself is not over-branded anyway so that is perfect for us.

@francois Ah good too read, and I agree. :) I think mostly replacing GNOME's branding by Purism's should be sufficient.

@adrien.plazas , these were old proposals from James but we decided not to go this way and keep the branding at its minimum, so we will keep the application menu and background unbranded.

@EchedeyLR https://packages.debian.org/source/testing/chromium

Please file a _new_ issue instead: It might make good sense to use other addons, but that does not mean that the currently used addons are not working and therefore this issue is wrong to have "open".

In T57#14719, @jonas.smedegaard wrote:

@mak Please stop block chromium - it does not contain non-free code and is no longer unclear about licensing.

I submitted this to PureOS.

flashrom v1.1 updated in PureOS