[SOLVED] slackware libraries messed up with every kernel upgrade?
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.
slackware libraries messed up with every kernel upgrade?
Hello folks,
i have been getting unusual missing-library-responses when launching certain packages.
A few months ago, it started with
- kernel 5.14 - loss of vga/graphic card drivers and aegisub stopped launching;
- kernel 5.15 - vga drivers issue fixed;
- kernel 5.16 - loss of kmail and pointer/mouse. Skypeforlinux won't launch unless i pass the "chmod 1777 /dev/shm" command to fiddle with RAM memory;
- kernel 5.17 (current) - the pointer issue fixed however, several packages won't launch because of, apparently, missing libraries (and skype still need the tweak to launch).
Just a few examples, although it seems that the list gets bigger with each kernel upgrade:
does anyone have any ideas why this is happening? or, is it just my box?
Thanks in advance for any suggestions
p.s.: I recall that Ponce confirmed that 'aegisub' issue was probably my system as not "pure slackware" and therefore other packages may have caused conflicts, etc... and he was right because I installed it on a "virgin-slackware" laptop and it launched however, after a few slackpkg update/upgrades (and no other packages installed so still virgin) it stopped launching with another missing-library error, below:
Code:
bash-5.1$ aegisub
aegisub: error while loading shared libraries: libboost_fylesystem.so.1.75.0: cannot open shared object file: No such file or directory
bash-5.1$
Are you mixing up packages from SLackware 15.0 and -current perhaps?
Kmail should normally not complain about libKF5Mime unless you mix up packages or do an incomplete upgrade. Check your configuration, make sure you use the repository that matches with your installed Slackware.
Darktable, aegisub are packages that you yourself have compiled a while ago. When Slackware-current upgrades its libraries and some of them increase their ABI version, your self-compiled binaries fail until you compile them again. That's an easy and fast fix.
As for appimages - Slackware does not support them so you're basically on your own if they give you issues.
I can't see any way that a kernel upgrade could affect precompiled libraries. In theory you can run any kernel with any set of mutually consistent libraries. Updating the kernel headers might affect packages that are locally compiled afterwards because some source code might directly reference a kernel header.
Updating the kernel headers might affect packages that are locally compiled afterwards because some source code might directly reference a kernel header.
Even then, this is extremely unlikely. I still have the 4.4 kernel headers installed on my 14.2 system, but I'm running a 5.10 kernel.
Are you mixing up packages from SLackware 15.0 and -current perhaps?
Kmail should normally not complain about libKF5Mime unless you mix up packages or do an incomplete upgrade. Check your configuration, make sure you use the repository that matches with your installed Slackware.
No, i am not using slack15 packages. The slackpkg configuration file is correct and download the 'slackware current' packages. I also tried to
Code:
slackpkg update && slackpkg installpkg kmail
to have the original libraries and it still won't launch
Quote:
Darktable, aegisub are packages that you yourself have compiled a while ago. When Slackware-current upgrades its libraries and some of them increase their ABI version, your self-compiled binaries fail until you compile them again. That's an easy and fast fix.
I did try to compile darktable again, from ponce's repository and then manually (building my own latest darktable package) and this is what it returned, from Ponce-s repo
Code:
/usr/bin/ld: /usr/lib64/libGraphicsMagick.so: undefined reference to `jas_matrix_create'
collect2: error: ld returned 1 exit status
make[2]: *** [bin/CMakeFiles/darktable.dir/build.make:164: bin/darktable] Error 1
make[2]: Leaving directory '/tmp/SBo/darktable-3.4.0/build'
make[1]: *** [CMakeFiles/Makefile2:1728: bin/CMakeFiles/darktable.dir/all] Error 2
make[1]: Leaving directory '/tmp/SBo/darktable-3.4.0/build'
make: *** [Makefile:156: all] Error 2
darktable:
Would you like to continue processing the rest of the
queue or would you like to abort? If this failed
package is a dependency of another package in the queue
then it may not make sense to continue.
(Y)es to continue, (N)o to abort, (R)etry the build?:
and then from a manual build with the latest darktable 3.8.1 (this was almost successful because it configured ok, then it built 100% and it stopped when creating the /tmp/file.tgz ) (i used the source from their webpage and the SlackBuild from Ponce's repo editing the darktable.SlackBuild file and adjusting the package version from 3.4.0 to 3.8.1)
Code:
-- Installing: /tmp/SBo/package-darktable/usr/share/darktable/tools/common.sh
-- Installing: /tmp/SBo/package-darktable/usr/share/darktable/tools/purge_from_cache.sh
-- Installing: /tmp/SBo/package-darktable/usr/share/darktable/tools/purge_non_existing_images.sh
-- Installing: /tmp/SBo/package-darktable/usr/share/darktable/tools/purge_unused_tags.sh
cp: cannot stat 'doc/ChangeLog': No such file or directory
cp: cannot stat 'doc/TODO': No such file or directory
bash-5.1#
Quote:
As for appimages - Slackware does not support them so you're basically on your own if they give you issues.
the thing is, appimages were running ok before; i guess i will have to wait for their upgrade then
Quote:
hazel
I can't see any way that a kernel upgrade could affect precompiled libraries. In theory you can run any kernel with any set of mutually consistent libraries. Updating the kernel headers might affect packages that are locally compiled afterwards because some source code might directly reference a kernel header.
I guess that what I was trying to say is "upgrading the whole kernel-set" (source, header and firmware)
Quote:
bassmadrigal
Even then, this is extremely unlikely. I still have the 4.4 kernel headers installed on my 14.2 system, but I'm running a 5.10 kernel.
a step too much for my technical reach, aka: I don't really understand what that means but, thank you for your input
-- Installing: /tmp/SBo/package-darktable/usr/share/darktable/tools/common.sh
-- Installing: /tmp/SBo/package-darktable/usr/share/darktable/tools/purge_from_cache.sh
-- Installing: /tmp/SBo/package-darktable/usr/share/darktable/tools/purge_non_existing_images.sh
-- Installing: /tmp/SBo/package-darktable/usr/share/darktable/tools/purge_unused_tags.sh
cp: cannot stat 'doc/ChangeLog': No such file or directory
cp: cannot stat 'doc/TODO': No such file or directory
bash-5.1#
I can't speak to the other issues you have in this thread, but all thats happening here is that there is no doc/ChangeLog or doc/TODO file in the source tarball for 3.8.1 Perhaps this used to exist for 3.4.0 but got removed? The best way forward would be to extract the tarball yourself and check whats in the doc/ directory. Maybe naming is changed or the files are actually removed? Then update your slackbuild to use the proper locations, or remove copying those if they no longer exist (you'll find the cp command somewhere after 'make install').
I can't speak to the other issues you have in this thread, but all thats happening here is that there is no doc/ChangeLog or doc/TODO file in the source tarball for 3.8.1 Perhaps this used to exist for 3.4.0 but got removed? The best way forward would be to extract the tarball yourself and check whats in the doc/ directory. Maybe naming is changed or the files are actually removed? Then update your slackbuild to use the proper locations, or remove copying those if they no longer exist (you'll find the cp command somewhere after 'make install').
Thank you so much. I learned something new. I did as you suggested and then edited the ./slackbuild file and the build completed successfully creating the new package.
However, when i install it and try to launch it:
Code:
bash-5.1$ /usr/bin/darktable
/usr/bin/darktable: error while loading shared libraries: libjasper.so.4: cannot open shared object file: No such file or directory
bash-5.1$
I reluctantly decided to do a 'slackpkg clean-system' and it seems to get somewhere.
So, now, i have a 'clean slackware profile' and nothing else installed except the slackware64 packages; I launch kmail and I get this
Code:
bash-5.1$ kmail
Connection to speech-dispatcher failed
Connection to speech-dispatcher failed
Connection to speech-dispatcher failed
Connection to speech-dispatcher failed
Connection to speech-dispatcher failed
Connection to speech-dispatcher failed
Connection to speech-dispatcher failed
Connection to speech-dispatcher failed
Connection to speech-dispatcher failed
[2557:2590:0426/131204.328537:ERROR:platform_shared_memory_region_posix.cc(250)] Creating shared memory in /dev/shm/.org.chromium.Chromium.ch8kEM failed: Permission denied (13)
[2557:2590:0426/131204.328609:ERROR:platform_shared_memory_region_posix.cc(253)] Unable to access(W_OK|X_OK) /dev/shm: Permission denied (13)
[2557:2590:0426/131204.328625:FATAL:platform_shared_memory_region_posix.cc(255)] This is frequently caused by incorrect permissions on /dev/shm. Try 'sudo chmod 1777 /dev/shm' to fix.
Trace/breakpoint trap
so I run
Code:
bash-5.1$ su
Password:
bash-5.1# chmod 1777 /dev/shm
and it launches ok.
But how is this now happening? (which means that at every system reboot I have to fiddle with the memory)
thank you, this solved the issue and kmail starts as usual
I guess, I made the assumptions of libraries being messed up by updates/upgrades when, perhaps, it's just that the previously compiled 3rd party packages became outdated with each system upgrade.
I will mark this thread as 'Solved' and, I thank again the kind members for the insights and the developers for the time they devote to keep slackware the best Linux distro out there.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
