IMA let Frenchy talk for a bit so you can see why software devels make horrid sys admins.

This is the type of stuff you encounter when running a system that has been patched all over the place in the past and decide it’s time to upgrade.

No, this is Ubuntu messing up something every other distro has sorted.

It’s one of the reason some people recommend doing a clean install, because they don’t know how to fix things when that happens

You can patch your system with never stuff, you can build yourself a frankendistro if you want to, just be prepared to clean up the mess when you upgrade.

Best solution might be to do a bit of cleaning up before upgrading so that things won’t break after.

Did that and the built in check even agreed that no problems were spotted.

From all the things you can patch on your system, using the Ubuntu Toolchain PPA is by far the most risky. Even installing a newer kernel won’t get you into any trouble.

Never used it until after the update.

There are many other alternatives to patching your daily system: dual booting, virtual machines, containers or even stuff like Flatpack and Snaps now. Keep in mind that if you want to run the latest software you have to run the latest OS as well.

You would leave an internet facing machine unpatched?

This, this right here is his malfunction.

Tis not a “daily system” it’s a production box that has to work the same today as it does 9 months from now.

Had to dpkg –force-all -i libstdc+‌+6_5.4.0-6ubuntu1~16‌.04.2_amd64.deb and libstdc+‌+6_5.4.0-6ubuntu1~16‌.04.2_i386.deb to get the little bugger to boot.

This was an adventure since the system could not enable networking.

Then ended up adding ppa:ubuntu-toolchain-r/test so I could run apt-get install -f

Had to install gcc-4.9 and remove gcc-4.8 to get the NVIDIA module to compile because ¯\_(ツ)_/¯

That said, it sorted the Warhammer online issue.

I’ve had so many bad experiences updating distros without a reinstall.