[Bug 158989] New: digikam won't start: MakerTagInfo registry full

[krienke]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=158989         




------- Additional Comments From krienke uni-koblenz de  2008-05-28 09:51 -------
Am Mittwoch, 28. Mai 2008 08:50:44 schrieb krienke uni-koblenz de:
[bugs.kde.org quoted mail]

I just found another explanaition for the "MakerTagInfo registry full". I just
tried to start digikam from the souce directory. The installed version runs
fine. If I however try to start  

$ ./digikam-0.9.4-beta5/digikam/digikam/digikam
terminate called after throwing an instance of 'Exiv2::Error'
  what():  MakerTagInfo registry full
Aborted

So here I still get the this error allthogh the very same version of digikam
is already installed and runs. Strange.

Have anice day
Rainer
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=158989         




------- Additional Comments From ahuggel gmx net  2008-05-28 13:02 -------
Just curious, can you do

   $ ldd digikam

from eg, your home directory and

   $ ldd ./digikam-0.9.4-beta5/digikam/digikam/digikam

to see if they load the same exiv2 library?

-ahu.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[krienke]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=158989         




------- Additional Comments From krienke uni-koblenz de  2008-05-28 13:15 -------
Am Mittwoch, 28. Mai 2008 13:02:54 schrieb Andreas Huggel:
> ------- You are receiving this mail because: -------
> You are the assignee for the bug, or are watching the assignee.
>


$ ldd /opt/kde3/bin/digikam | grep exiv2
        libkexiv2.so.3 => /opt/kde3/lib/libkexiv2.so.3 (0xb73bd000)
        libexiv2.so.0 => /usr/lib/libexiv2.so.0 (0xb72c4000)

The digikam file in digikam-0.9.4-beta5/digikam/digikam is a bourne shell
script.   It says its a wrapper:

# digikam - temporary wrapper script for .libs/digikam
# ....

It finally calls digikam-0.9.4-beta5/digikam/digikam/.libs/lt-digikam

$ ldd digikam-0.9.4-beta5/digikam/digikam/.libs/lt-digikam | grep exiv2
        libkexiv2.so.3 => /opt/kde3/lib/libkexiv2.so.3 (0xb73dd000)
        libexiv2.so.2 => /usr/lib/libexiv2.so.2 (0xb7260000)
        libexiv2.so.0 => /usr/lib/libexiv2.so.0 (0xb595a000)

Rainer
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=158989         




------- Additional Comments From caulier.gilles gmail com  2008-05-28 13:25 -------
Andreas,

This is the problem :

   libexiv2.so.2 => /usr/lib/libexiv2.so.2 (0xb7260000)
   libexiv2.so.0 => /usr/lib/libexiv2.so.0 (0xb595a000)

How it's possible ?

Gilles
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=158989         




------- Additional Comments From ahuggel gmx net  2008-05-28 13:42 -------
Yup. I suspect libkexiv2 loads one version and digikam is directly linked to another version.

-ahu.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=158989         




------- Additional Comments From caulier.gilles gmail com  2008-05-28 13:46 -------
Andreas,

But digiKam is not linked with Exiv2 directly (there is nothing in this way from the Makefile.am). Only libkexiv2 must do.

It's a packaging problem ?

Gilles
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=158989         




------- Additional Comments From ahuggel gmx net  2008-05-28 15:08 -------
I think we can find out what is linked to libexiv2 by running ldd on each of the libraries digikam is linked to. Those that don't show up anywhere are directly linked to digikam. A bit tedious since there are many but I don't have a better idea.

Rainer, since you have the interesting case with different versions, could you please do that? Start with libkexiv2 and then go through all the other libraries that digikam is linked to to see if any of them is linked to libexiv2. If not it must be digikam itself.

I don't think it's a packaging problem, Rainer compiled this version of digikam himself.

-ahu.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[krienke]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=158989         




------- Additional Comments From krienke uni-koblenz de  2008-05-29 15:08 -------
Am Mittwoch, 28. Mai 2008 15:08:43 schrieb Andreas Huggel:

> Rainer, since you have the interesting case with different versions, could
> you please do that? Start with libkexiv2 and then go through all the other
> libraries that digikam is linked to to see if any of them is linked to
> libexiv2. If not it must be digikam itself.


Ok, what I did was to run this quite simple loop in the beta5 source tree:

for i in `ldd digikam/digikam/.libs/lt-digikam | awk '{print $3}'`; do
        ldd $i|grep exiv2 && echo $i;
done

it does a ldd on all shared libs lt-digikam depends on and then does a ldd on
each of these libs and greps all occurences of exiv2 and then echos the lib
they were found in if there were any.

The result is:

        libkexiv2.so.3 => /opt/kde3/lib/libkexiv2.so.3 (0xb73d0000)
        libexiv2.so.2 => /usr/lib/libexiv2.so.2 (0xb7252000)
        libexiv2.so.0 => /usr/lib/libexiv2.so.0 (0xb5974000)
