Bug 137204 - crash when applying IPTC data
Summary: crash when applying IPTC data
Status: RESOLVED WORKSFORME
Alias: None
Product: digikam
Classification: Applications
Component: Metadata-Iptc (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-11 18:57 UTC by Heiner Lamprecht
Modified: 2017-08-13 07:31 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 0.9.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Heiner Lamprecht 2006-11-11 18:57:54 UTC
Version:           0.9.0-svn / 2006-11-11 (using KDE KDE 3.5.5)
Installed from:    SuSE RPMs
Compiler:          gcc version 4.0.2 
OS:                Linux

When editing IPTC data, digikam crashes after clicking "Apply".  When clicking "OK", digikam does not crash, but the meta data is not written to the image.

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47732995024672 (LWP 3008)]
[KCrash handler]
#4  0x00002b69af7fdc9d in Exiv2::IptcData::size (this=<value optimized out>)
    at iptc.cpp:231
#5  0x00002b69af7fdcec in Exiv2::IptcData::copy (this=0xe22280) at iptc.cpp:191
#6  0x00002b69af8008cd in Exiv2::Photoshop::setIptcIrb (
    pPsData=<value optimized out>, sizePsData=40, iptcData=@0xe22280)
    at jpgimage.cpp:151
#7  0x00002b69af80248e in Exiv2::JpegBase::doWriteMetadata (this=0xe22200,
    outIo=@0xe08cd0) at jpgimage.cpp:502
#8  0x00002b69af802c9f in Exiv2::JpegBase::writeMetadata (this=0xe22200)
    at jpgimage.cpp:360
#9  0x00002aaaad55b8a0 in KIPIPlugins::Exiv2Iface::save (this=0x7ffffc2623b0,
    filePath=@0x7ffffc2623d0)
    at /work/heiner/Develop/digikam_64bit/unstable/libs/kipi-plugins/common/exiv2iface/exiv2iface.cpp:304
#10 0x00002aaaad52e09b in KIPIMetadataEditPlugin::IPTCEditDialog::slotApply (
    this=0x7ffffc262de0)
    at /work/heiner/Develop/digikam_64bit/unstable/libs/kipi-plugins/metadataedit/iptceditdialog.cpp:301
#11 0x00002b69b07f2596 in KDialogBase::qt_invoke ()
   from /opt/kde3/lib64//libkdeui.so.4
#12 0x00002aaaad53088c in KIPIMetadataEditPlugin::IPTCEditDialog::qt_invoke (
    this=0x7ffffc262de0, _id=75, _o=0x7ffffc2624c0)
    at /work/heiner/Develop/digikam_64bit/unstable/libs/kipi-plugins/metadataedit/iptceditdialog.moc:105
#13 0x00002b69b1a3f120 in QObject::activate_signal ()
   from /usr/lib64//libqt-mt.so.3
#14 0x00002b69b1a3fed3 in QObject::activate_signal ()
   from /usr/lib64//libqt-mt.so.3
#15 0x00002b69b1a72097 in QWidget::event () from /usr/lib64//libqt-mt.so.3
#16 0x00002b69b19e8155 in QApplication::internalNotify ()
   from /usr/lib64//libqt-mt.so.3
#17 0x00002b69b19e8f7b in QApplication::notify ()
   from /usr/lib64//libqt-mt.so.3
#18 0x00002b69b0e37a98 in KApplication::notify ()
   from /opt/kde3/lib64//libkdecore.so.4
#19 0x00002b69b19901b4 in QETWidget::translateMouseEvent ()
   from /usr/lib64//libqt-mt.so.3
#20 0x00002b69b198f393 in QApplication::x11ProcessEvent ()
   from /usr/lib64//libqt-mt.so.3
#21 0x00002b69b199e31f in QEventLoop::processEvents ()
   from /usr/lib64//libqt-mt.so.3
#22 0x00002b69b19fce61 in QEventLoop::enterLoop ()
   from /usr/lib64//libqt-mt.so.3
