Article 6P161 Odd behavior regarding GLIBC

Odd behavior regarding GLIBC

by
asarangan
from LinuxQuestions.org on (#6P161)
I did a fresh install from Slackware64-15.0. Everything ran fine. Then I switched to the -current tree and ran slackpkg update; slackpkg install-new. Now everything hangs with the error message GLIBC_2.34 not found (required by lib/sbin/libcrypto.so.1.1).... Assuming that some of the new packages in the -current tree messed things up, I removed all the new packages with removepkg, leaving only the original ones behind. But after rebooting, I keep getting the same GLIBC error. In other words, removing all the packages installed since the fresh install seem not to have fixed the GLIBC error. I can easily reinstall everything from sratch and get things up and running again, but I am trying to understand the underlying cause.
External Content
Source RSS or Atom Feed
Feed Location https://feeds.feedburner.com/linuxquestions/latest
Feed Title LinuxQuestions.org
Feed Link https://www.linuxquestions.org/questions/
Reply 0 comments