Hangs on find new items
Locked
 
|
Hi All,
Trying out Plasma5 on Kubuntu 15.04. I have installed digiKam 4.12.0 on KDE 4.14.8. When I try to run it, it hangs everytime while "Finding new items". It hangs at 27% which I am guessing is when it hits a file it doesn't like. Starting it from terminal, it spits out a ton of digikam(18121)/KEXIV2: Cannot find Xmp key 'Xmp.acdsee.categories' into image using Exiv2 (Error # 35 : No namespace info available for XMP prefix `acdsee' before it dies. dpkg -s digikam yields Version: 4:4.12.0-vivid~ppa3 dpkg -s exiv2 yields Version: 0.25-vivid~ppa1 I had tried the default version before trying Philip's ppa. I had the same results. Any suggestions? Thanks, Mike _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
Your error message " Cannot find Xmp key 'Xmp.acdsee.categories' into image /Philipusing Exiv2" indicates that you don't use my package of libkexiv2-11 from my PPA. My package have updated libkexiv2 that you should use. Check which version of the package you are using. If there is any problem with it been hold back or something like that please report back to me so it can be fixed if it's on my PPAs end and not just your system. On Tue, Aug 11, 2015 at 12:19 AM, Michael Harnden <[hidden email]> wrote: Hi All, _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
On Tuesday, August 11, 2015 02:51:37 AM Philip Johnsson wrote:
> Your error message " Cannot find Xmp key 'Xmp.acdsee.categories' into image > using Exiv2" indicates that you don't use my package of libkexiv2-11 from > my PPA*.* My package have updated libkexiv2 that you should use. Check > which version of the package you are using. If there is any problem with it > been hold back or something like that please report back to me so it can be > fixed if it's on my PPAs end and not just your system. > > /Philip > > > On Tue, Aug 11, 2015 at 12:19 AM, Michael Harnden <[hidden email]> > > wrote: > > Hi All, > > Trying out Plasma5 on Kubuntu 15.04. I have installed digiKam 4.12.0 on > > KDE > > 4.14.8. When I try to run it, it hangs everytime while "Finding new > > items". It > > hangs at 27% which I am guessing is when it hits a file it doesn't like. > > > > Starting it from terminal, it spits out a ton of > > digikam(18121)/KEXIV2: Cannot find Xmp key 'Xmp.acdsee.categories' into > > image > > using Exiv2 (Error # 35 : No namespace info available for XMP prefix > > `acdsee' > > > > before it dies. > > > > dpkg -s digikam yields Version: 4:4.12.0-vivid~ppa3 > > dpkg -s exiv2 yields Version: 0.25-vivid~ppa1 > > > > I had tried the default version before trying Philip's ppa. I had the same > > results. > > > > Any suggestions? > > Thanks, > > Mike > > _______________________________________________ > > Digikam-users mailing list > > [hidden email] > > https://mail.kde.org/mailman/listinfo/digikam-users Thank you Philip, that got rid of the errors. I had to force a downgrade as the main repo has a newer version Source: libkexiv2 Version: 4:15.04.1-0ubuntu1~ubuntu15.04~ppa1 Unfortunately my scan still dies at 27%. The only thing it complains about is one file very early in the scan. /home/michael/Pictures/635csi.xcf: The file contains data of an unknown image type Mike _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
OK, then I should update that version of my package as it should override the official kde package until they are up with the digikam release of them so there is no need to downgrade for infact newer software. /Philip On Aug 11, 2015 3:32 AM, "Michael Harnden" <[hidden email]> wrote:
On Tuesday, August 11, 2015 02:51:37 AM Philip Johnsson wrote: _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
In reply to this post by Michael Harnden
> Unfortunately my scan still dies at 27%. The only thing it complains about
> is one file very early in the scan. > /home/michael/Pictures/635csi.xcf: The file contains data of an unknown > image type > > Mike > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users Does anyone know if there are any options I can use when starting from the commandline to see why it is hanging at 27%? _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
Marie-Noëlle 2015-08-12 0:02 GMT+02:00 Michael Harnden <[hidden email]>: > Unfortunately my scan still dies at 27%. The only thing it complains about --     et aussi sur Facebook : _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
Hi, guess I'm also having the sorts of problem many Kubuntu/LinuxMint
users are experiencing. Already upgraded my sqlite3/libsqlite3, also tested adding folders one by one to the collection; all was normal up to ~60 Gb of images or ~35 Mb of digikam4.db. Then the scan dies. Did a backtrace, see below*. But one thing intriques me; the digikamrc sometimes has incorrect encoding ISO-8859-15, and sometimes it iss UTF-8. Weird. To get rid of any doubt I even replaced the notsoveryold HDD containing the collection with a brand new HDD, but the symptoms persist. My system is LinuxMint 17.2 64bit, but I started to see this phenomenon before upgrading from 17.1 Hope there will be a solution to this anytime soon ;-) Best regards, Sveinn í Felli Þann mið 12.ágú 2015 05:59, skrifaði Marie-Noëlle Augendre: > See this page: https://www.digikam.org/contrib > > Marie-Noëlle > > 2015-08-12 0:02 GMT+02:00 Michael Harnden <[hidden email]>: > >>> Unfortunately my scan still dies at 27%. The only thing it complains >> about >>> is one file very early in the scan. >>> /home/michael/Pictures/635csi.xcf: The file contains data of an unknown >>> image type >>> >>> Mike >> >> Does anyone know if there are any options I can use when starting from the >> commandline to see why it is hanging at 27%? *Digikam backtrace: sveinn@MIKLAFELL ~ $ gdb digikam GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.2) 7.7.1 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from digikam...Reading symbols from /usr/lib/debug/.build-id/d1/b0ef81f272f5bc1bbca37367a121860d97ac64.debug...done. done. (gdb) catch throw Catchpoint 1 (throw) (gdb) run Starting program: /usr/bin/digikam Traceback (most recent call last): File "/usr/share/gdb/auto-load/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.19-gdb.py", line 63, in <module> from libstdcxx.v6.printers import register_libstdcxx_printers ImportError: No module named 'libstdcxx' [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffcd3bc700 (LWP 3584)] [New Thread 0x7fffc3faf700 (LWP 3585)] [New Thread 0x7fffc37ae700 (LWP 3586)] Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath) Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath) [New Thread 0x7fffc2fad700 (LWP 3587)] [Thread 0x7fffc2fad700 (LWP 3587) exited] [New Thread 0x7fffc2fad700 (LWP 3588)] [New Thread 0x7fffac3ab700 (LWP 3589)] [Thread 0x7fffac3ab700 (LWP 3589) exited] [New Thread 0x7fffac3ab700 (LWP 3590)] [New Thread 0x7fffaa8f3700 (LWP 3591)] [Thread 0x7fffac3ab700 (LWP 3590) exited] [Thread 0x7fffaa8f3700 (LWP 3591) exited] [New Thread 0x7fffaa8f3700 (LWP 3592)] [New Thread 0x7fffac3ab700 (LWP 3593)] [New Thread 0x7fffa94a2700 (LWP 3594)] [New Thread 0x7fffa8ca1700 (LWP 3595)] [New Thread 0x7fff9bfff700 (LWP 3596)] [New Thread 0x7fff9b7fe700 (LWP 3597)] [New Thread 0x7fff9affd700 (LWP 3598)] [New Thread 0x7fff9a7fc700 (LWP 3599)] [New Thread 0x7fff99ffb700 (LWP 3600)] [New Thread 0x7fff997fa700 (LWP 3601)] [New Thread 0x7fff98ff9700 (LWP 3602)] [New Thread 0x7fff7bfff700 (LWP 3603)] [New Thread 0x7fff7b7fe700 (LWP 3604)] [New Thread 0x7fff7affd700 (LWP 3605)] [New Thread 0x7fff7a7fc700 (LWP 3606)] [New Thread 0x7fff79ffb700 (LWP 3607)] [New Thread 0x7fff797fa700 (LWP 3608)] [New Thread 0x7fff78ff9700 (LWP 3609)] [New Thread 0x7fff5bfff700 (LWP 3610)] [New Thread 0x7fff5b7fe700 (LWP 3611)] [New Thread 0x7fff5affd700 (LWP 3612)] [New Thread 0x7fff5a7fc700 (LWP 3613)] [New Thread 0x7fff59ffb700 (LWP 3614)] [New Thread 0x7fff597fa700 (LWP 3615)] [New Thread 0x7fff58ff9700 (LWP 3616)] [New Thread 0x7fff37fff700 (LWP 3617)] [New Thread 0x7fff377fe700 (LWP 3618)] [New Thread 0x7fff36ffd700 (LWP 3619)] [New Thread 0x7fff367fc700 (LWP 3620)] [New Thread 0x7fff35ffb700 (LWP 3621)] [New Thread 0x7fff357fa700 (LWP 3622)] [New Thread 0x7fff34ff9700 (LWP 3623)] [New Thread 0x7fff1ffff700 (LWP 3624)] [New Thread 0x7fff1f7fe700 (LWP 3625)] [New Thread 0x7fff1effd700 (LWP 3626)] [New Thread 0x7fff1e7fc700 (LWP 3627)] [New Thread 0x7fff1dffb700 (LWP 3628)] [New Thread 0x7fff1d7fa700 (LWP 3629)] [New Thread 0x7fff1cff9700 (LWP 3630)] [New Thread 0x7ffefbfff700 (LWP 3631)] [New Thread 0x7ffefb7fe700 (LWP 3632)] [New Thread 0x7ffefaffd700 (LWP 3633)] Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath) Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath) Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath) Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath) Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath) Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath) [Switching to Thread 0x7fffc3faf700 (LWP 3585)] Catchpoint 1 (exception thrown), 0x00007ffff10788b0 in __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (gdb) bt #0 0x00007ffff10788b0 in __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #1 0x00007fffeec955a7 in ?? () from /usr/lib/x86_64-linux-gnu/libexiv2.so.14 #2 0x00007fffeec95cea in ?? () from /usr/lib/x86_64-linux-gnu/libexiv2.so.14 #3 0x00007fffeec964cf in ?? () from /usr/lib/x86_64-linux-gnu/libexiv2.so.14 #4 0x00007fffeec96c89 in ?? () from /usr/lib/x86_64-linux-gnu/libexiv2.so.14 #5 0x00007fffeec7148a in ?? () from /usr/lib/x86_64-linux-gnu/libexiv2.so.14 #6 0x00007fffeec9f9c0 in ?? () from /usr/lib/x86_64-linux-gnu/libexiv2.so.14 #7 0x00007fffeec40e58 in ?? () from /usr/lib/x86_64-linux-gnu/libexiv2.so.14 #8 0x00007fffeec40ec0 in ?? () from /usr/lib/x86_64-linux-gnu/libexiv2.so.14 #9 0x00007fffeec3c1c0 in Exiv2::XmpParser::decode(Exiv2::XmpData&, std::string const&) () from /usr/lib/x86_64-linux-gnu/libexiv2.so.14 #10 0x00007fffeebbf206 in Exiv2::JpegBase::readMetadata() () from /usr/lib/x86_64-linux-gnu/libexiv2.so.14 #11 0x00007ffff6368aca in KExiv2Iface::KExiv2::load(QString const&) const () from /usr/lib/libkexiv2.so.11 #12 0x00007ffff5c7afb6 in Digikam::DMetadata::load ( this=this@entry=0x7fffbc2d8a50, filePath=...) at /build/digikam-6g9Kqs/digikam-4.12.0/core/libs/dmetadata/dmetadata.cpp:110 #13 0x00007ffff56d6c1f in Digikam::ImageScanner::loadFromDisk ( this=this@entry=0x7fffc3fae490) at /build/digikam-6g9Kqs/digikam-4.12.0/core/libs/database/imagescanner.cpp:1550 #14 0x00007ffff56d6e00 in Digikam::ImageScanner::newFile ( this=this@entry=0x7fffc3fae490, albumId=albumId@entry=1422) at /build/digikam-6g9Kqs/digikam-4.12.0/core/libs/database/imagescanner.cpp:289 #15 0x00007ffff566f636 in Digikam::CollectionScanner::scanNewFile ( this=this@entry=0x7fffc3faeae0, info=..., albumId=1422) at /build/digikam-6g9Kqs/digikam-4.12.0/core/libs/database/collectionscanner.cpp:1255 #16 0x00007ffff56727bf in Digikam::CollectionScanner::scanAlbum ( this=this@entry=0x7fffc3faeae0, location=..., album=...) at /build/digikam-6g9Kqs/digikam-4.12.0/core/libs/database/collectionscanner.cpp:1090 #17 0x00007ffff5672677 in Digikam::CollectionScanner::scanAlbum ( this=this@entry=0x7fffc3faeae0, location=..., album=...) at /build/digikam-6g9Kqs/digikam-4.12.0/core/libs/database/collectionscanner.cpp:1113 #18 0x00007ffff5673083 in Digikam::CollectionScanner::scanAlbumRoot ( this=this@entry=0x7fffc3faeae0, location=...) at /build/digikam-6g9Kqs/digikam-4.12.0/core/libs/database/collectionscanner.cpp:829 #19 0x00007ffff5673c5d in Digikam::CollectionScanner::completeScan ( this=this@entry=0x7fffc3faeae0) ---Type <return> to continue, or q <return> to quit--- at /build/digikam-6g9Kqs/digikam-4.12.0/core/libs/database/collectionscanner.cpp:490 #20 0x00000000005dafaf in Digikam::ScanController::run (this=0xfd4a90) at /build/digikam-6g9Kqs/digikam-4.12.0/core/app/database/scancontroller.cpp:756 #21 0x00007ffff161432f in QThreadPrivate::start (arg=0xfd4a90) at thread/qthread_unix.cpp:349 #22 0x00007fffedc5f182 in start_thread (arg=0x7fffc3faf700) at pthread_create.c:312 #23 0x00007ffff0b3947d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 (gdb) quit _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
Exiv2 library crash while XMP parsing. Report this problem to Exiv2 team... Gilles Caulier 2015-08-20 0:52 GMT+02:00 Sveinn í Felli <[hidden email]>: Hi, guess I'm also having the sorts of problem many Kubuntu/LinuxMint users are experiencing. Already upgraded my sqlite3/libsqlite3, also tested adding folders one by one to the collection; all was normal up to ~60 Gb of images or ~35 Mb of digikam4.db. Then the scan dies. _______________________________________________ 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 |