#23 0x00002b69b1b9e7fb in QDialog::exec () from /usr/lib64//libqt-mt.so.3
#24 0x00002aaaad5104b4 in Plugin_MetadataEdit::slotEditIptc (this=0x9767e0)
    at /work/heiner/Develop/digikam_64bit/unstable/libs/kipi-plugins/metadataedit/plugin_metadataedit.cpp:286
#25 0x00002aaaad511e01 in Plugin_MetadataEdit::qt_invoke (this=0x9767e0,
    _id=5, _o=0x7ffffc263030)
    at /work/heiner/Develop/digikam_64bit/unstable/libs/kipi-plugins/metadataedit/plugin_metadataedit.moc:95
#26 0x00002b69b1a3f1bc in QObject::activate_signal ()
   from /usr/lib64//libqt-mt.so.3
#27 0x00002b69b1a3fed3 in QObject::activate_signal ()
   from /usr/lib64//libqt-mt.so.3
#28 0x00002b69b0831b11 in KAction::qt_invoke ()
   from /opt/kde3/lib64//libkdeui.so.4
#29 0x00002b69b1a3f1bc in QObject::activate_signal ()
   from /usr/lib64//libqt-mt.so.3
#30 0x00002b69b1a3fed3 in QObject::activate_signal ()
   from /usr/lib64//libqt-mt.so.3
#31 0x00002b69b0da5915 in KAccelPrivate::emitActivatedSignal ()
   from /opt/kde3/lib64//libkdecore.so.4
#32 0x00002b69b0dee41f in KAccelPrivate::eventFilter ()
   from /opt/kde3/lib64//libkdecore.so.4
#33 0x00002b69b1a3ebc2 in QObject::activate_filters ()
   from /usr/lib64//libqt-mt.so.3
#34 0x00002b69b1a3ec17 in QObject::event () from /usr/lib64//libqt-mt.so.3
#35 0x00002b69b1a71cf8 in QWidget::event () from /usr/lib64//libqt-mt.so.3
#36 0x00002b69b1b1d6d5 in QMainWindow::event () from /usr/lib64//libqt-mt.so.3
#37 0x00002b69b19e8155 in QApplication::internalNotify ()
   from /usr/lib64//libqt-mt.so.3
#38 0x00002b69b19e9429 in QApplication::notify ()
   from /usr/lib64//libqt-mt.so.3
#39 0x00002b69b0e37a98 in KApplication::notify ()
   from /opt/kde3/lib64//libkdecore.so.4
#40 0x00002b69b0db0d59 in KAccelEventHandler::x11Event ()
   from /opt/kde3/lib64//libkdecore.so.4
#41 0x00002b69b0e2f4d8 in KApplication::x11EventFilter ()
   from /opt/kde3/lib64//libkdecore.so.4
#42 0x00002b69b1980347 in qt_x11EventFilter () from /usr/lib64//libqt-mt.so.3
#43 0x00002b69b198eb09 in QApplication::x11ProcessEvent ()
   from /usr/lib64//libqt-mt.so.3
#44 0x00002b69b199e31f in QEventLoop::processEvents ()
   from /usr/lib64//libqt-mt.so.3
#45 0x00002b69b19fce61 in QEventLoop::enterLoop ()
   from /usr/lib64//libqt-mt.so.3
#46 0x00002b69b19fcd0a in QEventLoop::exec () from /usr/lib64//libqt-mt.so.3
#47 0x0000000000402f5b in main (argc=1, argv=0x7ffffc263e78)
    at /work/heiner/Develop/digikam_64bit/unstable/graphics/digikam/digikam/main.cpp:269
Comment 1 Andreas Huggel 2006-11-18 01:29:28 UTC
Heiner,

We suspect this is a duplicate of bug #136855 and need your feedback to confirm if the problem is solved.

If you can still recreate this please try again with the latest Exiv2/digiKam/kipi-plugins from SVN. You need to compile and install Exiv2 first and cleanup digiKam/kipi-plugins before recompiling and installing it. 

Please report if the problem still occurs. Thanks!

-ahu.
Comment 2 Heiner Lamprecht 2006-11-18 17:42:53 UTC
Andreas,

using a fresh svn update, all works fine now.

Thanks,


    Heiner