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.

But the Live image and the Plasma image still need testing

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

Is this not something that can also be pushed to upstream g-i-s

This has been fixed in PureOS for some time now

This has been fixed in PureOS for some time now, but we'll still need an upstream solution. I'll likely push this change to Debian as well meanwhile, so Debian can benefit from the bugfix as well.

Tried to install Kodi on Byzantium this morning, here's what I got:

I don't currently have access to a monitor but that will be changing soon. If the issue returns with my new monitor (whichever I end up choosing) then I'll check the dmesg log and report back.

Is there any relevant dmesg output? Can you monitor the kernel ring buffer with dmesg -w?

In T298#15256, @jeremiah.foster wrote:

In this case;

For the last couples of weeks I have had my Librem hooked up to an external monitor (UP2516D) by HDMI and experience some odd screen flickering. Maybe “flickering” is the wrong word, what happens is that the screen blanks at random intervals for about a second once every few minutes. I have struggled to establish any pattern, my best current guess is that it is correlated with CPU load as it becomes much more frequent once the fan starts spinning. It should also be emphasised that the laptop screen never flickers, I have confirmed this by observing flickering on the external monitor while the laptop monitored remained stable when I mirrored the output. I have investigated this issue on and off for about a week now, with no success, thus I am reaching out to you.

Add recommended hardware for mobile devices: CPU, graphics and WiFi card for Librem 5 decreasing minimum RAM to 3 GB.

Works for me also as of a couple days ago.

I can't reproduce this. I just installed apt-listchanges in Byzantium

In T913#17039, @jeremiah.foster wrote:

@adaian What happens when you turn on the computer? What do you see? Can you write down any messages that the screen shows? The term 'brick' doesn't describe very much unfortunately. Do you have a USB device you can burn a live ISO to and boot from?

This bug was indeed fixed by me earlier this week :-)

@adaian What happens when you turn on the computer? What do you see? Can you write down any messages that the screen shows? The term 'brick' doesn't describe very much unfortunately. Do you have a USB device you can burn a live ISO to and boot from?

Hello everyone.
I have a Purism Librem 13 bricked version 3 laptop, I need you to help me with the initial bin file

I'm getting a "page not found" for the depcheck byzantium issue.

This appears to be fixed as I was able to re-install it tonight

I'm not sure what this means but I think it is related:

I tried switching to repo.puri.sm, apt update, and install apt-listchanges. I still get the same dependency error.

It looks like you're using the Sonic mirror.

We no longer are going to maintain Purebrowser given upstream lack of support.

Very strange. Are we using different repositories?

The issue is resolved on my side too. The version of libhandy is now correct.

Yes, not only on first boot where you made the initial setup also second boot and go on

Is this on reboot?

I can't reproduce;

I can't reproduce;

$ sudo apt install gnome-contacts

Which device is this @francois?

@jeremiah.foster If it is ok for you I would like to take a shot at this task as a weekend learning experience.

Found this issue because I had the same idea, it is a really cool app :D

I think this might also be the cause of this problem: https://tracker.pureos.net/T915

I just found out that the python3-apt package in Byzantium is not up to date and is at version 1.8.4, which is the same version as Debian stable, which is not compatible with python 3.8 : https://packages.debian.org/buster/python3-apt

@jeremiah.foster I get the same output from the same command.

My python version is;

0.0.11-1pureos1 can be removed from buzantium and we can switch to the Debian version. There's no downstream changes in there, it was just a rebuilt since the package wasn't in Debian at that time.

@jeremiah.foster I am still getting the same error after updating and upgrading.

Looks like a dup for T907

I did;

Considering that we phased out Purebrowser in Favor of Epiphany and Firefox-ESR and that the bug was closed in Debian.

After trying to install gnome-software again, I now get the following error :

Thanks for the update @alexngould

Switched my sources.list back to the mirrors.sonic.net repositories today, and now it seems to work without any errors.

Nitrokey app folked merged support for the Librem Key upstream yesterday: https://github.com/Nitrokey/libnitrokey/pull/163

@mak Considering that Purebrowser has been phased out in favor of Epiphany/Firefox-ESR can this ticket be closed?

I'm not sure - it looks like they do have a signed release file here: https://mirrors.sonic.net/pureos/repo/pureos/dists/byzantium/

That works. It must be a problem with mirrors.sonic.net.

You can try the main repos;

Thank you @mak ! I will retry in a few days then. Do you know how many days?

What do you mean with "breaks"? Does it crash? Is it not installable? In the former case, a backzrace or at least console output would be nice.

This should be fixed now, but the update will need a few days to migrate out of landing.

Exciting - we should test this in Byzantium and hopefully we can close this bug.

Debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928893 indicates that this has been fixed.

@jeremiah.foster Perhaps this might help:

I am sorry that did not help.

Thank you @Wayne, but I don't find a solution there or something that could help me.

You may want to check and track this post. It may be related to your issue.

they're already on it!

If you follow the upstream discussion you can see that they're already on it! :-)

ok, so we should contact the Litrokey app devs? To see if they merge that request?