@noe.nieto While you are at perfect liberty to install any flatpack you want, it is not in your best interest to install flatpacks that:

Am looking into this, but not simple due to upstream changes requiring additional Python libraries packaged.

@jeremiah.foster @mak not that update-initramfs did not fixed issues, but it made it worse: customer now cannot boot even the older kernel version.

In T788#14927, @mak wrote:

Thank you for the feature request, but unfortunately we'll definitely not have cdrtools in PureOS.
There has been an old fight about its license change which I really don't want to start again. Also, the legal situation didn't really change and Debian, the FSF and Red Hat all agree on this particular legal issue.
Plus, to put it frankly, Jörg Schilling is one of the least fun upstream developers one could ever deal with.
See https://en.wikipedia.org/wiki/Cdrtools#License_compatibility_controversy for some abbreviated summary of the licensing issue.
You can use cdrkit to burn optical media, or just switch to the much more modern libburnia which is used by many open source projects: https://en.wikipedia.org/wiki/Libburnia
GNOME's Brasero is using libburn anyway.

The user upgraded via sudo apt update && sudo apt full-upgrade and also did sudo update-initramfs -u -k all and here's the output:

Thank you for the feature request, but unfortunately we'll definitely not have cdrtools in PureOS.
There has been an old fight about its license change which I really don't want to start again. Also, the legal situation didn't really change and Debian, the FSF and Red Hat all agree on this particular legal issue.
Plus, to put it frankly, Jörg Schilling is one of the least fun upstream developers one could ever deal with.

@jonas.smedegaard Do you think it's worth packaging and if so who will be the maintainer?

@mak Can you make it happen?

In T792#14905, @gorgeous wrote:

I can do that, of course, but as I said already, this is happening for the 2nd time, after a new/clean installation from a USB flash drive with a PureOS8 ISO image. After installing some of the system updates, this issue appears. How can I be sure this would not happen again?

I can do that, of course, but as I said already, this is happening for the 2nd time, after a new/clean installation from a USB flash drive with a PureOS8 ISO image. After installing some of the system updates, this issue appears. How can I be sure this would not happen again?

@mladen Can we ask the user to do an apt-get update && apt-get upgrade? Otherwise we need to get more information.

A user recently upgraded via Software Center and had this issue. He can successfully boot *4.19.0-2* but the newer kernel (4.19.0-5):

@gorgeous I suggest you do a re-install, you will save yourself a lot of time. Your installation seems very broken.

Similarly we need to update the welcome screen (language page) of GNOME Initial Setup. I'm happy to patch the app, but for that we need to ship a logo to dislqy in the OS first.

@mladen & @Erik_Leroux please help me with this issue! :(
Many thanks!

Thank you!

Just FYI - in latest PureOS live/OEM images memtest (and also HW detect) are not working from the Grub menu.
This should either be fixed or the menu entries removed from Grub.

Using the Qt-version on PureOS and the status icons aren't really needed. The popup for allowing a device looks a little bit out of place, but it works flawlessly.

In T792#14834, @mladen wrote:

@gorgeous Did you try this procedure: https://tracker.pureos.net/w/troubleshooting/broken_upgrade/#problem-2 (solution for problem 2)?

@gorgeous Did you try this procedure: https://tracker.pureos.net/w/troubleshooting/broken_upgrade/#problem-2 (solution for problem 2)?

This has been updated a few days already, but the new images weren't fully tested yet (so aren't on the pureos.net page for download by default). That should happen this week.
Thanks for the heads up though!

@nicole you said "I am not sure if this issue relates to Coreboot," I was simply confirming that it does not / is a different issue altogether :)

That's what I wrote?
This is not Coreboot, it is a PureOS issue.

@nicole this isn't a coreboot issue. If you boot a Qubes 4.0.1 ISO (eg) and run memtest from there, it works perfectly fine.

Is there any workaround for this, any way to install PureOS on a UEFI system? I would like to try PureOS on my laptop but it seems I am stuck due to this issue.

@MrChromebox I am not sure if this issue relates to Coreboot. I see exactly this issue when e.g. booting from the OEM or live image and choose the memtest from the Grub menu.
And yes, I would also like to see this fixed since being able to run a memtest from a USB stick would be very helpful. I have not yet tested if this issue also applies to a PureOS installation.
(tested with latest OEM image 2019-07-14)

More detailed picture with messages on the 2nd attachment.

Silly me. It's already packaged. But it looks terrible in Plasma. It's a Gnome client.

Only if it does not conflict with Purism's philosophy.

yes, this is yet another area of this Mozilla product (unsurprisingly, really) linking to Mozxilla resources.

@jonas.smedegaard i know you have been working on this issue of references of Mozilla and Firefox in purebrowser.

Also see https://directory.fsf.org/wiki/Review:Chromium-REV-ID-1 or https://directory.fsf.org/wiki/Talk:Chromium (the first link might be moved to the last one). Iridium Browser suffers from the same issues (this is described in the references). Also as described there, none of the lists is exhaustive, as we/volunteers from FSD lack some contributors specific for this issue.

This didn't change anything, but I did finally get an image of my screen after entering my decryption password, there are some statements about failed loading of firmware before PureOS boots. The least benign-sounding is:
[ 1.402310] i915 0000:0:02.0: firmware: failed to load i915/kbl_dmc_ver1_04. bin (-2)
Which I take it has something to do with the kabylake graphics processor, but may be completely normal for all I know? There's also a statement about failed Bluetooth firmware which I assume is normal.

Awesome, can we close this now?

I have this snippet you pasted here at the bottom of my /etc/pulse/default.pa file. It came in via the regular update process on June 4th (I didn't add it manually.)

May I ask that you try commenting out

Hi, any advice on getting the splash screen back by editing my grub.cfg file? It's not a huge priority at this point, but I would feel better if I could resolve this.

Thanks for the followup. Feel free to post status updates here about the upstream progress :-)

Thanks, @rinigus !

I suggest to close this - looks like pyotherside made it to PureOS

Sorry for late reply - haven't received any notification regarding it by email.

@EchedeyLR Thanks for investigating. Please however report any concrete findings as separate issues.

I think there is still a similar problem with Chromium like https://tracker.pureos.net/T663 due to Google dependence/promotion.

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.

If I remember, Chromium is not packaged on Trisquel due to more problems but I am not sure.

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

See https://software.pureos.net/sw/linphone.desktop
(there is still a warning that the icon is upscaled, which could be fixed in the packaging)

This seems to be fixed now - sort of...