Bug 241889 - kmail crashed when hitting reply while still scrolling message
Summary: kmail crashed when hitting reply while still scrolling message
Status: RESOLVED DUPLICATE of bug 233574
Alias: None
Product: kmail
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: 2010-06-16 09:54 UTC by kavol
Modified: 2010-06-17 10:43 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 kavol 2010-06-16 09:54:55 UTC
Application that crashed: kmail
Version of the application: 1.12.4
KDE Version: 4.3.5 (KDE 4.3.5)
Qt Version: 4.6.2
Operating System: Linux 2.6.33-gentoo-r2 x86_64

What I was doing when the application crashed:
SSIA

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[KCrash Handler]
#5  0x0000000001abfee0 in ?? ()
#6  0x00007f5df5d096fe in KMCommand::slotStart (this=0x2394790) at /var/tmp/portage/kde-base/kmail-4.3.5/work/kmail-4.3.5/kmail/kmcommands.cpp:247
#7  0x00007f5df5cfa92a in KMCommand::qt_metacall (this=0x2394790, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff40aa34b0)
    at /var/tmp/portage/kde-base/kmail-4.3.5/work/kmail-4.3.5_build/kmail/kmcommands.moc:92
#8  0x00007f5df211d167 in QMetaObject::activate (sender=0x1d5cb60, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x2eee6d0) at kernel/qobject.cpp:3285
#9  0x00007f5df212435f in QSingleShotTimer::timerEvent (this=0x1d5cb60) at kernel/qtimer.cpp:308
#10 0x00007f5df2119c03 in QObject::event (this=0x1d5cb60, e=0x0) at kernel/qobject.cpp:1204
#11 0x00007f5df0d4cd2d in QApplicationPrivate::notify_helper (this=0x10371e0, receiver=0x1d5cb60, e=0x7fff40aa3cc0) at kernel/qapplication.cpp:4300
#12 0x00007f5df0d54124 in QApplication::notify (this=0x7fff40aa4120, receiver=0x1d5cb60, e=0x7fff40aa3cc0) at kernel/qapplication.cpp:3704
#13 0x00007f5df69f0d66 in KApplication::notify (this=0x7fff40aa4120, receiver=0x1d5cb60, event=0x7fff40aa3cc0)
    at /var/tmp/portage/kde-base/kdelibs-4.3.5/work/kdelibs-4.3.5/kdeui/kernel/kapplication.cpp:302
#14 0x00007f5df2109dab in QCoreApplication::notifyInternal (this=0x7fff40aa4120, receiver=0x1d5cb60, event=0x7fff40aa3cc0) at kernel/qcoreapplication.cpp:704
#15 0x00007f5df2136e94 in QCoreApplication::sendEvent (this=0x103aa60) at kernel/qcoreapplication.h:215
#16 QTimerInfoList::activateTimers (this=0x103aa60) at kernel/qeventdispatcher_unix.cpp:603
#17 0x00007f5df2133844 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#18 0x00007f5dea2b6d99 in g_main_dispatch (context=0x1039920) at gmain.c:1960
#19 IA__g_main_context_dispatch (context=0x1039920) at gmain.c:2513
#20 0x00007f5dea2ba5e8 in g_main_context_iterate (context=0x1039920, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2591
#21 0x00007f5dea2ba79c in IA__g_main_context_iteration (context=0x1039920, may_block=1) at gmain.c:2654
#22 0x00007f5df213354c in QEventDispatcherGlib::processEvents (this=0xa8feb0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#23 0x00007f5df0dfcfaf in QGuiEventDispatcherGlib::processEvents (this=0x1fdc560, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#24 0x00007f5df21086d2 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#25 0x00007f5df2108aa4 in QEventLoop::exec (this=0x7fff40aa3f70, flags=...) at kernel/qeventloop.cpp:201
#26 0x00007f5df210aef6 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#27 0x00000000004034db in main (argc=<value optimized out>, argv=<value optimized out>) at /var/tmp/portage/kde-base/kmail-4.3.5/work/kmail-4.3.5/kmail/main.cpp:146

This bug may be a duplicate of or related to bug 233574

Reported using DrKonqi
Comment 1 Nicolas L. 2010-06-17 10:43:47 UTC

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