LinuxQuestions.org
Visit Jeremy's Blog.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 01-04-2023, 08:58 AM   #1
ccoffee
Member
 
Registered: Mar 2003
Location: Lake City, South Carolina
Distribution: Slackware 15 and current
Posts: 60

Rep: Reputation: 7
Slackware64_15.0 Digikam Error


Running Slackware64 15.0 and can't get Digikam 7.5.0 to run and it had run previously. Not sure what happened but now when I go to /usr/bin and run Digikam
from the command line I get the following:

bash-5.1# ./digikam
./digikam: /lib64/libc.so.6: version `GLIBC_2.34' not found (required by
/usr/lib64/libopencv_core.so.405)
./digikam: /lib64/libc.so.6: version `GLIBC_2.34' not found (required by
/usr/lib64/libomp.so.1)

The standard glibc_2.33 is installed as listed in pkgtool.

Have reinstalled digikam-7.5.0 but that has not helped.

Have done multiple searches and keep coming up with libs, etc that are supposedly
needed but those were not installed previously and when it was running.

Any ideas on what I can do to get this repaired and running?

I have searched for Digikam dependencies but I can't find anything on the Web.
 
Old 01-04-2023, 10:13 AM   #2
marav
LQ Sage
 
Registered: Sep 2018
Location: Gironde
Distribution: Slackware
Posts: 5,409

Rep: Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145
Where did you get Digikam 7.5 ?
 
Old 01-04-2023, 10:49 AM   #3
ccoffee
Member
 
Registered: Mar 2003
Location: Lake City, South Carolina
Distribution: Slackware 15 and current
Posts: 60

Original Poster
Rep: Reputation: 7
Out of my Slackware64_15.0/slackware64/kde packages and can also be found
at the Packages.slackware.com/Slackware64_15.0/slackware64/kde.

CC
 
Old 01-04-2023, 11:31 AM   #4
marav
LQ Sage
 
Registered: Sep 2018
Location: Gironde
Distribution: Slackware
Posts: 5,409

Rep: Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145
No trouble on my VM 15.0

It looks like you grab the one from current
Might that be possible ?
 
Old 01-04-2023, 11:37 AM   #5
drumz
Member
 
Registered: Apr 2005
Location: Oklahoma, USA
Distribution: Slackware
Posts: 907

Rep: Reputation: 697Reputation: 697Reputation: 697Reputation: 697Reputation: 697Reputation: 697
Digikam works for me.

Do you have the wrong versions of opencv and/or llvm installed? Can you run these same commands and paste the output?

