[SOLVED] X won't start after update error while loading shared libraries libicui18n.so.65 on current
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
There is no "multilib" version of icu4c (the package containing libicui18n). There are only 2 official versions of that package, 64bit and 32bit. Alien Bob has a "compat32" version, which is the 32bit version modified to work on a multilib system without overwriting the 64bit version.
On a 64bit version of Slackware, you need the 64bit version of icuic installed, and if you have multilib, you should probably install compat32 version, but that's in addition to the 64bit version.
The only "multilib" packages that actually replace stock Slackware packages are gcc-* and glibc-*. Everything else is compat32 packages that are 32bit packages modified to coexist with the original 64bit packages.
Long story short, install the 64bit icu4c package and your problem should be resolved.
Whoops I was not paying attention the 64 bit icu4c package is installed. It is the .68 version not sure why X wants the .65 version? Any suggestions on where the problem could be?
Whoops I was not paying attention the 64 bit icu4c package is installed. It is the .68 version not sure why X wants the .65 version? Any suggestions on where the problem could be?
First thing I'd do is obviously check and make sure the mirror you're using is up-to-date and that slackpkg is updated against that mirror. Next, check your slackpkg blacklist and then check to see if you have all the updates with slackpkg. If you use slackpkg+ with multilib, make sure your priorities are correct.
You could also use slackpkg search to look for various things like the following to see if they're showing in need up upgrades or missing:
It is Plasma all other window managers work. I suspect there was a problem with the last update there were some checksum errors, was not sure how to handle them? I will try to download and reinstall Plasma?
The error is that libicui18n.so.65 no such lib or does not exist that is because libicui18n.so.68 is there and something in Plasma wants the old version for some reason.
Last edited by TarFile; 12-15-2020 at 07:35 PM.
Reason: more information
The error is that libicui18n.so.65 no such lib or does not exist that is because libicui18n.so.68 is there and something in Plasma wants the old version for some reason.
It seems you have a really old package installed that references the .65 version. icu4c was upgraded to the .68 version in October, but that was from the .67 version (which was upgraded in May from the .65 version). The .65 version was used from October 2019 until May 2020.
This is a test box to test new software releases and new software.
About the time-frame bassmadrigal mentioned I installed KDE5 or Plasma to test some stuff that required it. At the time it was not part of current so I used stuff from Alien Bob including QT5. It did not get updated so it was an old version.
I really should keep a log when I do something like that
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.