Dear Maintainer,

Digikam does not start either from menu or command line:

digikam: error while loading shared libraries: libOpenEXR-3_1.so.30: cannot
open shared object file: No such file or directory


This appears to be bug 1130756, marked as fixed 11 Apr 2026. I have just run an
apt upgrade, not fixed, then purged and reinstalled digikam, still not fixed.

Please run
	 dpkg --list|grep -i openexr
to see what openexr packages you have installed.

On my system:

$ dpkg --list|grep -i openexr
ii  libimath-3-2-30:amd64                                    3.2.2-2+b1
amd64        Utility libraries from ASF used by OpenEXR - runtime
ii  libopenexr-3-4-33:amd64                                  3.4.15+ds-1
amd64        runtime files for the OpenEXR image library
ii  libopenexr-doc                                           3.4.15+ds-1
all          documentation and examples for the OpenEXR image format
ii  openexr                                                  3.4.15+ds-1
amd64        command-line tools for the OpenEXR image format
ii  python3-imath:amd64                                      3.2.2-2+b1
amd64        Utility libraries from ASF used by OpenEXR - Python bindings

Yeah.  I'm going to have to find a way to depend on the openexr libs even
though digikam doesn't actually build against it.

There's something wrong here.  I have the same version of digikam and it links
with libOpenEXR-3_4.so.33  NOT ...3_1.so.30.

$ ldd /usr/bin/digikam |grep -i exr
        libOpenEXR-3_4.so.33 => /usr/lib/x86_64-linux-gnu/libOpenEXR-3_4.so.33
(0x00007fa65c0b7000)
        libOpenEXRCore-3_4.so.33 => /usr/lib/x86_64-linux-gnu/
libOpenEXRCore-3_4.so.33 (0x00007fa650b86000)
steve@riemann:~/Packages/digikam/salsa$

It seems the failure of digikam to run was due to the presence of
cheese, which was preventing some graphic upgrades from occurring,
including a dependency of digikam. Cheese was removed from unstable
around last November, but was itself still working. You live and learn.

Joe