Going back, I did notice something that might be interesting. On the first reboot after the update, vt.handoff=7 is missing.

This was not fixed in the above due to https://bugs.debian.org/898511 ("git repository missing latest 0.9.3-2 upload")

Fixed in https://code.puri.sm/pureos/plymouth/commit/c6c31458c6e485c559c1757efbd6187a132f4a60 (uploaded as plymouth_0.9.3-1pureos1_amd64.changes)

wellton reminded me....The 5/9 update was the upgrade to linux-image-4.16.0-1 pkg. I failed to explicitly mention that.

Same problem here. My kernel is 4.16.8-gnu

On boot I am seeing

Yes, the package manager. There was no output from terminal when launched. I needed to determine another package version (Synergy) that was available, but if Synaptic is going to be dropped this ticket could be closed.

This could indeed be related to stripped firmware as the firmware we strip out (the intel nonfree firmware) indeed contain power management parts.

Coreboot splash screen (with Purism logo) provides that info. Are you using latest coreboot? Note that it is indeed fast in showing that but putting some higher timeout would annoy users who want fast boot :-/

Synaptic the package manager? Please attach the output from terminal once you launch it.
Also note that synaptic does not have (at least last time I checked) Wayland support nor do I know any effort to port it so it will most likely drop from archive in time.

Broken again. Please stop breaking dependencies! This should be trivial to automatically test.

Thanks for the suggestion.

This was addressed in Debian today with the release of kodi 2:17.6+dfsg1-2.
Consequently should likely reach PureOS in ~1 month.

This is not really a duplicate of T255, but rather an issue concretely actionable since it is isolated to a specific package, whereas T255 is a meta-issue tracking the broader concept.

The issue remains. I'm informed of this "unable to install" issue everytime I open Software.

If you go to the hamburger menu and then add ons, you'll see the attached picture. In the past this was directed to a FSF add on page. After loading up the most recent build on a test machine without Firefox installed, the normal Firefox add-ons page is shown within PureBrowser. So the original issue remains despite my being incorrect as to the cause.