[Digikam-devel] [Bug 165348] New: Problems when trying to import KDE3 data

Thomas McGuire Thomas.McGuire at gmx.net
Sun Jun 29 17:14:12 BST 2008

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
           Summary: Problems when trying to import KDE3 data
           Product: digikam
           Version: 0.10.0-svn
          Platform: Compiled Sources
        OS/Version: Linux
            Status: NEW
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: digikam-devel kde org
        ReportedBy: Thomas.McGuire gmx net

Version:           0.10.0-svn (using Devel)
Installed from:    Compiled sources
OS:                Linux

Importing my old Digikam data does not seems to work, or has too many problems to work correctly.

I didn't want to loose all my tags, so I copied over my old $HOME/share/config/digikamrc and $HOME/share/apps/digikam/ over to my KDE4 home directory.
My picture directory, which also contained the database files, remained the same.

When I then started Digikam, A progress dialog was shown, which contained a listview which showed the folder which was currently processed.
Problem: There was no label or caption saying what digikam actually does at that moment.

During processing, I got a lot of warnings like:

Cannot find Exif key 'Exif.Pentax.LensType' into image using Exiv2  (Error #6: Invalid key `Exif.Pentax.LensType')
digikam(23164): "/media/daten/Bilder/Fotos/Zuhause/2005-07-28/imag0031.jpg"  : JPEG file identified
DateTime => Exif.Photo.DateTimeOriginal =>  QDateTime("Thu Jul 28 06:40:17 2005")

Orientation => Exif.Image.Orientation =>  1

Not sure if these warnings matter

At some point, the dialog froze completely.
The last lines of output were:

digikam(23164): Returning true from updating to 5
digikam(23164): Success updating to v5

I attached GDB to the process and it showed the following backtrace for the frozen Digikam:

#0  0xffffe403 in __kernel_vsyscall ()
#1  0xb7d07566 in pthread_cond_wait  GLIBC_2 3 2 () from /lib/libpthread.so.0
#2  0xb7da8230 in QMutexPrivate::wait () from /media/kdedev/trunk/qt-copy/lib/libQtCore.so.4
#3  0xb7da2892 in QMutex::lock () from /media/kdedev/trunk/qt-copy/lib/libQtCore.so.4
#4  0xb70eb004 in DatabaseAccess (this=0xbfe21feb) at /media/kdedev/trunk/src/KDE/graphics/digikam/libs/database/databaseaccess.cpp:73
#5  0xb70fd81f in Digikam::ImageInfoCache::slotImageChanged (this=0x8432a00, changeset= 0xb1739378) at /media/kdedev/trunk/src/KDE/graphics/digikam/libs/database/imageinfocache.cpp:92
#6  0xb70fe27a in Digikam::ImageInfoCache::qt_metacall (this=0x8432a00, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xb1716768) at /media/kdedev/trunk/build/KDE/graphics/digikam/digikam/imageinfocache.moc:68
#7  0xb7eac5a6 in QMetaCallEvent::placeMetaCall () from /media/kdedev/trunk/qt-copy/lib/libQtCore.so.4
#8  0xb7eb094c in QObject::event () from /media/kdedev/trunk/qt-copy/lib/libQtCore.so.4
#9  0xb5860e0d in QApplicationPrivate::notify_helper () from /media/kdedev/trunk/qt-copy/lib/libQtGui.so.4
#10 0xb5861126 in QApplication::notify () from /media/kdedev/trunk/qt-copy/lib/libQtGui.so.4
#11 0xb7988f6b in KApplication::notify (this=0xbfe229cc, receiver=0x8432a00, event=0xb1730c40) at /media/kdedev/trunk/src/KDE/kdelibs/kdeui/kernel/kapplication.cpp:311
#12 0xb7e9d88a in QCoreApplication::notifyInternal () from /media/kdedev/trunk/qt-copy/lib/libQtCore.so.4
#13 0xb7ea13c9 in QCoreApplication::sendEvent () from /media/kdedev/trunk/qt-copy/lib/libQtCore.so.4
#14 0xb7e9dda2 in QCoreApplicationPrivate::sendPostedEvents () from /media/kdedev/trunk/qt-copy/lib/libQtCore.so.4
#15 0xb7e9df53 in QCoreApplication::sendPostedEvents () from /media/kdedev/trunk/qt-copy/lib/libQtCore.so.4
#16 0xb7eceb1e in QCoreApplication::sendPostedEvents () from /media/kdedev/trunk/qt-copy/lib/libQtCore.so.4
#17 0xb7ecdd2f in postEventSourceDispatch () from /media/kdedev/trunk/qt-copy/lib/libQtCore.so.4
#18 0xb50725d6 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#19 0xb5075972 in ?? () from /usr/lib/libglib-2.0.so.0
#20 0x08384c90 in ?? ()
#21 0x00000000 in ?? ()

I killed Digikam afterwards.

I restarted digikam. It showed the progress dialog again, and then eventually crashed with the following backtrace:

Application: digiKam (digikam), signal SIGSEGV
[Thread debugging using libthread_db enabled]
[New Thread 0xb49e66d0 (LWP 23376)]
[New Thread 0xb298eb90 (LWP 23390)]
[New Thread 0xb218db90 (LWP 23389)]
[New Thread 0xb3401b90 (LWP 23380)]
[KCrash handler]
#6  0x081ebc1c in Digikam::Album::insertChild (this=0x1, child=0xc135f80)
    at /media/kdedev/trunk/src/KDE/graphics/digikam/digikam/album.cpp:101
#7  0x081ebc9f in Digikam::Album::setParent (this=0xc135f80, parent=0x1)
    at /media/kdedev/trunk/src/KDE/graphics/digikam/digikam/album.cpp:67
#8  0x0821fc3e in Digikam::AlbumManager::scanTAlbums (this=0x83ef878)
    at /media/kdedev/trunk/src/KDE/graphics/digikam/digikam/albummanager.cpp:728
#9  0x08222324 in Digikam::AlbumManager::refresh (this=0x83ef878)
    at /media/kdedev/trunk/src/KDE/graphics/digikam/digikam/albummanager.cpp:497
#10 0x08222a07 in Digikam::AlbumManager::startScan (this=0x83ef878)
    at /media/kdedev/trunk/src/KDE/graphics/digikam/digikam/albummanager.cpp:435
#11 0x0825a921 in DigikamApp (this=0x84ed488)
    at /media/kdedev/trunk/src/KDE/graphics/digikam/digikam/digikamapp.cpp:200
#12 0x0828fce2 in main (argc=1, argv=0xbfe2dde4)
    at /media/kdedev/trunk/src/KDE/graphics/digikam/digikam/main.cpp:318
#0  0xffffe410 in __kernel_vsyscall ()

In short: I was unable to import my old tags, and thus I cannot upgrade to the KDE4 version at the moment.

More information about the Digikam-devel mailing list