[Digikam-devel] [Bug 158989] digikam won't start: MakerTagInfo registry full

Andreas Huggel ahuggel at gmx.net
Tue May 27 17:01:25 BST 2008

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

------- Additional Comments From ahuggel gmx net  2008-05-27 18:01 -------
> When I install additionally libexiv2-0.15-8.2 then digikam will start
> however then I get the "MakerTagInfo registry full" error. 

So does it load 0.15? Since digikam (and I assume libkexiv2) was compiled with exiv2 0.16, that would be the case I mentioned in comment #9. Digikam shouldn't even start in this case! (see below)

> When I [...] only install libexiv2-0.15-8.2 as well as
> libexiv2-devel-0.15-8.2 and then recompile digikam everything works fine
> and no "MakerTagInfo registry full"  error is shown. 

Compile and run the same versions of everything: works fine. That's fine.

The questions are
1) When you installed libexiv2-2-0.16-17, you say "when I start digikam it then tells me it cannot find libexiv2.so.0". Why not? And why is it not looking for libexiv2.so.2 (see below)??

2) When digikam was compiled with v0.16 and run with 0.15, why does it load the library in the first place? 

Here is a small illustration done using the tarballs from the exiv2 distribution:

When I install exiv2 0.16 in /usr/local/lib, it installs
 libexiv2.so.2 -> libexiv2.so.2.1.0
 libexiv2.so -> libexiv2.so.2.1.0

When I compile a small application (exifprint from the samples directory), I get
$ ldd exifprint
	libexiv2.so.2 => /usr/local/lib/libexiv2.so.2 (0xb7de6000)
        (and several others)

Now, I uninstall exiv2 0.16 and install 0.15 instead. In /usr/local/lib, it installs
 libexiv2.so.0 -> libexiv2.so.0.1.0
 libexiv2.so -> libexiv2.so.0.1.0

When I now try to run the application compiled with 0.16, I get

$ exiv2-0.16/samples/exifprint
exiv2-0.16/samples/exifprint: error while loading shared libraries: libexiv2.so.2: cannot open shared object file: No such file or directory

It doesn't even start! So I don't understand how it is possible to run digikam with exiv2 0.15 when it was compiled with exiv2 0.16

Do you have any other versions of exiv2 installed on your system?

Or is it a problem with the exiv2 package of your distribution? Try the same thing that you did with the exiv2 distribution from www.exiv2.org to find out. I would expect similar results as those described above.


More information about the Digikam-devel mailing list