Bug 218748 - The crash occurred while an e-mail message was being read and/or saved in Kmail.
Summary: The crash occurred while an e-mail message was being read and/or saved in Kmail.
Status: RESOLVED DUPLICATE of bug 218693
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-15 04:28 UTC by K. A. Sayeed
Modified: 2009-12-15 14:01 UTC (History)
1 user (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 K. A. Sayeed 2009-12-15 04:28:29 UTC
Application that crashed: kontact
Version of the application: 4.3.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-16-generic x86_64
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
An e-mail message was just saved in the Ubuntu File Browser and it was being examined there when Kontact crashed.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
The current source language is "auto; currently c".
[KCrash Handler]
#5  KMail::MessageListView::Widget::getSelectionStats (this=0x2ade360, selectedSernums=..., selectedVisibleSernums=<value optimized out>, allSelectedBelongToSameThread=<value optimized out>, 
    includeCollapsedChildren=<value optimized out>) at ../../kmail/messagelistview/widget.cpp:580
#6  0x00007f46379ffc1e in KMMainWidget::updateMessageActions (this=0x2adbbd0) at ../../kmail/kmmainwidget.cpp:4274
#7  0x00007f4637a167bd in KMMainWidget::qt_metacall (this=0x2adbbd0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff25b5d530) at ./kmmainwidget.moc:367
#8  0x00007f4657353ddc in QMetaObject::activate (sender=0x2e69f20, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3113
#9  0x00007f465734dd83 in QObject::event (this=0x2e69f20, e=0x31) at kernel/qobject.cpp:1075
#10 0x00007f4657c5eefc in QApplicationPrivate::notify_helper (this=0x2262f60, receiver=0x2e69f20, e=0x7fff25b5db30) at kernel/qapplication.cpp:4056
#11 0x00007f4657c661ce in QApplication::notify (this=0x7fff25b5de90, receiver=0x2e69f20, e=0x7fff25b5db30) at kernel/qapplication.cpp:4021
#12 0x00007f4658895ab6 in KApplication::notify (this=0x7fff25b5de90, receiver=0x2e69f20, event=0x7fff25b5db30) at ../../kdeui/kernel/kapplication.cpp:302
#13 0x00007f465733ec2c in QCoreApplication::notifyInternal (this=0x7fff25b5de90, receiver=0x2e69f20, event=0x7fff25b5db30) at kernel/qcoreapplication.cpp:610
#14 0x00007f4657369862 in QCoreApplication::sendEvent (this=0x225bda0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#15 QTimerInfoList::activateTimers (this=0x225bda0) at kernel/qeventdispatcher_unix.cpp:572
#16 0x00007f465736725d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165
#17 0x00007f4650bb8bbe in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#18 0x00007f4650bbc588 in ?? () from /lib/libglib-2.0.so.0
#19 0x00007f4650bbc6b0 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#20 0x00007f46573671a6 in QEventDispatcherGlib::processEvents (this=0x222fcb0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#21 0x00007f4657cf34be in QGuiEventDispatcherGlib::processEvents (this=0x28bdaa0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#22 0x00007f465733d532 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#23 0x00007f465733d904 in QEventLoop::exec (this=0x7fff25b5ddd0, flags=) at kernel/qeventloop.cpp:201
#24 0x00007f465733fab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#25 0x0000000000403f47 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../../kontact/src/main.cpp:218

Reported using DrKonqi
Comment 1 Dario Andres 2009-12-15 14:01:00 UTC
Merging with bug 218693 Thanks

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