Version: 0.7 (using KDE 3.2.3, (testing/unstable)) Compiler: gcc version 3.3.3 (Debian 20040422) OS: Linux (i686) release 2.6.8-1-686 In My Tags area. Select a image and then select Batch Process, then select Border Image (kipi-plugins) and the SEGFAULT. Process works fine if I perform action within My Album of same photo. I suspect the immediate fix is to disable Batch Processes on My Tags pictures, the longer term fix would be to correctly perform the action on the parerent image. Mark (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread 1099323424 (LWP 8925)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x411e6f5e in waitpid () from /lib/tls/libc.so.6 #0 0x411e6f5e in waitpid () from /lib/tls/libc.so.6 #1 0x4088bdd0 in KCrash::defaultCrashHandler () from /usr/lib/libkdecore.so.4 #2 <signal handler called> #3 0x4084622f in KProcess::operator<< () from /usr/lib/libkdecore.so.4 #4 0x41e0ba08 in KIPIBatchProcessImagesPlugin::BorderImagesDialog::makeProcess () from /usr/lib/kde3/kipiplugin_batchprocessimages.so #5 0x41e3a3ad in KIPIBatchProcessImagesPlugin::BatchProcessImagesDialog::startProcess () from /usr/lib/kde3/kipiplugin_batchprocessimages.so #6 0x41e39e73 in KIPIBatchProcessImagesPlugin::BatchProcessImagesDialog::slotProcessStart () from /usr/lib/kde3/kipiplugin_batchprocessimages.so #7 0x41e3eb37 in KIPIBatchProcessImagesPlugin::BatchProcessImagesDialog::qt_invoke () from /usr/lib/kde3/kipiplugin_batchprocessimages.so #8 0x41e0bbc4 in KIPIBatchProcessImagesPlugin::BorderImagesDialog::qt_invoke () from /usr/lib/kde3/kipiplugin_batchprocessimages.so #9 0x40c0b52c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #10 0x40c0b354 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #11 0x40672f6e in KDialogBase::user1Clicked () from /usr/lib/libkdeui.so.4 #12 0x40670f1f in KDialogBase::slotUser1 () from /usr/lib/libkdeui.so.4 #13 0x40673544 in KDialogBase::qt_invoke () from /usr/lib/libkdeui.so.4 #14 0x41e3ecd3 in KIPIBatchProcessImagesPlugin::BatchProcessImagesDialog::qt_invoke () from /usr/lib/kde3/kipiplugin_batchprocessimages.so #15 0x41e0bbc4 in KIPIBatchProcessImagesPlugin::BorderImagesDialog::qt_invoke () from /usr/lib/kde3/kipiplugin_batchprocessimages.so #16 0x40c0b52c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #17 0x40c0b354 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #18 0x40f5028e in QButton::clicked () from /usr/lib/libqt-mt.so.3 #19 0x40c9d97a in QButton::mouseReleaseEvent () from /usr/lib/libqt-mt.so.3 #20 0x40c41697 in QWidget::event () from /usr/lib/libqt-mt.so.3 #21 0x40baebcf in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #22 0x40bae2c4 in QApplication::notify () from /usr/lib/libqt-mt.so.3 #23 0x40806af9 in KApplication::notify () from /usr/lib/libkdecore.so.4 #24 0x40b43640 in QETWidget::translateMouseEvent () from /usr/lib/libqt-mt.so.3 #25 0x40b412ce in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3 #26 0x40b581a4 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #27 0x40bc0f28 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #28 0x40bc0dd8 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 #29 0x40baee21 in QApplication::exec () from /usr/lib/libqt-mt.so.3 #30 0x0804a274 in main ()
*** Bug 94376 has been marked as a duplicate of this bug. ***
CVS commit by pahlibar: * fix retrieving upload path from a virtual album (libkipi/uploadwidget) * fix crash in batchprocess plugin when no destination path is selected. the function thinks its being called in preview mode, but the preview process is null there. its dangerous to make an assumption of a passed arg being null, when its being called from multiple places in different modes. better use a separate explicit variable to indicate that the function is being called in a different mode. good for the sanity of those reading the code as well BUG: 94370 M +1 -1 kipi-plugins/batchprocessimages/batchprocessimagesdialog.cpp 1.48 M +2 -1 kipi-plugins/batchprocessimages/batchprocessimagesdialog.h 1.13 M +3 -3 kipi-plugins/batchprocessimages/borderimagesdialog.cpp 1.23 M +1 -1 kipi-plugins/batchprocessimages/borderimagesdialog.h 1.6 M +3 -3 kipi-plugins/batchprocessimages/colorimagesdialog.cpp 1.22 M +1 -1 kipi-plugins/batchprocessimages/colorimagesdialog.h 1.7 M +3 -3 kipi-plugins/batchprocessimages/convertimagesdialog.cpp 1.24 M +1 -1 kipi-plugins/batchprocessimages/convertimagesdialog.h 1.7 M +3 -3 kipi-plugins/batchprocessimages/effectimagesdialog.cpp 1.23 M +1 -1 kipi-plugins/batchprocessimages/effectimagesdialog.h 1.6 M +3 -3 kipi-plugins/batchprocessimages/filterimagesdialog.cpp 1.23 M +1 -1 kipi-plugins/batchprocessimages/filterimagesdialog.h 1.7 M +3 -3 kipi-plugins/batchprocessimages/recompressimagesdialog.cpp 1.21 M +1 -1 kipi-plugins/batchprocessimages/recompressimagesdialog.h 1.6 M +1 -1 kipi-plugins/batchprocessimages/resizeimagesdialog.cpp 1.27 M +1 -1 kipi-plugins/batchprocessimages/resizeimagesdialog.h 1.6 M +2 -2 libkipi/libkipi/uploadwidget.cpp 1.16