Code:
$ objdump -T /usr/lib64/libopencv_core.so.405 | grep GLIBC_2.3
0000000000000000      DF *UND*  0000000000000000  GLIBC_2.3   realpath
0000000000000000      DF *UND*  0000000000000000  GLIBC_2.33  stat
0000000000000000      DO *UND*  0000000000000000  GLIBC_2.32  __libc_single_threaded
0000000000000000      DF *UND*  0000000000000000  GLIBC_2.30  pthread_cond_clockwait
0000000000000000      DF *UND*  0000000000000000  GLIBC_2.3.4 sched_getaffinity
Code:
$ objdump -T /usr/lib64/libomp.so | grep GLIBC_2.3
0000000000000000      DF *UND*  0000000000000000  GLIBC_2.32  pthread_getattr_np
0000000000000000      DF *UND*  0000000000000000  GLIBC_2.3.2 pthread_cond_init
0000000000000000      DF *UND*  0000000000000000  GLIBC_2.3.2 pthread_cond_destroy
0000000000000000      DF *UND*  0000000000000000  GLIBC_2.3.2 __register_atfork
0000000000000000      DF *UND*  0000000000000000  GLIBC_2.3.2 pthread_cond_signal
0000000000000000      DF *UND*  0000000000000000  GLIBC_2.3.2 pthread_cond_wait
0000000000000000      DF *UND*  0000000000000000  GLIBC_2.3   __tls_get_addr
Code:
$ grep libopencv_core.so /var/lib/pkgtools/packages/*
/var/lib/pkgtools/packages/opencv-4.5.5-x86_64-1:usr/lib64/libopencv_core.so.4.5.5
Code:
$ grep libomp.so /var/lib/pkgtools/packages/*
/var/lib/pkgtools/packages/llvm-13.0.0-x86_64-2:usr/lib64/libomp.so
/var/lib/pkgtools/packages/llvm-compat32-13.0.0-x86_64-2compat32:usr/lib/libomp.so
 
Old 01-04-2023, 11:57 AM   #6
ccoffee
Member
 
Registered: Mar 2003
Location: Lake City, South Carolina
Distribution: Slackware 15 and current
Posts: 60

Original Poster
Rep: Reputation: 7
Ok here are the outputs you asked about:

bash-5.1# objdump -T /usr/lib64/libopencv_core.so.405 | grep GLIBC_2.3
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.34 pthread_cond_clockwait
0000000000000000 w DF *UND* 0000000000000000 GLIBC_2.34 __pthread_key_create
0000000000000000 DO *UND* 0000000000000000 GLIBC_2.32 __libc_single_threaded
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.33 stat
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.34 dlsym
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.34 dlopen
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.34 dlclose
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.3.4 sched_getaffinity
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.3.4 __memset_chk
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.3.4 __vsnprintf_chk
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.34 pthread_key_create
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.34 pthread_key_delete
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.34 pthread_getspecific
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.34 pthread_setspecific
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.34 dladdr
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.3 realpath
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.34 dlerror
0000000000000000 w DF *UND* 0000000000000000 GLIBC_2.34 pthread_mutexattr_init
0000000000000000 w DF *UND* 0000000000000000 GLIBC_2.34 pthread_mutexattr_settype
0000000000000000 w DF *UND* 0000000000000000 GLIBC_2.34 pthread_mutexattr_destroy
bash-5.1#
bash-5.1# objdump -T /usr/lib64/libomp.so | grep GLIBC_2.3
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.34 dlopen
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.34 dlsym
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.34 dlclose
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.3.4 __vsnprintf_chk
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.3.4 __vfprintf_chk
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.34 shm_open
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.34 shm_unlink
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.34 pthread_attr_setstacksize
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.34 pthread_create
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.34 pthread_join
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.34 pthread_mutexattr_init
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.3.2 pthread_cond_init
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.3.2 pthread_cond_destroy
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.34 pthread_mutex_trylock
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.34 pthread_setspecific
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.34 pthread_getspecific
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.34 pthread_key_create
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.34 pthread_mutexattr_destroy
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.34 pthread_key_delete
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.34 sem_wait
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.34 sem_init
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.3.2 pthread_cond_wait
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.3.2 pthread_cond_signal
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.34 sem_post
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.32 pthread_getattr_np
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.34 pthread_attr_getstack
0000000000000000 w DF *UND* 0000000000000000 GLIBC_2.34 pthread_mutexattr_settype
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.34 dlerror
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.3.4 __strncpy_chk
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.34 dladdr
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.3.2 __register_atfork
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.3 __tls_get_addr
bash-5.1#

bash-5.1# grep libopencv_core.so /var/lib/pkgtools/packages/*
/var/lib/pkgtools/packages/lib64opencv_core4.5-4.5.5-3-omv4050.x86_64:usr/lib64/libopencv_core.so.4.5.5
/var/lib/pkgtools/packages/opencv-4.5.5-x86_64-1:usr/lib64/libopencv_core.so.4.5.5
bash-5.1#

bash-5.1# grep libomp.so /var/lib/pkgtools/packages/*
/var/lib/pkgtools/packages/lib64omp-15.0.4-1-omv22090.x86_64:usr/lib64/libomp.so.1.15.0.4
/var/lib/pkgtools/packages/llvm-13.0.0-x86_64-2:usr/lib64/libomp.so
 
Old 01-04-2023, 12:01 PM   #7
marav
LQ Sage
 
Registered: Sep 2018
Location: Gironde
Distribution: Slackware
Posts: 5,409

Rep: Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145
Why you have glibc 2.34 in Slackware 15.0, since the version must be 2.33 ?
 
Old 01-04-2023, 12:26 PM   #8
drumz
Member
 
Registered: Apr 2005
Location: Oklahoma, USA
Distribution: Slackware
Posts: 907

Rep: Reputation: 697Reputation: 697Reputation: 697Reputation: 697Reputation: 697Reputation: 697
You have 2 packages installed that are not stock Slackware packages and have overwritten files:

lib64opencv_core4.5-4.5.5-3-omv4050.x86_64
lib64omp-15.0.4-1-omv22090.x86_64

Based on the names I'd say these are somehow converted Debian or Red Hat packages to Slackware format. Unless they are packages that live in /opt this is almost always a really bad idea. (Note how some SBo packages are Debian packages repackaged into Slackware packages - but this is always done so as not to interfere with stock Slackware packages.) These non-Slackware packages have been compiled against a newer glibc than is present in Slackware, which is the problem.

You need to remove these packages and then reinstall the Slackware packages (upgradepkg --reinstall) opencv-4.5.5-x86_64-1 and llvm-13.0.0-x86_64-2.
 
2 members found this post helpful.
Old 01-04-2023, 01:01 PM   #9
marav
LQ Sage
 
Registered: Sep 2018
Location: Gironde
Distribution: Slackware
Posts: 5,409

Rep: Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145
https://www.youtube.com/watch?v=wifOU9xN19I
 
Old 01-04-2023, 01:22 PM   #10
ccoffee
Member
 
Registered: Mar 2003
Location: Lake City, South Carolina
Distribution: Slackware 15 and current
Posts: 60

Original Poster
Rep: Reputation: 7
marav - Love the title to the utube video link - Aint that the absolute truth.....
I really do not know where the glibc-2.34 is coming from but I guess I have some corrupted files. I do not remember ever trying to load
glibc-2.34 and according to my pkgtool list, I have glibc-2.33 installed and that is what I show in my slackware64_15.0/slackware64/l/
files. I am going to try and upgradepkg --reinstall --install-new glibc-2.33.

drumz
Yes will try those two files next with upgradepkg...

Thanks everyone...
 
1 members found this post helpful.
Old 01-04-2023, 01:40 PM   #11
drumz
Member
 
Registered: Apr 2005
Location: Oklahoma, USA
Distribution: Slackware
Posts: 907

Rep: Reputation: 697Reputation: 697Reputation: 697Reputation: 697Reputation: 697Reputation: 697
You don't have glibc-2.34 installed. Those two rogue packages have been linked against glibc-2.34 (or newer) when they were compiled. That's why they have those symbol names in them. Your system is (rightfully) complaining that it can't find the glibc-2.34 symbols - they aren't installed.

This is why you shouldn't blindly install binary packages from other distros. I imagine you have several other packages installed that conflict with stock Slackware packages.
 
1 members found this post helpful.
Old 01-04-2023, 01:42 PM   #12
drumz
Member
 
Registered: Apr 2005
Location: Oklahoma, USA
Distribution: Slackware
Posts: 907

Rep: Reputation: 697Reputation: 697Reputation: 697Reputation: 697Reputation: 697Reputation: 697
To be clear: no, you don't have corrupted files. You simply have packages installed that shouldn't have been installed. They overwrote files belonging to stock Slackware packages. You need to remove the rogue packages and then reinstall any Slackware packages that had files overwritten.
 
Old 01-04-2023, 01:46 PM   #13
marav
LQ Sage
 
Registered: Sep 2018
Location: Gironde
Distribution: Slackware
Posts: 5,409

Rep: Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145
Is "omv" related to OpenMediaVault ?
 
Old 01-04-2023, 02:12 PM   #14
ccoffee
Member
 
Registered: Mar 2003
Location: Lake City, South Carolina
Distribution: Slackware 15 and current
Posts: 60

Original Poster
Rep: Reputation: 7
This is now the output of the drumz had directed earlier and it looks better:

bash-5.1# objdump -T /usr/lib64/libopencv_core.so.405 | grep GLIBC_2.3
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.3 realpath
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.33 stat
0000000000000000 DO *UND* 0000000000000000 GLIBC_2.32 __libc_single_threaded
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.30 pthread_cond_clockwait
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.3.4 sched_getaffinity
bash-5.1#

bash-5.1# objdump -T /usr/lib64/libomp.so | grep GLIBC_2.3
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.32 pthread_getattr_np
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.3.2 pthread_cond_init
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.3.2 pthread_cond_destroy
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.3.2 __register_atfork
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.3.2 pthread_cond_signal
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.3.2 pthread_cond_wait
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.3 __tls_get_addr
bash-5.1#

bash-5.1# grep libopencv_core.so /var/lib/pkgtools/packages/*
/var/lib/pkgtools/packages/opencv-4.5.5-x86_64-1:usr/lib64/libopencv_core.so.4.5.5

and

bash-5.1# grep libomp.so /var/lib/pkgtools/packages/*
/var/lib/pkgtools/packages/llvm-13.0.0-x86_64-2:usr/lib64/libomp.so

I will have to search and see what rouge files are on here and then remove, however it appears that
digikam is now working as once again I can open the "heic" files I need to work with.

Thanks to all, this is really a great place to get resolution.

cc
 
3 members found this post helpful.
  


Reply

Tags
digikam, slackware 15.0



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Slackware64_15, Virtualbox 6.1.34: All Windows 10 guests BSOD slacker_et Slackware 29 10-14-2022 01:51 PM
tigervnc: starting a server on slackware64_15.0 via rc.local gives me an empty plasma desktop _peter Slackware 5 04-09-2022 12:53 PM
[SOLVED] Internet security and slackware64_15.0 slacnovitz Slackware 23 03-01-2022 10:43 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 01:36 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration