NikonPreview?
Locked
 
|
Do these errors:
Error: Directory NikonPreview with 2020 entries considered invalid; not read. Error: Directory NikonPreview with 2020 entries considered invalid; not read. Error: Directory Panasonic with 3500 entries considered invalid; not read. indicate a problem with my libkexiv2 library? I'm running beta2 but I also got them from v0.10.0. I initially thought I had a seriously corrupt hard drive but a search indicates that this error message cropped up in March on the digikam mailing list. Is there any further comment on the problem? I assume it means that the XMP information has not been written correctly. It occurred when I tried to sync metadata with database. I had only edited two images with v0.10 before upgrading to beta2 so most of the files I have do not have XMP information in them, just IPTC keywords written by v0.9.x Tim _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
This is not libkexiv2 messages, but Exiv2 library.
Try with to use last Exiv2 0.18.2... Do not mix old Exiv2 in your computer, and check which Exiv2 is used in digiKam by Help/components Info menu. Note : updating Exiv2, you need to recompile libkexiv2. if you use more recent libkexiv2 code, digiKam and co need to be recompiled too. Gilles Caulier 2009/7/16 Tim Jenness <[hidden email]>: > Do these errors: > > Error: Directory NikonPreview with 2020 entries considered invalid; not > read. > Error: Directory NikonPreview with 2020 entries considered invalid; not > read. > Error: Directory Panasonic with 3500 entries considered invalid; not > read. > > indicate a problem with my libkexiv2 library? I'm running beta2 but I also > got them from v0.10.0. I initially thought I had a seriously corrupt hard > drive but a search indicates that this error message cropped up in March on > the digikam mailing list. Is there any further comment on the problem? I > assume it means that the XMP information has not been written correctly. It > occurred when I tried to sync metadata with database. I had only edited two > images with v0.10 before upgrading to beta2 so most of the files I have do > not have XMP information in them, just IPTC keywords written by v0.9.x > > Tim > > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users > > Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
On Thu, Jul 16, 2009 at 3:03 AM, Gilles Caulier<[hidden email]> wrote:
> This is not libkexiv2 messages, but Exiv2 library. > > Try with to use last Exiv2 0.18.2... Do not mix old Exiv2 in your > computer, and check which Exiv2 is used in digiKam by Help/components > Info menu. > > Note : updating Exiv2, you need to recompile libkexiv2. if you use > more recent libkexiv2 code, digiKam and co need to be recompiled too. > > Gilles Caulier > > 2009/7/16 Tim Jenness <[hidden email]>: >> Do these errors: >> >> Error: Directory NikonPreview with 2020 entries considered invalid; not >> read. >> Error: Directory NikonPreview with 2020 entries considered invalid; not >> read. >> Error: Directory Panasonic with 3500 entries considered invalid; not >> read. >> >> indicate a problem with my libkexiv2 library? I'm running beta2 but I also >> got them from v0.10.0. I initially thought I had a seriously corrupt hard >> drive but a search indicates that this error message cropped up in March on >> the digikam mailing list. Is there any further comment on the problem? I >> assume it means that the XMP information has not been written correctly. It >> occurred when I tried to sync metadata with database. I had only edited two >> images with v0.10 before upgrading to beta2 so most of the files I have do >> not have XMP information in them, just IPTC keywords written by v0.9.x >> >> Tim >> >> _______________________________________________ >> Digikam-users mailing list >> [hidden email] >> https://mail.kde.org/mailman/listinfo/digikam-users >> >> > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users > So if we build exiv2-0.18.2, we also need to rebuild kdegraphics and digikam afterwards? Anything else? sean _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
2009/7/16 sean darcy <[hidden email]>:
> On Thu, Jul 16, 2009 at 3:03 AM, Gilles Caulier<[hidden email]> wrote: >> This is not libkexiv2 messages, but Exiv2 library. >> >> Try with to use last Exiv2 0.18.2... Do not mix old Exiv2 in your >> computer, and check which Exiv2 is used in digiKam by Help/components >> Info menu. >> >> Note : updating Exiv2, you need to recompile libkexiv2. if you use >> more recent libkexiv2 code, digiKam and co need to be recompiled too. >> >> Gilles Caulier >> >> 2009/7/16 Tim Jenness <[hidden email]>: >>> Do these errors: >>> >>> Error: Directory NikonPreview with 2020 entries considered invalid; not >>> read. >>> Error: Directory NikonPreview with 2020 entries considered invalid; not >>> read. >>> Error: Directory Panasonic with 3500 entries considered invalid; not >>> read. >>> >>> indicate a problem with my libkexiv2 library? I'm running beta2 but I also >>> got them from v0.10.0. I initially thought I had a seriously corrupt hard >>> drive but a search indicates that this error message cropped up in March on >>> the digikam mailing list. Is there any further comment on the problem? I >>> assume it means that the XMP information has not been written correctly. It >>> occurred when I tried to sync metadata with database. I had only edited two >>> images with v0.10 before upgrading to beta2 so most of the files I have do >>> not have XMP information in them, just IPTC keywords written by v0.9.x >>> >>> Tim >>> >>> _______________________________________________ >>> Digikam-users mailing list >>> [hidden email] >>> https://mail.kde.org/mailman/listinfo/digikam-users >>> >>> >> _______________________________________________ >> Digikam-users mailing list >> [hidden email] >> https://mail.kde.org/mailman/listinfo/digikam-users >> > > So if we build exiv2-0.18.2, we also need to rebuild kdegraphics and > digikam afterwards? Yes. Anything else? kipi-plugins. That all.. Gilles > > sean > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users > _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
On Thu, Jul 16, 2009 at 9:51 AM, Gilles Caulier<[hidden email]> wrote:
> 2009/7/16 sean darcy <[hidden email]>: >> On Thu, Jul 16, 2009 at 3:03 AM, Gilles Caulier<[hidden email]> wrote: >>> This is not libkexiv2 messages, but Exiv2 library. >>> >>> Try with to use last Exiv2 0.18.2... Do not mix old Exiv2 in your >>> computer, and check which Exiv2 is used in digiKam by Help/components >>> Info menu. >>> >>> Note : updating Exiv2, you need to recompile libkexiv2. if you use >>> more recent libkexiv2 code, digiKam and co need to be recompiled too. >>> >>> Gilles Caulier >>> >>> 2009/7/16 Tim Jenness <[hidden email]>: >>>> Do these errors: >>>> >>>> Error: Directory NikonPreview with 2020 entries considered invalid; not >>>> read. >>>> Error: Directory NikonPreview with 2020 entries considered invalid; not >>>> read. >>>> Error: Directory Panasonic with 3500 entries considered invalid; not >>>> read. >>>> >>>> indicate a problem with my libkexiv2 library? I'm running beta2 but I also >>>> got them from v0.10.0. I initially thought I had a seriously corrupt hard >>>> drive but a search indicates that this error message cropped up in March on >>>> the digikam mailing list. Is there any further comment on the problem? I >>>> assume it means that the XMP information has not been written correctly. It >>>> occurred when I tried to sync metadata with database. I had only edited two >>>> images with v0.10 before upgrading to beta2 so most of the files I have do >>>> not have XMP information in them, just IPTC keywords written by v0.9.x >>>> >>>> Tim >>>> >>>> _______________________________________________ >>>> Digikam-users mailing list >>>> [hidden email] >>>> https://mail.kde.org/mailman/listinfo/digikam-users >>>> >>>> >>> _______________________________________________ >>> Digikam-users mailing list >>> [hidden email] >>> https://mail.kde.org/mailman/listinfo/digikam-users >>> >> >> So if we build exiv2-0.18.2, we also need to rebuild kdegraphics and >> digikam afterwards? > > Yes. > > Anything else? > > kipi-plugins. That all.. > > Gilles > >> >> sean >> _______________________________________________ >> Digikam-users mailing list >> [hidden email] >> https://mail.kde.org/mailman/listinfo/digikam-users >> > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users > OK. Sadly Fedora is still at exiv2-0.18.1. So any updates of kdegraphics will need to be rebuilt manually, if I'm alert enough to notice. sean _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
«
Return to digikam-users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |