This could be related to bug 190273
If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? 
You need to install the "libqt4-dbg" package
Thanks

You will not get a better backtrace if this is the same problem as in bug 190273, you need to use valgrind to see anything useful.
Anyway you sure could try to use gdb for a backtrace, maybe it is something different.

correchouso@hotmail.com:
Can you please give us some more description what you did? First of all:
How do you resize?
Tools->Resize Images?

If so, this is not a digiKam problem.

Second question: When happened the crash? When clicking the close button? If o this might really be fixed in SVN.

Andi

(In reply to comment #2)
> You will not get a better backtrace if this is the same problem as in bug
> 190273, you need to use valgrind to see anything useful.
> Anyway you sure could try to use gdb for a backtrace, maybe it is something
> different.
> 
> correchouso@hotmail.com:
> Can you please give us some more description what you did? First of all:
> How do you resize?
> Tools->Resize Images?
> 
> If so, this is not a digiKam problem.
> 
> Second question: When happened the crash? When clicking the close button? If o
> this might really be fixed in SVN.
> 
> Andi

Digikam crash when I click the close button on the Batch --> Resize Images dialog. The resizing was completed.

(In reply to comment #1)
> This could be related to bug 190273
> If you can reproduce the crash at will, may you read
> http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
> and post a complete backtrace here? 
> You need to install the "libqt4-dbg" package
> Thanks

It looks similar to bug 190273.

It's a problem with Kipi plugins?

The new backtrace:

Application: digiKam (digikam), signal SIGSEGV
0x00007fe51162fd21 in nanosleep () from /lib/libc.so.6
[Current thread is 0 (LWP 7480)]

Thread 6 (Thread 0x7fe5026b8950 (LWP 7481)):
#0  0x00007fe5113772e9 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1  0x00007fe512111939 in QWaitCondition::wait (this=0x2773f78, mutex=0x2773f70, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:87
#2  0x000000000064bbb3 in ?? ()
#3  0x00007fe512110952 in QThreadPrivate::start (arg=0x274b3f0) at thread/qthread_unix.cpp:189
#4  0x00007fe5113733ba in start_thread () from /lib/libpthread.so.0
#5  0x00007fe51166dfcd in clone () from /lib/libc.so.6
#6  0x0000000000000000 in ?? ()

Thread 5 (Thread 0x7fe4fabbe950 (LWP 7483)):
#0  0x00007fe5113772e9 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1  0x00007fe512111939 in QWaitCondition::wait (this=0x28e2630, mutex=0x28e2628, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:87
#2  0x00007fe5159ed62c in Digikam::LoadSaveThread::run () from /usr/lib/libdigikamcore.so.1
#3  0x00007fe512110952 in QThreadPrivate::start (arg=0x28e2610) at thread/qthread_unix.cpp:189
#4  0x00007fe5113733ba in start_thread () from /lib/libpthread.so.0
#5  0x00007fe51166dfcd in clone () from /lib/libc.so.6
#6  0x0000000000000000 in ?? ()

Thread 4 (Thread 0x7fe4fa3bd950 (LWP 7484)):
#0  0x00007fe5113772e9 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1  0x00007fe512111939 in QWaitCondition::wait (this=0x2989020, mutex=0x2989018, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:87
#2  0x00007fe5159ed62c in Digikam::LoadSaveThread::run () from /usr/lib/libdigikamcore.so.1
#3  0x00007fe512110952 in QThreadPrivate::start (arg=0x2989000) at thread/qthread_unix.cpp:189
#4  0x00007fe5113733ba in start_thread () from /lib/libpthread.so.0
#5  0x00007fe51166dfcd in clone () from /lib/libc.so.6
#6  0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7fe4ef6d2950 (LWP 7506)):
#0  0x00007fe5113772e9 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1  0x00007fe512111939 in QWaitCondition::wait (this=0x3275e70, mutex=0x3275e68, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:87
#2  0x00007fe5159ed62c in Digikam::LoadSaveThread::run () from /usr/lib/libdigikamcore.so.1
#3  0x00007fe512110952 in QThreadPrivate::start (arg=0x3275e50) at thread/qthread_unix.cpp:189
#4  0x00007fe5113733ba in start_thread () from /lib/libpthread.so.0
#5  0x00007fe51166dfcd in clone () from /lib/libc.so.6
#6  0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7fe4f4dca950 (LWP 7523)):
#0  0x00007fe511666742 in select () from /lib/libc.so.6
#1  0x00007fe5121d7f06 in QProcessManager::run (this=0x2459580) at io/qprocess_unix.cpp:305
#2  0x00007fe512110952 in QThreadPrivate::start (arg=0x2459580) at thread/qthread_unix.cpp:189
#3  0x00007fe5113733ba in start_thread () from /lib/libpthread.so.0
#4  0x00007fe51166dfcd in clone () from /lib/libc.so.6
#5  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fe5186e2750 (LWP 7480)):
[KCrash Handler]
#5  QHash<QObject*, QString>::findNode (this=<value optimized out>, akey=<value optimized out>, ahp=0x0) at ../../include/QtCore/../../src/corelib/tools/qhash.h:863
#6  0x00007fe5122128d4 in QSignalMapper::map (this=0x45190b8, sender=0x451b4e0) at ../../include/QtCore/../../src/corelib/tools/qhash.h:850
#7  0x00007fe5122134b0 in QSignalMapper::qt_metacall (this=0x45190b8, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff20724230) at .moc/release-shared/moc_qsignalmapper.cpp:81
#8  0x00007fe51220f1f2 in QMetaObject::activate (sender=0x451b4e0, from_signal_index=<value optimized out>, to_signal_index=30, argv=0xc0) at kernel/qobject.cpp:3069
#9  0x00007fe5133e7547 in QAbstractButton::clicked (this=0x300, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:200
#10 0x00007fe5131450cb in QAbstractButtonPrivate::emitClicked (this=0x4515580) at widgets/qabstractbutton.cpp:543
#11 0x00007fe513146d32 in QAbstractButtonPrivate::click (this=0x4515580) at widgets/qabstractbutton.cpp:536
#12 0x00007fe513146f85 in QAbstractButton::mouseReleaseEvent (this=0x451b4e0, e=0x7fff20724a00) at widgets/qabstractbutton.cpp:1115
#13 0x00007fe512df397f in QWidget::event (this=0x451b4e0, event=0x7fff20724a00) at kernel/qwidget.cpp:7516
#14 0x00007fe512da283d in QApplicationPrivate::notify_helper (this=0x2454a60, receiver=0x451b4e0, e=0x7fff20724a00) at kernel/qapplication.cpp:4084
#15 0x00007fe512dab18a in QApplication::notify (this=<value optimized out>, receiver=0x451b4e0, e=0x7fff20724a00) at kernel/qapplication.cpp:3786
#16 0x00007fe5141d726b in KApplication::notify () from /usr/lib/libkdeui.so.5
#17 0x00007fe5121f975c in QCoreApplication::notifyInternal (this=0x7fff20725930, receiver=0x451b4e0, event=0x7fff20724a00) at kernel/qcoreapplication.cpp:602
#18 0x00007fe512daa3d8 in QApplicationPrivate::sendMouseEvent (receiver=0x451b4e0, event=0x7fff20724a00, alienWidget=0x451b4e0, nativeWidget=0x4519290, buttonDown=<value optimized out>, 
    lastMouseReceiver=@0x7fe513806eb0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216
#19 0x00007fe512e13ec9 in QETWidget::translateMouseEvent (this=0x4519290, event=<value optimized out>) at kernel/qapplication_x11.cpp:4425
#20 0x00007fe512e12b38 in QApplication::x11ProcessEvent (this=0x7fff20725930, event=0x7fff20725540) at kernel/qapplication_x11.cpp:3543
#21 0x00007fe512e3b514 in x11EventSourceDispatch (s=0x24586e0, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#22 0x00007fe50c14820a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#23 0x00007fe50c14b8e0 in ?? () from /usr/lib/libglib-2.0.so.0
#24 0x00007fe50c14ba7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#25 0x00007fe512222e6f in QEventDispatcherGlib::processEvents (this=0x243dcd0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:323
#26 0x00007fe512e3ac9f in QGuiEventDispatcherGlib::processEvents (this=0x300, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#27 0x00007fe5121f8002 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 544364592}) at kernel/qeventloop.cpp:149
#28 0x00007fe5121f83cd in QEventLoop::exec (this=0x7fff20725870, flags={i = 544364672}) at kernel/qeventloop.cpp:200
#29 0x00007fe5121fa694 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880
#30 0x0000000000671a37 in ?? ()
#31 0x00007fe5115a65a6 in __libc_start_main () from /lib/libc.so.6
#32 0x0000000000458839 in _start ()

Regards. Un saludo.

I'm pretty sure I have fixed this in SVN.
Gilles,

maybe we should release a kipi-plugins bugfix release?
None of the batch plugins is working in 0.3.0. We had discussed this before, but I guess we should do this immediately?
Releasing 0.3.1 this weekend?
I don't know if many distributions will change the kipiplugins package though, Archlinux will (its a rolling-release distro)...
Anyway I think we really should do this now.

Andi

correchouso: Why have you changed it back to digiKam?
It should be a kipiplugins problem. You can test this easily when using gwenview and call it from in there.

This is kipi-plugins not digiKam.

Gilles Caulier

To Andi #5,

>maybe we should release a kipi-plugins bugfix release?

yes, as 0.3.0 release

>None of the batch plugins is working in 0.3.0. 

0.2.0 you want mean...

>We had discussed this before,
>but I guess we should do this immediately?
>Releasing 0.3.1 this weekend?

0.3.0 (:=)))

>I don't know if many distributions will change the kipiplugins package though,
>Archlinux will (its a rolling-release distro)...
>Anyway I think we really should do this now.

Agree. I can prepare package sunday, or, if you want to do it now... It's easy to do. I'm on IRC to talk if you want info...

Gilles

(In reply to comment #8)
> yes, as 0.3.0 release
> 0.2.0 you want mean... 
> 0.3.0 (:=)))

:-)

Ok I messed this up. But shouldn't it be called 0.2.1 then?
Would make it more clear that it is some bugfix release...

Andi

Andi,

I think it's time to up release id to see quickly 1.0 release...

Gilles

Ok...

correchouso:

Can you test with the latest KIPI-Plugins version (0.3.0) or even SVN if the problem still exists?

Andi

(In reply to comment #12)
> correchouso:
> 
> Can you test with the latest KIPI-Plugins version (0.3.0) or even SVN if the
> problem still exists?
> 
> Andi

Where I could find this version? 

Regards.

I don't know where to find it in your distribution, you need to ask them where an updated package can be found.

Closing this one, it is definitely fixed.