So... What did you try? Is there still an issue at all?
Not root filesystem could mean the OEM installation didn't happen. When the OEM installer asks you whether it should automatically determine the fastest disk, what did you answer?

"no root filesystem is defined" on an a BIWIN 128 gb SSD sata 2.5"

i made a mistake.

Patches have been cleaned up and pushed to gerrit.

"no root filesystem is defined" on an Order with two drives: Nvme m.2 1 tb SSD and Samsung 850 evo 1 tb sata.

Done by @MrChromebox

Fixed by @MrChromebox via FSP2 SATA speed limit option.

Done by @MrChromebox and to be merged upstream soon.

Done, and tested.

While true that smtube _can_ use tonvid.com, Debian distribution of smtube does not.

bogusly forked fromT61: It is tonvid.com (not smtube itslef) that tracks users.

its the usb(s) that are having the issues loading purism OEM install. Problem Resolved with new USBs.

@ah_purism From the logs Zlatan sent me it looks like this is indeed the case. The SquashFS filesystem on the source disk is damaged. This can happen because of a defective download, or because your USB stick is at the end of its life.
Can you download the ISO image again, verify its checksum and then try it maybe with one other USB stick, to rule out defective hardware?

I tried installing using the same OEM installation. i get this error. I will send through my whatsapp account. It might be the download may be corrupted?

upload failure

press back or escape button and you should have an option to access the shell/logs

how would i check the access logs

@mak @kakaroto can we test this somehow? Also @ah_purism can you attach images as well and check if you have access to logs?

Should i wait for a new coreboot/oem install or should i use the older version that i know would work?

On the 15 inch Purism Laptops. Have not tried 13 inch.

Current status:

I dput'ed last night a fork of Debian kodi, stripped of the kodi-repository-kodi binary package.

for the record:

While we will for now remove Kodi (as it was in our default installation to showcase basically the power of Free software) because it is blocked from entering Debian testing - we will re-introduce this package with all fixes around services.

Installed this and finding it super useful. I can't remember the default settings but Indicator style: Both, Notifications: Off is visible but unobtrusive. I'm not sure if everyday users would prefer "Notifications: On" (more noticeable).

Ok. Thanks for the explanation.

Ignore: I misunderstood how this rolling release of PureOS should _not_ auto-remove what gets removed from Debian testing.

I know about this, fixing it is already on my todo list.

I don't understand BOINC well enough to say how exactly the distributed code gets fed into the system, only (believe that I) understand that it does happen and that we cannot ensure that code fed into the system is freely licensed.

@jonas.smedegaard I can not block binary packages, it's either all or nothing. You will need to edit the package in PureOS, removing the problematic pieces.
Only syncing a few binary packages leads to an inconsistent archive with big headaches for QA, and if we later rebuild all packages from scratch becomes completely impossible.
So, adding a PureOS delta is the way to go here.

Closing this one, in case you experience a similar issue again, please file a new bug.

This has been blacklisted for ages now :-)

This has been resolved in https://github.com/lkorigin/laniakea/commit/5b5745da84fdf55e80f1829626daf01543380d38
The list of blacklisted packages is now visible at http://master.pureos.net/synchrotron/blacklist

I am currently using Debian 9.1 (Stretch) on a Libreboot x200, and while I still have problems with the Mullvad appliation, the connection is stable when I use OpenVPN: only disconnecting every once in a while. Presently, It's been going continuously since this morning (9am), without any issues.

Now with GNOME Night Mode, I think we can close this bug.

Same issue for me and I have another VPN provider as ezs777 mentioned above.

@mak can you block (not src:kodi but) the binary package kodi-repository-kodi from entering PureOS?

Debian kodi package re-entered unstable today, which means it will re-enter likely re-enter PureOS 10 days from now.

Debian kodi package re-entered unstable today, which means it will likely re-enter PureOS 10 days from now.

Kodi was removed from Debian testing some time ago due to FTBFS with GCC7.

Pardon my silly question, but as the latest release of Firefox ESR is version 52.4, could we take the opportunity to leap to that instead of being stuck at the 1.5-years-old 45 series, and lock ourselves into version 52 for the foreseeable future? (I would tend to think we should not jump to regular Firefox 57+ for a while, because the forceful migration to webextensions might cause us untold misery)

Purebrowser is currently out of date as rebuilding the latest esr results in extremely strange rendering artifacts such as completely missing icons and lines, etc. until I mouseover:

I've managed a way out : running a KaliLinux Live on USb, I could access to my hard drive and decrypt it without a problem with the password.

To solve another issue, I had to reinstall the all system.
https://tracker.pureos.net/T163

Thanks. All good now.

@mak There's new version of kpmcore, perhaps it will solve this issue?

Check your sources, solve https://tracker.pureos.net/T203 first and then update, it will be okay.

Check your /etc/apt/sources.list file, it should contain only the following line:

AMO example: https://addons.mozilla.org/en-US/firefox/addon/umatrix/