Bug 188626 - kontact crashed when shift+deleting email
Summary: kontact crashed when shift+deleting email
Status: RESOLVED NOT A BUG
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-01 23:36 UTC by sovsep
Modified: 2009-10-23 10:37 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description sovsep 2009-04-01 23:36:48 UTC
Version:            (using KDE 4.2.1)
OS:                Linux
Installed from:    SuSE RPMs

Application: Kontact (kontact), signal SIGSEGV
0x00007f091a432ce1 in nanosleep () from /lib64/libc.so.6
[Current thread is 1 (Thread 0x7f0920b35750 (LWP 7679))]

Thread 2 (Thread 0x7f090201e950 (LWP 8854)):
#0  0x00007f091bfaed59 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f091c21ff79 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQtCore.so.4
#2  0x00007f091bd0910c in ?? () from /usr/lib64/libQtNetwork.so.4
#3  0x00007f091c21efc2 in ?? () from /usr/lib64/libQtCore.so.4
#4  0x00007f091bfab070 in start_thread () from /lib64/libpthread.so.0
#5  0x00007f091a46410d in clone () from /lib64/libc.so.6
#6  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f0920b35750 (LWP 7679)):
[KCrash Handler]
#5  0x00007f091a4111e7 in ?? () from /lib64/libc.so.6
#6  0x00007f091a40f3ca in memmove () from /lib64/libc.so.6
#7  0x00007f091c2428f9 in QListData::remove(int) () from /usr/lib64/libQtCore.so.4
#8  0x00007f091c24293b in QListData::erase(void**) () from /usr/lib64/libQtCore.so.4
#9  0x00007f090856dc4f in ?? () from /usr/lib64/libkmailprivate.so.4
#10 0x00007f0908561405 in ?? () from /usr/lib64/libkmailprivate.so.4
#11 0x00007f0908567a94 in ?? () from /usr/lib64/libkmailprivate.so.4
#12 0x00007f090856a155 in ?? () from /usr/lib64/libkmailprivate.so.4
#13 0x00007f090856a6ff in ?? () from /usr/lib64/libkmailprivate.so.4
#14 0x00007f090856b248 in ?? () from /usr/lib64/libkmailprivate.so.4
#15 0x00007f0908189f78 in ?? () from /usr/lib64/libkmailprivate.so.4
#16 0x00007f091c31d9c2 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4
#17 0x00007f091c317ce3 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#18 0x00007f091b001e8d in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#19 0x00007f091b00a09a in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#20 0x00007f091d11ad5b in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#21 0x00007f091c307f3c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#22 0x00007f091c335380 in ?? () from /usr/lib64/libQtCore.so.4
#23 0x00007f091c3316fd in ?? () from /usr/lib64/libQtCore.so.4
#24 0x00007f09159c70db in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#25 0x00007f09159ca8ad in ?? () from /usr/lib64/libglib-2.0.so.0
#26 0x00007f09159caa6b in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#27 0x00007f091c33165f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#28 0x00007f091b098b1f in ?? () from /usr/lib64/libQtGui.so.4
#29 0x00007f091c3067d2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#30 0x00007f091c306b9d in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#31 0x00007f091c308e84 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#32 0x0000000000404875 in _start ()
Comment 1 Dario Andres 2009-04-02 01:39:22 UTC
The trace isn't very useful.
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 "kdepim4-debuginfo" package
Thanks :)
Comment 2 Dario Andres 2009-05-07 02:43:15 UTC
Marking as NEEDSINFO
Comment 3 Andres Rodriguez Guapacha 2009-06-03 00:20:27 UTC
I had a similar problem, although not created by the same sequence of actions.

I was shift-deleting multiple contacts with the mouse and kontact crashed when I did the left click. This was the backtrace. I hope it helps:

Application: Kontact (kontact), signal SIGSEGV
0x00007f7e04b17831 in nanosleep () from /lib/libc.so.6

Thread 1 (Thread 0x7f7e07466760 (LWP 3847)):
[KCrash Handler]
#5  0x00007f7e01799498 in Q3ListViewItem::depth (this=0x35c58b0) at itemviews/q3listview.cpp:3815
#6  0x00007f7e017a54aa in Q3ListView::contentsMousePressEventEx (this=0x351d9c0, e=0x7fff0f5a4870) at itemviews/q3listview.cpp:4323
#7  0x00007f7e030ded4e in K3ListView::contentsMousePressEvent (this=0x351d9c0, e=0x7fff0f5a4870) at ../../kde3support/kdeui/k3listview.cpp:796
#8  0x00007f7e017fb2b9 in Q3ScrollView::viewportMousePressEvent (this=0x351d9c0, e=0x7fff0f5a5110) at widgets/q3scrollview.cpp:1742
#9  0x00007f7e017fca06 in Q3ScrollView::eventFilter (this=0x351d9c0, obj=0x351e470, e=0x7fff0f5a5110) at widgets/q3scrollview.cpp:1470
#10 0x00007f7e017a074e in Q3ListView::eventFilter (this=0x351d9c0, o=0x351e470, e=0x7fff0f5a5110) at itemviews/q3listview.cpp:3787
#11 0x00007f7e05e74158 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=<value optimized out>, receiver=0x351e470, event=0x7fff0f5a5110) at kernel/qcoreapplication.cpp:726
#12 0x00007f7e052b24cc in QApplicationPrivate::notify_helper (this=0x23f3520, receiver=0x351e470, e=0x7fff0f5a5110) at kernel/qapplication.cpp:4053
#13 0x00007f7e052baeda in QApplication::notify (this=<value optimized out>, receiver=0x351e470, e=0x7fff0f5a5110) at kernel/qapplication.cpp:3759
#14 0x00007f7e067fc55b in KApplication::notify (this=0x7fff0f5a6fb0, receiver=0x351e470, event=0x7fff0f5a5110) at ../../kdeui/kernel/kapplication.cpp:307
#15 0x00007f7e05e74e4c in QCoreApplication::notifyInternal (this=0x7fff0f5a6fb0, receiver=0x351e470, event=0x7fff0f5a5110) at kernel/qcoreapplication.cpp:610
#16 0x00007f7e052ba128 in QApplicationPrivate::sendMouseEvent (receiver=0x351e470, event=0x7fff0f5a5110, alienWidget=0x351e470, nativeWidget=0x252a720, buttonDown=<value optimized out>, 
    lastMouseReceiver=@0x7f7e05d1cc30) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216
#17 0x00007f7e05324009 in QETWidget::translateMouseEvent (this=0x252a720, event=<value optimized out>) at kernel/qapplication_x11.cpp:4448
#18 0x00007f7e05322d4d in QApplication::x11ProcessEvent (this=0x7fff0f5a6fb0, event=0x7fff0f5a6ae0) at kernel/qapplication_x11.cpp:3566
#19 0x00007f7e0534b4d4 in x11EventSourceDispatch (s=0x23e5e00, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#20 0x00007f7dff1e8f7a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#21 0x00007f7dff1ec640 in ?? () from /usr/lib/libglib-2.0.so.0
#22 0x00007f7dff1ec7dc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#23 0x00007f7e05e9e4bf in QEventDispatcherGlib::processEvents (this=0x23c4740, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:324
#24 0x00007f7e0534ac7f in QGuiEventDispatcherGlib::processEvents (this=0x35c58b0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#25 0x00007f7e05e736f2 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 257584592}) at kernel/qeventloop.cpp:149
#26 0x00007f7e05e73abd in QEventLoop::exec (this=0x7fff0f5a6e10, flags={i = 257584672}) at kernel/qeventloop.cpp:200
#27 0x00007f7e05e75d84 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#28 0x0000000000404741 in _start ()
Comment 4 Dario Andres 2009-06-03 14:39:59 UTC
@Andres: your bug looks more related to bug 170906 / bug 158179. Thanks
Comment 5 Christophe Marin 2009-10-23 10:37:02 UTC
Closing the old crash reports which don't have a useful backtrace. Thanks.