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.
Folks, having pulled some hairs out over not having Alien Bob's EXCELLENT port of Plasma 5 to Slackware64-current working since the Big upgrade Friday, I've been blessed by working with some folks on Eric's blog to discover the cause of the mischief and fix it on my own server. In /lib64 there remains the OLD udev libudev.so.0.13.1 and several symbolic links to it. DELETE that old troublemaker, and point your symlinks to eudev's /lib64/libudev.so.1.6.3, and your Plasma 5 deesktop with ALL the trimmings will come back in good working order.
In /lib64 there remains the OLD udev libudev.so.0.13.1 and several symbolic links to it. DELETE that old troublemaker (...)
The older libudev.so.0.13.1 is not there by mistake, it was put in aaa_elflibs for the following reason:
Quote:
Originally Posted by volkerdi
libudev.so.0 was added to aaa_elflibs late last month as a fallback for third party packages that might still link with that after the switch to eudev and libudev.so.1.
All software in -current that still linked to it was already fixed a few days ago:
Quote:
Originally Posted by ChangeLog
Sat Nov 21 19:18:17 UTC 2015
Some more recompiles and a couple upgrades. Most of these were needed to
fix packages on 32-bit that were needlessly linking the old libudev.so.0.
Thanks to bormant for spotting these. After rebuilding them, they no longer
link to libudev at all...
I don't use Plasma 5, but perhaps it should point to the newer library instead?
If it's a package linked to libudev.so.0, then simply rebuild the package and check after building if it's relinked against libudev.so.1 before using it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.