These images should now be(come) default. Thanks everyone for testing!
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Aug 27 2020
Aug 26 2020
Aug 20 2020
Aug 18 2020
Aug 16 2020
Aug 14 2020
$ cat /etc/os-release
ID=pureos
NAME=PureOS
PRETTY_NAME=PureOS
GNU+Linux is the highly hackable thing by its nature. The access to the corresponding sources is an expected behavior.
Is this in Amber, or Byzantium? (/etc/os-release should have this info.)
I think that this might be an "okay" situation as it is. The point is that adding deb-src repos is more of a power user thing, no?
Will do. Thanks for keeping it such good shape Jonas. :-)
Aug 11 2020
I've tried reducing the QHD refresh rate from 60Hz to 50hz and this has been quite stable so far. Fingers crossed...
I've got my new monitor (a Dell U2719DC) and I've been able to reproduce the blanking issue reliably. I think your correspondent is correct that it's related to performance.
Aug 9 2020
Aug 8 2020
Ran GNOME OEM on my LMv1 and GNOME Live on L15v4:
This fixes it for upgrading Ubuntu as well from 18.04 to 20.04. Thank you so much.
Aug 7 2020
I am also having this issue after trying the dd and Gnome Disks method. Both the January version of PureOS as well as the version from last night are not detected by the BIOS. On the other hand, I can boot live Debian and Trisquel just fine.
Aug 6 2020
Nice! If nobody vetoes this image until next Monday/Tuesday, I will send this image to the factory and marketing people - we really have to update the default image, and especially that OEM username issue is causing very frequent support issues, so it has to go (not to mention the huge amount of security fixes that newer PureOS releases contain and that just aren't there yet with the current images).
I'll be able to test this next saturday
Aug 5 2020
Aug 4 2020
The image has been updated to incorporate the latest security fixed for a bunch of vulnerabilities in GRUB (less relevant for us if /boot is verified anyway, but still good to have, especially for custom installations).
This should have been resolved with the latest util-linux upload.
Aug 3 2020
At some point the intent is to make this nicer-looking and better integrated, but until that point is there, we'll have this page :-)
They were signed with an expired key. refreshging that key from a keyserver fixed this issue.
Thanks!
Aug 2 2020
Jul 30 2020
https://software.pureos.net/package/bin/byzantium/libglib2.0-0 currently says "This package is currently not installable!"
Jul 29 2020
And a follow up. When the disk has partitions on it, the installer won't allow you to select 'Erase Disk'. I have to install gparted to delete the partitions before the 'Erase Disk' option is available. Don't know if this is a bug or on purpose.
@mak Tested 2020-07-22 OEM on my Librem Mini. It installs and boots just fine!
Jul 23 2020
@all but especially @richard.kolla : Can you please test the 2020-07-22 image? There were now functional changes, only minor bugfixes from Debian and security fixes (so I expect everything to still work as before).
Jul 22 2020
Jul 20 2020
In T919#17068, @richard.kolla wrote:[...]
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.
Jul 19 2020
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
Jul 18 2020
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.
Jul 17 2020
Tried to install Kodi on Byzantium this morning, here's what I got:
Jul 14 2020
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.