[SOLVED] digikam not launching on current

camorri · 03-16-2024, 09:56 AM

As the title says, digikam fails to launch on one of my current systems.

On my desktop, digikam fails with

Code:

digikam
digikam: error while loading shared libraries: libunibreak.so.5: cannot open shared object file: No such file or directory

Well, of course, libunibreak is now at

Code:

libunibreak-6.1-x86_64-1

Here is the weird part. It works fine on my latop, with libunibreak at 6.1.

On both systems digikam has package

Code:

digikam-8.3.0-x86_64-1.txz

installed. After launching digikam on my laptop. the splash screen show version 8.4.0, and so does the about screen.

Any one else have issues with digikam?

I did reinstall digikam on the failing system, it still fails.

chrisretusn · 03-16-2024, 10:01 AM

No issues here. Try reinstalling libunibreak.

EDit: Add.

Code:

$ digikam --version
digikam 8.4.0

Code:

[ Status    ] [ Repository  ] [ Package                   ]
  installed     slackware64     libunibreak-6.1-x86_64-1 

[ Status    ] [ Repository  ] [ Package                 ]
  installed     slackware64     digikam-8.3.0-x86_64-1

camorri · 03-16-2024, 10:04 AM

After a reinstall of libunibreak;

Quote:

digikam
digikam: error while loading shared libraries: libunibreak.so.5: cannot open shared object file: No such file or directory

camorri · 03-16-2024, 10:33 AM

I re-installed libunibreak to version 5.1, and digikam works on my desktop. I does report digikam as 8.4.0.

Petri Kaukasoina · 03-16-2024, 10:35 AM

Is this up to date: libass-0.17.1-x86_64-2

camorri · 03-16-2024, 11:10 AM

No, i'm seeing:

Quote:

ls -l /var/lib/pkgtools/packages | grep libass
-rw-r--r-- 1 root root 900 Feb 15 13:55 libass-0.17.1-x86_64-1

I will update it, put libunibreak back on 6.1 and report back.

camorri · 03-16-2024, 01:06 PM

I updated libass to:

Quote:

ls -l /var/lib/pkgtools/packages | grep libass
-rw-r--r-- 1 root root 902 Mar 16 13:57 libass-0.17.1-x86_64-2

and updated libunibreak to

Quote:

ls -l /var/lib/pkgtools/packages | grep libunibreak
-rw-r--r-- 1 root root 1074 Mar 16 13:58 libunibreak-6.1-x86_64-1

and digikam is now working normally.

I'm at a loss to explain why libass was not updated. I update my current systems daily ( when there are updated ) and for unknown reasons libass was not updated with everything else.

Thank-you for those who helped.

FWIW, Digikam is still reported as 8.4.0.

Petri Kaukasoina · 03-16-2024, 04:41 PM

Quote:

Originally Posted by camorri

Code:

digikam: error while loading shared libraries: libunibreak.so.5: cannot open shared object file: No such file or directory

The reason for this kind of error is not always obvious. Digikam does not link directly to libunibreak. Instead, digikam links, for example, to libdigikamgui and libdigikamcore which link to libavfilter which links to libass which links to libunibreak.

Looking for 'not found' in the output of 'ldd /usr/bin/digikam' does not help, as it prints all direct library dependencies mixed with dependencies of dependencies, and so on.

The script below, 'lddtree', lists the direct library dependencies and their dependencies separately. In case of 'lddtree /usr/bin/digikam', looking for 'not found' would have pointed to libass.

Code:

#!/bin/sh
# lddtree
# List direct library dependencies and their dependencies and so on.
# Something like ldd, but ldd does not separate direct dependencies.
# pk 2024-03-16

function check {
  echo NEEDED by "$1":
  objdump -p "$1"|grep NEEDED|sed 's/ *NEEDED *//;s/$/ /;s/\./\\\./g' > $NEEDED
  ldd "$1"|grep -f $NEEDED|sed 's/ (.*//'
  echo
}

[ $# -ne 1 ] && echo 'Give a binary or a library.' && exit 1
objdump -p "$1" > /dev/null || exit 1
NEEDED=$(mktemp)
trap 'rm $NEEDED' EXIT
check "$1"
ldd "$1"|grep -v -e linux-vdso.so.1 -e statically -e 'not found' |\
sed 's/.*=> //;s/ (.*//' |\
while read line; do
  check $line
done

camorri · 03-16-2024, 04:49 PM

Thank-you for the explanation! and the script to check this type of error.