Bug 197747 - kmail new message send crash
Summary: kmail new message send crash
Status: RESOLVED DUPLICATE of bug 195893
Alias: None
Product: kmail
Classification: Unmaintained
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-06-24 17:34 UTC by Ed
Modified: 2009-06-24 18:09 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ed 2009-06-24 17:34:51 UTC
Application that crashed: kmail
Version of the application: 1.11.90
KDE Version: 4.2.90 (KDE 4.2.90 (KDE 4.3 Beta2))
Qt Version: 4.5.0
Operating System: Linux 2.6.28-13-generic x86_64
Distribution: Ubuntu 9.04

What I was doing when the application crashed:
Kmail crashed after I had created a new message, added subject and body then clicked send on new mesage window toolbar and it crashed.

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[KCrash Handler]
#5  KMail::MessageListView::Widget::getSelectionStats (this=0x22a6440, selectedSernums=@0x7fff52c98a90, selectedVisibleSernums=@0x7fff52c98a80, allSelectedBelongToSameThread=0x7fff52c98aaf, 
    includeCollapsedChildren=<value optimized out>) at /build/buildd/kdepim-4.2.90/kmail/messagelistview/widget.cpp:579
#6  0x00007f89499e307c in KMMainWidget::updateMessageActions (this=0x22aa0c0) at /build/buildd/kdepim-4.2.90/kmail/kmmainwidget.cpp:4280
#7  0x00007f89499faacd in KMMainWidget::qt_metacall (this=0x22aa0c0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff52c98bb0)
    at /build/buildd/kdepim-4.2.90/obj-x86_64-linux-gnu/kmail/kmmainwidget.moc:366
#8  0x00007f894601e1f2 in QMetaObject::activate (sender=0x2ce4c20, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3069
#9  0x00007f89460184d3 in QObject::event (this=0x2ce4c20, e=0x2a5) at kernel/qobject.cpp:1082
#10 0x00007f894674d78d in QApplicationPrivate::notify_helper (this=0x1e74b50, receiver=0x2ce4c20, e=0x7fff52c99260) at kernel/qapplication.cpp:4084
#11 0x00007f894675597a in QApplication::notify (this=0x7fff52c996c0, receiver=0x2ce4c20, e=0x7fff52c99260) at kernel/qapplication.cpp:4049
#12 0x00007f894a68406b in KApplication::notify (this=0x7fff52c996c0, receiver=0x2ce4c20, event=0x7fff52c99260) at /build/buildd/kde4libs-4.2.90/kdeui/kernel/kapplication.cpp:302
#13 0x00007f894600875c in QCoreApplication::notifyInternal (this=0x7fff52c996c0, receiver=0x2ce4c20, event=0x7fff52c99260) at kernel/qcoreapplication.cpp:602
#14 0x00007f89460357f6 in QTimerInfoList::activateTimers (this=0x1e780d0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#15 0x00007f8946031f0d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:164
#16 0x00007f893ce9220a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#17 0x00007f893ce958e0 in ?? () from /usr/lib/libglib-2.0.so.0
#18 0x00007f893ce95a7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#19 0x00007f8946031e6f in QEventDispatcherGlib::processEvents (this=0x1e2e4e0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:323
#20 0x00007f89467e5bef in QGuiEventDispatcherGlib::processEvents (this=0x21a4ea0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#21 0x00007f8946007002 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 1388942544}) at kernel/qeventloop.cpp:149
#22 0x00007f89460073cd in QEventLoop::exec (this=0x7fff52c99510, flags={i = 1388942624}) at kernel/qeventloop.cpp:200
#23 0x00007f8946009694 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880
#24 0x00000000004030bb in main (argc=<value optimized out>, argv=<value optimized out>) at /build/buildd/kdepim-4.2.90/kmail/main.cpp:146

Reported using DrKonqi
Comment 1 Dario Andres 2009-06-24 18:09:41 UTC
This was fixed recently. Thanks

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