Bug 241767

Summary: crash after redirect mail
Product: [Applications] kontact Reporter: Roman Panfilov <roman-panfilov>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: 4.4.2   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Roman Panfilov 2010-06-14 21:45:53 UTC
Application: kontact (4.4.2)
KDE Platform Version: 4.4.2 (KDE 4.4.2)
Qt Version: 4.6.2
Operating System: Linux 2.6.31-21-generic i686
Distribution: Ubuntu 10.04 LTS

-- Information about the crash:
i recieve the mail. after that i redirect then to another person. when i push "send" it has crashed.

The crash can be reproduced some of the time.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  KMail::MessageListView::Widget::getSelectionStats (this=0x8f16858, selectedSernums=..., selectedVisibleSernums=..., allSelectedBelongToSameThread=0xbfabcf0f, 
    includeCollapsedChildren=<value optimized out>) at ../../kmail/messagelistview/widget.cpp:594
#7  0xb40e3066 in KMail::MessageListView::Pane::getSelectionStats (this=0x8f244a0, selectedSernums=..., selectedVisibleSernums=..., allSelectedBelongToSameThread=0xbfabcf0f, 
    includeCollapsedChildren=60) at ../../kmail/messagelistview/pane.cpp:646
#8  0xb3f95f6c in KMMainWidget::updateMessageActions (this=0x8f15280) at ../../kmail/kmmainwidget.cpp:4231
#9  0xb3faf172 in KMMainWidget::qt_metacall (this=0x8f15280, _c=QMetaObject::InvokeMetaMethod, _id=21, _a=0xbfabd01c) at ./kmmainwidget.moc:375
#10 0x00fe4c9a in QMetaObject::metacall (object=0x8f15280, cl=60, idx=48, argv=0xbfabd01c) at kernel/qmetaobject.cpp:237
#11 0x00ff33d5 in QMetaObject::activate (sender=0x90516e8, m=0x10f35a4, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3293
#12 0x01044aa7 in QTimer::timeout (this=0x90516e8) at .moc/release-shared/moc_qtimer.cpp:134
#13 0x00ffb60e in QTimer::timerEvent (this=0x90516e8, e=0xbfabd550) at kernel/qtimer.cpp:271
#14 0x00ff0254 in QObject::event (this=0x90516e8, e=0xb4357ee8) at kernel/qobject.cpp:1212
#15 0x0145c4dc in QApplicationPrivate::notify_helper (this=0x8a6f9c8, receiver=0x90516e8, e=0xbfabd550) at kernel/qapplication.cpp:4300
#16 0x0146305e in QApplication::notify (this=0xbfabd8b4, receiver=0x90516e8, e=0xbfabd550) at kernel/qapplication.cpp:3704
#17 0x00969f2a in KApplication::notify (this=0xbfabd8b4, receiver=0x90516e8, event=0xbfabd550) at ../../kdeui/kernel/kapplication.cpp:302
#18 0x00fdfa3b in QCoreApplication::notifyInternal (this=0xbfabd8b4, receiver=0x90516e8, event=0xbfabd550) at kernel/qcoreapplication.cpp:704
#19 0x0100ed66 in QCoreApplication::sendEvent (this=0x8a74884) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#20 QTimerInfoList::activateTimers (this=0x8a74884) at kernel/qeventdispatcher_unix.cpp:603
#21 0x0100b8e4 in timerSourceDispatch (source=0x8a74850) at kernel/qeventdispatcher_glib.cpp:184
#22 0x012855e5 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#23 0x012892d8 in ?? () from /lib/libglib-2.0.so.0
#24 0x012894b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#25 0x0100b5d5 in QEventDispatcherGlib::processEvents (this=0x8a4e588, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#26 0x0151c135 in QGuiEventDispatcherGlib::processEvents (this=0x8a4e588, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#27 0x00fde059 in QEventLoop::processEvents (this=0xbfabd814, flags=) at kernel/qeventloop.cpp:149
#28 0x00fde4aa in QEventLoop::exec (this=0xbfabd814, flags=...) at kernel/qeventloop.cpp:201
#29 0x00fe269f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#30 0x0145c577 in QApplication::exec () at kernel/qapplication.cpp:3579
#31 0x0804b472 in main (argc=1, argv=0xbfabdad4) at ../../../kontact/src/main.cpp:224

Possible duplicates by query: bug 240206, bug 237087, bug 234556, bug 233425, bug 233066.

Reported using DrKonqi
Comment 1 Christophe Marin 2010-06-14 22:27:32 UTC

*** This bug has been marked as a duplicate of bug 218693 ***