Some users reported that they cannot boot after latest updates.
Reopened, because it has happened again. From a user:
today when turn on my Librem 13 it showed 30 updates to install. I gave permission to "restart and Install" the picture attached is what appears now when I turn on my laptop. I can access in safe mode...
Waiting for further info from the user.
I believe this is an isolated issue which was fixed, and is surfacing for users who didn't update for a long time (it happens for people who update via GNOME Software Center, AFAIK update via apt doesn't trigger the bug).
That's … odd. They should be calling the exact same thing. Can you provide the background etc. for your rationale?
Can you provide the background etc. for your rationale?
Well, the user managed to boot into rescue mode, from there they issued sudo apt update && sudo apt full-upgrade and got the following:
282 packages can be updated to see run 'apt list' upgradable E: dpkg was interrupted, you must manually run 'sudo dpkg -- configure -a' to correct the problem.
After they run sudo dpkg -- configure -a and right after that sudo apt update && sudo apt full-upgrade, the system started normally after restart.
Something happened while updating via GNOME Software Center to cause the interruption. This hasn't happened to users who update via apt (at least I didn't get any reports).
I did experience the same kernel panic as described above with brand new laptop at several occasion:
- When rebooting after setting up PureOS on a Librem 13 v2, out of the box
- When rebooting after upgrade to latest updates (kernel4.18) via Software Center
- When rebooting after setting up PureOS following fresh install
- When rebooting after upgrade to latest updates (kernel4.18) via apt with sudo apt update && sudo apt remove libavcodec-extra57 && sudo apt upgrade
At every occasion I just had to force shutdown and switch it back on. No need for any other action.
I have removed the 128 GB Intel SATA SSD and replaced it with a 500 GB Samsung 970 Evo NVMe M.2.
I did install PureOS from scratch and did not encounter any kernel panic.
Issue related to Intel SATA SSD?