Bug 218913 - I clicked on to open a sent kmail message and the crash occured
Summary: I clicked on to open a sent kmail message and the crash occured
Status: RESOLVED DUPLICATE of bug 180741
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-12-16 13:01 UTC by John Richardson
Modified: 2010-01-20 23:52 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 John Richardson 2009-12-16 13:01:00 UTC
Application that crashed: kmail
Version of the application: 1.12.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-17-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
I sent an email as a test ater initial KMAIL config and went to the SENT folder to open the message again as a test. It is then when KMAIL crashed.

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[Current thread is 1 (Thread 0xb78b1aa0 (LWP 5037))]

Thread 2 (Thread 0xaff28b70 (LWP 5107)):
#0  0x007d0422 in __kernel_vsyscall ()
#1  0x056b0e15 in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:122
#2  0x07e6878d in __pthread_cond_wait (cond=0x9707da8, mutex=0x9707d90) at forward.c:139
#3  0x00cb2e67 in QWaitConditionPrivate::wait (this=0x96c1340, mutex=0x96c133c, time=4294967295) at thread/qwaitcondition_unix.cpp:87
#4  QWaitCondition::wait (this=0x96c1340, mutex=0x96c133c, time=4294967295) at thread/qwaitcondition_unix.cpp:159
#5  0x057df922 in QHostInfoAgent::run (this=0x96c1330) at kernel/qhostinfo.cpp:260
#6  0x00cb1e32 in QThreadPrivate::start (arg=0x96c1330) at thread/qthread_unix.cpp:188
#7  0x056ac80e in start_thread (arg=0xaff28b70) at pthread_create.c:300
#8  0x07e5b7ee in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb78b1aa0 (LWP 5037)):
[KCrash Handler]
#6  0x010be640 in KMReaderWin::parseMsg (this=0x8f2c678, aMsg=0x96b1a68) at ../../kmail/kmreaderwin.cpp:1681
#7  0x010aa4d9 in KMReaderWin::displayMessage (this=0x8f2c678) at ../../kmail/kmreaderwin.cpp:1605
#8  0x010aa6cb in KMReaderWin::updateReaderWin (this=0x8f2c678) at ../../kmail/kmreaderwin.cpp:1545
#9  0x010b79d4 in KMReaderWin::qt_metacall (this=0x8f2c678, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbf95cd7c) at ./kmreaderwin.moc:168
#10 0x00db8263 in QMetaObject::activate (sender=0x8f2c6d0, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113
#11 0x00db8ec2 in QMetaObject::activate (sender=0x8f2c6d0, m=0xe93904, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187
#12 0x00df2667 in QTimer::timeout (this=0x8f2c6d0) at .moc/release-shared/moc_qtimer.cpp:128
#13 0x00dbd9ae in QTimer::timerEvent (this=0x8f2c6d0, e=0xbf95d210) at kernel/qtimer.cpp:261
#14 0x00db23bf in QObject::event (this=0x8f2c6d0, e=0xbf95d210) at kernel/qobject.cpp:1075
#15 0x02f79f54 in QApplicationPrivate::notify_helper (this=0x8cf0808, receiver=0x8f2c6d0, e=0xbf95d210) at kernel/qapplication.cpp:4056
#16 0x02f8167c in QApplication::notify (this=0xbf95d610, receiver=0x8f2c6d0, e=0xbf95d210) at kernel/qapplication.cpp:3603
#17 0x003f4bfa in KApplication::notify (this=0xbf95d610, receiver=0x8f2c6d0, event=0xbf95d210) at ../../kdeui/kernel/kapplication.cpp:302
#18 0x00da26cb in QCoreApplication::notifyInternal (this=0xbf95d610, receiver=0x8f2c6d0, event=0xbf95d210) at kernel/qcoreapplication.cpp:610
#19 0x00dcf7ce in QCoreApplication::sendEvent (this=0x8cf318c) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#20 QTimerInfoList::activateTimers (this=0x8cf318c) at kernel/qeventdispatcher_unix.cpp:572
#21 0x00dcd0e0 in timerSourceDispatch (source=0x8cf3158) at kernel/qeventdispatcher_glib.cpp:165
#22 0x0287ae88 in g_main_dispatch (context=0x8cf2110) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:1960
#23 IA__g_main_context_dispatch (context=0x8cf2110) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2513
#24 0x0287e730 in g_main_context_iterate (context=0x8cf2110, block=<value optimized out>, dispatch=1, self=0x8cefd48) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2591
#25 0x0287e863 in IA__g_main_context_iteration (context=0x8cf2110, may_block=1) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2654
#26 0x00dcd02c in QEventDispatcherGlib::processEvents (this=0x8cca180, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#27 0x0301abe5 in QGuiEventDispatcherGlib::processEvents (this=0x8cca180, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#28 0x00da0c79 in QEventLoop::processEvents (this=0xbf95d4d4, flags=) at kernel/qeventloop.cpp:149
#29 0x00da10ca in QEventLoop::exec (this=0xbf95d4d4, flags=...) at kernel/qeventloop.cpp:201
#30 0x00da353f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#31 0x02f79dd7 in QApplication::exec () at kernel/qapplication.cpp:3525
#32 0x0804a702 in main (argc=3, argv=0xbf95d7c4) at ../../kmail/main.cpp:146

Reported using DrKonqi
Comment 1 Dario Andres 2009-12-17 00:36:45 UTC
This looks like bug 180741. Can you check
https://bugs.kde.org/show_bug.cgi?id=180741#c41 ? Thanks
Comment 2 Dario Andres 2010-01-20 23:52:03 UTC

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