Application: kontact (4.6 pre)
KDE Platform Version: 4.5.80 (4.6 Beta1)
Qt Version: 4.7.1
Operating System: Linux 2.6.36-89-default i686
Distribution: "openSUSE 11.3 (i586)"

-- Information about the crash:
kmail2 (embedded in kontact) showed one of its often occurring conflict dialogs regarding an email, where it asks if one should take the left or the right or both sides. After I choose the left side kontact crashed.

As this dialog pops up rather often and the crashed occured so far only once, I am not sure if/how good the bug is reproducable.

I will attach a screenshot of such a confilct dialog (when I see one again.)

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[Current thread is 1 (Thread 0xb2ea0710 (LWP 4218))]

Thread 2 (Thread 0xb09d5b70 (LWP 4219)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb4189125 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb620824c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libc.so.6
#3  0xb5ae3ca7 in ?? () from /usr/lib/libQtWebKit.so.4
#4  0xb4184b25 in start_thread () from /lib/libpthread.so.0
#5  0xb61fa46e in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb2ea0710 (LWP 4218)):
[KCrash Handler]
#7  0xb47252af in Akonadi::Item::setRevision (this=0xbff7adbc, rev=-1) at /usr/src/debug/kdepimlibs-4.5.80/akonadi/item.cpp:223
#8  0xb47bcc5c in Akonadi::ConflictHandler::useLocalItem (this=0xaef4f50) at /usr/src/debug/kdepimlibs-4.5.80/akonadi/conflicthandling/conflicthandler.cpp:103
#9  0xb47cf760 in Akonadi::ConflictHandler::resolve (this=0xaef4f50) at /usr/src/debug/kdepimlibs-4.5.80/akonadi/conflicthandling/conflicthandler.cpp:85
#10 0xb47cf90c in Akonadi::ConflictHandler::qt_metacall (this=0xaef4f50, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0xae9e8f8)
    at /usr/src/debug/kdepimlibs-4.5.80/build/akonadi/conflicthandler_p.moc:91
#11 0xb6fafe5d in QMetaObject::metacall (object=0xaef4f50, cl=QMetaObject::InvokeMetaMethod, idx=10, argv=0xae9e8f8) at kernel/qmetaobject.cpp:237
#12 0xb6fba945 in QMetaCallEvent::placeMetaCall (this=0x8278ef0, object=0xaef4f50) at kernel/qobject.cpp:534
#13 0xb6fbeb7f in QObject::event (this=0xaef4f50, e=0x8278ef0) at kernel/qobject.cpp:1211
#14 0xb64c1414 in QApplicationPrivate::notify_helper (this=0x80777a0, receiver=0xaef4f50, e=0x8278ef0) at kernel/qapplication.cpp:4445
#15 0xb64ca137 in QApplication::notify (this=0xbff7b694, receiver=0xaef4f50, e=0x8278ef0) at kernel/qapplication.cpp:3845
#16 0xb74db471 in KApplication::notify (this=0xbff7b694, receiver=0xaef4f50, event=0x8278ef0) at /usr/src/debug/kdelibs-4.5.80/kdeui/kernel/kapplication.cpp:311
#17 0xb6fa95be in QCoreApplication::notifyInternal (this=0xbff7b694, receiver=0xaef4f50, event=0x8278ef0) at kernel/qcoreapplication.cpp:732
#18 0xb6fad34c in sendEvent (receiver=0x0, event_type=0, data=0x80531c8) at kernel/qcoreapplication.h:215
#19 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x80531c8) at kernel/qcoreapplication.cpp:1373
#20 0xb6fad49c in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1266
#21 0xb6fd7bd4 in sendPostedEvents (s=0x8079b20) at kernel/qcoreapplication.h:220
#22 postEventSourceDispatch (s=0x8079b20) at kernel/qeventdispatcher_glib.cpp:277
#23 0xb4042b49 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#24 0xb4043350 in ?? () from /usr/lib/libglib-2.0.so.0
#25 0xb404360e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#26 0xb6fd7d5b in QEventDispatcherGlib::processEvents (this=0x8074950, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#27 0xb65779aa in QGuiEventDispatcherGlib::processEvents (this=0x8074950, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#28 0xb6fa889d in QEventLoop::processEvents (this=0xbff7b5f4, flags=...) at kernel/qeventloop.cpp:149
#29 0xb6fa8ac9 in QEventLoop::exec (this=0xbff7b5f4, flags=...) at kernel/qeventloop.cpp:201
#30 0xb6fad570 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#31 0xb64bf114 in QApplication::exec () at kernel/qapplication.cpp:3719
#32 0x0804b707 in _start ()

Reported using DrKonqi