Going Linux podcast planned to review MX, but...

[Stevo]

https://archive.org/details/glp366

starting at 0:53. What normal updates from our normal repo in a virtual machine would have prevented MX from booting? I'm not aware of any. I hope they didn't add Ubuntu PPAs...

[richb]

https://archive.org/details/glp366

starting at 0:53. What normal updates from our normal repo in a virtual machine would have prevented MX from booting? I'm not aware of any. I hope they didn't add Ubuntu PPAs...

Have 18.2 in VBox for a system with only updates and minimal app additions for testing purposes as opposed to my highly changed SSD install. No regular updates have caused any problems.

EDIT: Oh he then installed on hardware. No clue.

[Richard]

Originally installed the MX-18rc1 on the T430 in sig. Currently updated to MX 18.2, with the following added or upgraded & up-to-date apps:

From MX repo: apt-offline audacious audacity axel
cdrdao fdupes fsarchiver geeqie gpart gpm grive gtkorphan hplip indicator-keylock irqbalance meld mirage mtp-tools normallize-audio poedit qpdf redshift shotwell speedcrunch sqlitebrowser streamtuner2 thermald timeshift vim virtualbox vorbis* xsane

From developer's sites:
Cherrytree, DoubleCommander-beta, Dropbox, Libreoffice-fresh, OmegaT

Via the MX-Package-Installer:
Liquorix-5.0.0-8.1 (a definite improvement on the T430 over the stock kernel, temp-wise), MasterPdfEd,

And I use Xfce compositing & Thermald,

tl;dr
Strangely enough, since April 2014, with all sorts of changes, that I have inflicted on my daily ride,

I've never had MX fail to boot after updating with:
$ sudo apt update && sudo apt dist-upgrade
or
Synaptic.