[digikam] [Bug 339803] New: digikam crashes frequently on batch rename

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 339803] New: digikam crashes frequently on batch rename

Bugzilla from reiner.nix@web.de
https://bugs.kde.org/show_bug.cgi?id=339803

            Bug ID: 339803
           Summary: digikam crashes frequently on batch rename
           Product: digikam
           Version: 4.3.0
          Platform: Debian testing
                OS: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: Advanced Rename
          Assignee: [hidden email]
          Reporter: [hidden email]

Using a pattern "[date:yyyy-MM-dd]_###" to rename a set of images digikam 4.3.0
crashes very frequently. My previously installed digikam 4.1.0 was stable.

Reproducible: Sometimes

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 339803] digikam crashes frequently on batch rename

Gilles Caulier-4
https://bugs.kde.org/show_bug.cgi?id=339803

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |BACKTRACE
                 CC|                            |[hidden email]
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #1 from Gilles Caulier <[hidden email]> ---
If it crash, we need a GDB backtrace to hack. See this page for details :

https://www.digikam.org/contrib

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 339803] digikam crashes frequently on batch rename

Bugzilla from reiner.nix@web.de
In reply to this post by Bugzilla from reiner.nix@web.de
https://bugs.kde.org/show_bug.cgi?id=339803

Reiner Nix <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |VERIFIED

--- Comment #2 from Reiner Nix <[hidden email]> ---
Hello Gilles,

well prepared to pass a link with the usefull debugging howto.

Here is the backtrace:
(...)
digikam(6098)/digikam (core) Digikam::ImageInfo::ImageInfo: No itemShortInfo
could be retrieved from the database for image "2014-07-20_025.JPG"
digikam(6098)/digikam (core) Digikam::ImageInfo::ImageInfo: No itemShortInfo
could be retrieved from the database for image "2014-07-20_025.JPG"
[Switching to Thread 0xa6b0fb40 (LWP 6103)]
Catchpoint 1 (exception thrown), 0xb4c2fa06 in __cxa_throw () from
/usr/lib/i386-linux-gnu/libstdc++.so.6
(gdb) bt
#0  0xb4c2fa06 in __cxa_throw () from /usr/lib/i386-linux-gnu/libstdc++.so.6
#1  0xb3a01417 in Exiv2::ImageFactory::open(std::auto_ptr<Exiv2::BasicIo>) ()
from /usr/lib/i386-linux-gnu/libexiv2.so.13
#2  0xb3a0151f in Exiv2::ImageFactory::open(std::string const&) () from
/usr/lib/i386-linux-gnu/libexiv2.so.13
#3  0xb7441574 in KExiv2Iface::KExiv2::load(QString const&) const () from
/usr/lib/libkexiv2.so.11
#4  0xb710ef3e in Digikam::DMetadata::load(QString const&) const () from
/usr/lib/digikam/libdigikamcore.so.4.3.0
#5  0xb6d73bba in Digikam::ImageScanner::loadFromDisk() () from
/usr/lib/digikam/libdigikamdatabase.so.4.3.0
#6  0xb6d73daa in Digikam::ImageScanner::fileModified() () from
/usr/lib/digikam/libdigikamdatabase.so.4.3.0
#7  0xb6cfe267 in Digikam::CollectionScanner::scanModifiedFile(QFileInfo
const&, Digikam::ItemScanInfo const&) ()
   from /usr/lib/digikam/libdigikamdatabase.so.4.3.0
#8  0xb6cfe87b in Digikam::CollectionScanner::scanFileNormal(QFileInfo const&,
Digikam::ItemScanInfo const&) ()
   from /usr/lib/digikam/libdigikamdatabase.so.4.3.0
#9  0xb6d01695 in
Digikam::CollectionScanner::scanAlbum(Digikam::CollectionLocation const&,
QString const&) ()
   from /usr/lib/digikam/libdigikamdatabase.so.4.3.0
#10 0xb6d02a3b in Digikam::CollectionScanner::partialScan(QString const&,
QString const&) () from /usr/lib/digikam/libdigikamdatabase.so.4.3.0
#11 0xb6d02ca5 in Digikam::CollectionScanner::partialScan(QString const&) ()
from /usr/lib/digikam/libdigikamdatabase.so.4.3.0
#12 0x082312a3 in ?? ()
#13 0xb4dc03be in ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#14 0xb36a6efb in start_thread (arg=0xa6b0fb40) at pthread_create.c:309
#15 0xb4abfd4e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129
(gdb)

I hope that this will be helpful.

Many thanks,
Reiner

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel