Version: 1.0.0 (using 4.3.5 (KDE 4.3.5), Mandriva Linux release 2010.0 (Official) for i586) Compiler: gcc OS: Linux (i686) release 2.6.31.12-desktop-1mnb since the begining i test digikam 1.0.0 with Mandriva 2010.0 when you go to metadata settings in digikam settings then you have only the EXIF settings panel see https://qa.mandriva.com/show_bug.cgi?id=56078
I'm not sure to understand. Can you take a shot ? Also, please test with Exiv2 0.19 and digiKam 1.1.0 Gilles Caulier
Created attachment 40765 [details] metadatasetting.png
Mandriva does not supply digikam 1.1.0 for 2010.0 then i installed digikam 1.1.0, kipi-plugins, libkexiv2_7 from MIB i didn't find any exiv2 0.19 then i stay with 0.18.2 i tried to launch digikam 1.1.0 with no success ******************************************************************** [roubach@localhost ~]$ digikam digikam: symbol lookup error: digikam: undefined symbol: _ZN7Digikam17CollectionScanner11recordHintsERK5QListINS_14ItemChangeHintEE [roubach@localhost ~]$ ********************************************************************
i installed libexiv2_6 0.19 from mandriva 2010.1 (cooker) with no more success same launching error
The 1.1.0 start error is the lidigikam.so binary compatibility broken. Package problem or a wrong install on your computer. Do you have properlly uninstalled 1.1.0 before I recommend to install also libkexiv2 from trunk. From your screenshot, i cannot see any problem... Where you you see a dysfunction ? Gilles Caulier
Gilles, we have five more tabs there, Nepomuk, Exif viewer, etc. These tabs will be hidden if you are running digikam compiled with an older libkexiv2. Gilles knows better than me what KEXIV2_VERSION >= 0x010000 means. The other problems you report here are due to broken, incomplete packages are leftover older library versions.
To comment#4: Which is expected not to work, installing a cooker package on a stable release usually doesn't work. And since digikam in 2010.0 wasn't compiled against this version of exiv, then it's definitely not gonna make any difference installing exiv2 package from cooker...
(In reply to comment #7) > To comment#4: > Which is expected not to work, installing a cooker package on a stable release > usually doesn't work. And since digikam in 2010.0 wasn't compiled against this > version of exiv, then it's definitely not gonna make any difference installing > exiv2 package from cooker... you don't understand Mandriva 2010.0 + digikam 1.0.0 does not work with Mandriva 2010.0 exiv2 and kexiv2 it is necessary to update exiv2 adn kexiv2 the test with digikam 1.1.0 is just to narrow the pb
(In reply to comment #6) > Gilles, we have five more tabs there, Nepomuk, Exif viewer, etc. > > These tabs will be hidden if you are running digikam compiled with an older > libkexiv2. Gilles knows better than me what KEXIV2_VERSION >= 0x010000 means. > The other problems you report here are due to broken, incomplete packages are > leftover older library versions. i compiled and install exiv2 0.19 and kexiv2 1.0.0 but pb still there thus i assume kipi-plugins and digikam must be compiled against these new version of exiv2 and kexiv2 ?
>i assume kipi-plugins and digikam must be compiled against these new version of >exiv2 and kexiv2 ? Yes of course. Look in Help/Components Info to be sure to use right version of shared libs after recompilation... Gilles Caulier
kexiv2 depends on kde 4.4 digikam is installed with kde 4.3 with mandriva 2010.0 thus there is no mean to fix the pb i think digikam is too much dependent from kde it's easy to update exiftool indenpendently from kde. i do this using "geotag" software it would be better to use exiftool
Definitivly no. Exiftool is perl script, digiKam is C++. A good puzzle no ? you can compile KEXiv2 (and all other libs from kdegraphics that digiKam use) with old KDE4 version. I do it myself, as developper and maintainer of these libs. Don't forget : i use also mandriva distro (2010.0 with KDE 4.2.3) Gilles