Comment 101 for bug 1317449

Created attachment 87235
New crash information added by DrKonqi

digikam (4.0.0) on KDE Platform 4.13.1 using Qt 4.8.6

- What I was doing when the application crashed:
Another sample of the sql-related crash-when-opening-an-image-for-editing issue, on a freshly updated Kubuntu 14.04/KDE 4.13.1 system (Digikam was installed after said update).

-- Backtrace (Reduced):
#7 0x00007f1181b96dac in sqlite3MemCompare (pMem1=pMem1@entry=0x7fffe1e68ce0, pMem2=<optimized out>, pColl=0xa4ee338) at sqlite3.c:60484
#8 0x00007f1181b96f63 in sqlite3VdbeRecordCompare (nKey1=24, pKey1=0x7f11600979ae, pPKey2=pPKey2@entry=0x7fffe1e68fe0) at sqlite3.c:64162
#9 0x00007f1181bab579 in sqlite3BtreeMovetoUnpacked (pCur=0xadd9a50, pIdxKey=0x7fffe1e68fe0, intKey=0, biasRight=<optimized out>, pRes=0x7fffe1e68fd0) at sqlite3.c:55077
#10 0x00007f1181bd39c5 in sqlite3VdbeExec (p=p@entry=0x6b3e418) at sqlite3.c:70168
#11 0x00007f1181bdbed7 in sqlite3Step (p=0x6b3e418) at sqlite3.c:64828