[digikam] [Bug 338358] New: Segmentation fault in libthread_db.so.1 saving jpag in new version after editing

[Yuri Ingultsov]

https://bugs.kde.org/show_bug.cgi?id=338358

            Bug ID: 338358
           Summary: Segmentation fault in libthread_db.so.1 saving jpag in
                    new version after editing
           Product: digikam
           Version: 4.1.0
          Platform: Kubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: Image Editor
          Assignee: [hidden email]
          Reporter: [hidden email]

Created attachment 88307
  --> https://bugs.kde.org/attachment.cgi?id=88307&action=edit
Backtrace, OS/KDE details and description

1. I get opend jpeg in editor
2. I added resize & sharpen filters
3. pressed "close editor" and then select save as new images
4. moved new verrion of image to another albut

repeat the steps above for several  images 2-5 time and it will crashed

--
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

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=338358

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |DUPLICATE
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |[hidden email]
          Component|Image Editor                |Database

--- Comment #1 from Gilles Caulier <[hidden email]> ---
Thread 1 (Thread 0x7f2e87baeac0 (LWP 5421)):
[KCrash Handler]
#6  0x0000000f00000030 in ?? ()
#7  0x00007f2e6ace8dac in sqlite3MemCompare (pMem1=pMem1@entry=0x7fff56b27100,
pMem2=<optimized out>, pColl=0x1e240c8) at sqlite3.c:60484
#8  0x00007f2e6ace8f63 in sqlite3VdbeRecordCompare (nKey1=37, pKey1=0x45a7ea3,
pPKey2=pPKey2@entry=0x7fff56b27400) at sqlite3.c:64162
#9  0x00007f2e6acfd579 in sqlite3BtreeMovetoUnpacked (pCur=0x5433cf0,
pIdxKey=0x7fff56b27400, intKey=0, biasRight=<optimized out>,
pRes=0x7fff56b273f0) at sqlite3.c:55077
#10 0x00007f2e6ad259c5 in sqlite3VdbeExec (p=p@entry=0x6d5c958) at
sqlite3.c:70168
#11 0x00007f2e6ad2ded7 in sqlite3Step (p=0x6d5c958) at sqlite3.c:64828
#12 sqlite3_step (pStmt=<optimized out>) at sqlite3.c:64894

It's the Sqlite BC problem...

Gilles Caulier

*** This bug has been marked as a duplicate of bug 329697 ***

--
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

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=338358

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Database                    |Database-Sqlite

--
You are receiving this mail because:
You are the assignee for the bug.