Hi all
I've just upgraded my PC and decided to upgrade to 64bit kubuntu and of course, digikam 0.10 (from svn). After the usual annoyances with pre-installed exiv2 packages I managed to compile it due to the detailed wiki instructions, however I still have problems running digikam... I had a very large database in digikam 0.9.5 and when starting 0.10, I get lots of errors like: Error: Directory SubImage1 with 29280 entries considered invalid; not read. And then the final situation in digikam is that it shows all directories, but no image files at all. Another problem, though not directly related to digikam is that in order to compile digikam, I need to uninstall gwenview and exiv2 (0.17) of the distribution packages and recompile gwenview from sources/svn, because I'm using a custom exiv2 lib. Any suggestions (esp, for the first problem!) tnx Simon _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Simon Oosthoek wrote:
> Hi all > > I've just upgraded my PC and decided to upgrade to 64bit kubuntu and of > course, digikam 0.10 (from svn). > > After the usual annoyances with pre-installed exiv2 packages I managed > to compile it due to the detailed wiki instructions, however I still > have problems running digikam... > > I had a very large database in digikam 0.9.5 and when starting 0.10, I > get lots of errors like: > Error: Directory SubImage1 with 29280 entries considered invalid; not read. > > And then the final situation in digikam is that it shows all > directories, but no image files at all. > > Another problem, though not directly related to digikam is that in order > to compile digikam, I need to uninstall gwenview and exiv2 (0.17) of the > distribution packages and recompile gwenview from sources/svn, because > I'm using a custom exiv2 lib. > > Any suggestions (esp, for the first problem!) > Hmm, after restarting digikam it somehow does seem to work now... But I guess the upgrade procedure might be a little rough on unsuspecting users... Cheers Simon _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Bugzilla from s.oosthoek@xs4all.nl
2009/1/26 Simon Oosthoek <[hidden email]> Hi all This is an internal Exiv2 warning. It's not digiKam directly... Gilles Caulier _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Bugzilla from s.oosthoek@xs4all.nl
Am Montag, 26. Januar 2009 20:52:25 schrieb Simon Oosthoek:
> Hmm, after restarting digikam it somehow does seem to work now... But I > guess the upgrade procedure might be a little rough on unsuspecting > users... I can confirm this. It's easy to reproduce. Quit digikam4, remove the database-file, start digikam4. It indexes the pictures but does nto show them. If you restart it again, it works. Sven _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
> > Hmm, after restarting digikam it somehow does seem to work now... But I > > guess the upgrade procedure might be a little rough on unsuspecting > > users... > > I can confirm this. It's easy to reproduce. Quit digikam4, remove the > database-file, start digikam4. It indexes the pictures but does nto show > them. If you restart it again, it works. Gilles, can you reproduce this? I cannot. Sven, when this happens for you, what is your kioslave output on the console (lines starting with kio_digikam... usually found in ~/.xsession-errors)? Marcel _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Please let's continue this here: http://bugs.kde.org/show_bug.cgi?id=181792 _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Free forum by Nabble | Edit this page |