/home/krienke/tmp/digikam/digikam-0.9.4-beta5/digikam/digikam/.libs/libdigikam.so.0
        libexiv2.so.0 => /usr/lib/libexiv2.so.0 (0xb7ea6000)
/opt/kde3/lib/libkexiv2.so.3

So both libdigikam.so.0 links to exiv2 as well as libkexiv2.so.3

Is this what you wanted to see?

Rainer
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=158989         




------- Additional Comments From ahuggel gmx net  2008-05-29 18:31 -------
Rainer,
Yes, thanks, good job!

Gilles,
The public libkexiv2 API "leaks" Exiv2 objects in at least 2 places:
   static void printExiv2ExceptionError(const QString& msg, Exiv2::Error& e);
   static QString convertCommentValue(const Exiv2::Exifdatum &comment);

(I didn't check if it also throws Exiv2::Error out of the library)

If these methods are used in digikam, then digikam must link to Exiv2. And if it links a different version than libkexiv2 then I'm not sure what will happen.
Is it possible that you use Exiv2 objects only in the implementation of libkexiv2 and not in its API? (I suggest nowhere in kexiv2.h at all, not even in the private sections of the classes there) This includes that libkexiv2 shouldn't throw Exiv2 objects for digikam to catch.

Having said that, I still don't really understand this bug. The error that we get is not caused by any of these calls directly, it happens during the initialization of Exiv2, before any client call is made. I've opened a bug for Exiv2 to replace this initialization code with something more straightforward (http://dev.robotbattle.com/mantis/view.php?id=550), maybe that will help too.

-ahu.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=158989         




------- Additional Comments From caulier.gilles gmail com  2008-05-29 19:37 -------
> static void printExiv2ExceptionError(const QString& msg, Exiv2::Error& e);

==> Not used in digiKam

> static QString convertCommentValue(const Exiv2::Exifdatum &comment);

==> Not used in digiKam

> I didn't check if it also throws Exiv2::Error out of the library

No isn't it....

> Is it possible that you use Exiv2 objects only in the implementation of >libkexiv2 and not in its API? (I suggest nowhere in kexiv2.h at all, not even >in the private sections of the classes there) This includes that libkexiv2 >shouldn't throw Exiv2 objects for digikam to catch.

Yes, i will do it.

Gilles
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=158989         




------- Additional Comments From caulier.gilles gmail com  2008-05-30 08:20 -------
SVN commit 814354 by cgilles:

libkexiv2 from trunk : reduce memory fingerprint and API simplifications: remove unecessary private methods to access on internal STD C++ and Exiv2 C++ components
CCBUGS: 158989


 M  +4 -5      CMakeLists.txt  
 M  +15 -15    kexiv2.cpp  
 M  +4 -35     kexiv2.h  
 M  +5 -5      kexiv2comments.cpp  
 M  +0 -45     kexiv2private.cpp  
 M  +4 -2      kexiv2private.h  


WebSVN link: http://websvn.kde.org/?view=rev&revision=814354
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=158989         




------- Additional Comments From caulier.gilles gmail com  2008-05-30 08:22 -------
SVN commit 814357 by cgilles:

libkexiv2 from trunk : No need to redeclare internal Exiv2 components here.
CCBUGS: 158989


 M  +0 -3      kexiv2.h  


WebSVN link: http://websvn.kde.org/?view=rev&revision=814357
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=158989         




------- Additional Comments From caulier.gilles gmail com  2008-05-30 09:09 -------
SVN commit 814363 by cgilles:

libkexiv2 from trunk : improve binary compatibility again. do not make visible all private methods from kexiv2.h
Now, all Exiv2 components are unknow from host application which use libkexiv2
CCBUGS: 158989


 M  +2 -8      kexiv2.cpp  
 M  +242 -152  kexiv2.h  
 M  +1 -92     kexiv2comments.cpp  
 M  +30 -30    kexiv2exif.cpp  
 M  +8 -8      kexiv2gps.cpp  
 M  +11 -11    kexiv2image.cpp  
 M  +19 -19    kexiv2iptc.cpp  
 M  +106 -0    kexiv2private.h  
 M  +19 -19    kexiv2xmp.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=814363
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=158989         
caulier.gilles gmail com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Metadata                    |libkexiv2
            Product|digikam                     |kipiplugins
            Summary|digikam won't start:        |digikam won't start:
                   |MakerTagInfo registry full  |MakerTagInfo registry full
                   |                            |(libkexiv2 relevant)
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=158989         
caulier.gilles gmail com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|digikam-devel kde org       |kde-imaging kde org



------- Additional Comments From caulier.gilles gmail com  2008-05-30 09:11 -------
Andreas,

I have reassigned this file to libkexiv2 component in bugzilla

Gilles
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel