Bug 186322

Summary: KMail crash on replying to mail
Product: [Unmaintained] kmail Reporter: René Krell <renda.krell>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: 1.11.1   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description René Krell 2009-03-06 11:02:56 UTC
Version:           1.11.1 (using 4.2.1 (KDE 4.2.1) "release 103", KDE:KDE4:Factory:Desktop / openSUSE_11.1)
Compiler:          gcc
OS:                Linux (i686) release 2.6.27.19-3.2-default

On replying to a mail, KMail crashed.
Using KDE 4.2.1 from OpenSUSE 11.1 / KDE 4.2 packages + Qt 4.5.0 (release).

Backtrace:

Application: Kontact (kontact), signal SIGSEGV
[?1034h[Thread debugging using libthread_db enabled]
[Current thread is 1 (Thread 0xb47cd700 (LWP 10804))]

Thread 4 (Thread 0xad7dab90 (LWP 10927)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb59c8411 in select () from /lib/libc.so.6
#2  0xb67d5477 in QProcessManager::run (this=0x80623a8) at io/qprocess_unix.cpp:305
#3  0xb670374e in QThreadPrivate::start (arg=0x80623a8) at thread/qthread_unix.cpp:189
#4  0xb66a01b5 in start_thread () from /lib/libpthread.so.0
#5  0xb59cf3be in clone () from /lib/libc.so.6

Thread 3 (Thread 0xb04f1b90 (LWP 11086)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb66a3f62 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xace49701 in ?? () from /usr/lib/libxine.so.1
#3  0xb66a01b5 in start_thread () from /lib/libpthread.so.0
#4  0xb59cf3be in clone () from /lib/libc.so.6

Thread 2 (Thread 0xaaf3db90 (LWP 11175)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb59c56a7 in poll () from /lib/libc.so.6
#2  0xb4f86ef2 in g_main_context_iterate (context=0x8186170, block=1, dispatch=1, self=0x9dc6590) at gmain.c:3091
#3  0xb4f87221 in IA__g_main_context_iteration (context=0x8186170, may_block=1) at gmain.c:2841
#4  0xb6823447 in QEventDispatcherGlib::processEvents (this=0xa204c50, flags={i = -1426861448}) at kernel/qeventdispatcher_glib.cpp:325
#5  0xb67f5ffa in QEventLoop::processEvents (this=0xaaf3d2f0, flags={i = -1426861384}) at kernel/qeventloop.cpp:149
#6  0xb67f643a in QEventLoop::exec (this=0xaaf3d2f0, flags={i = -1426861320}) at kernel/qeventloop.cpp:200
#7  0xb67003f9 in QThread::exec (this=0xa098300) at thread/qthread.cpp:481
#8  0xace9f8f9 in Phonon::Xine::XineThread::run (this=0xa098300) at /usr/src/debug/phonon-4.3.1/xine/xinethread.cpp:143
#9  0xb670374e in QThreadPrivate::start (arg=0xa098300) at thread/qthread_unix.cpp:189
#10 0xb66a01b5 in start_thread () from /lib/libpthread.so.0
#11 0xb59cf3be in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb47cd700 (LWP 10804)):
[KCrash Handler]
#6  0x092a3d9b in ?? ()
#7  0xb11ebfd3 in KMCommand::qt_metacall (this=0x8dd5e08, _c=QMetaObject::InvokeMetaMethod, _id=165570488, _a=0x4) at /usr/src/debug/kdepim-4.2.1/build/kmail/kmcommands.moc:85
#8  0xb11eca32 in KMReplyToCommand::qt_metacall (this=0x8dd5e08, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbfcc7ec8) at /usr/src/debug/kdepim-4.2.1/build/kmail/kmcommands.moc:822
#9  0xb680dc88 in QMetaObject::activate (sender=0x9d77b88, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3069
#10 0xb680f412 in QMetaObject::activate (sender=0x9d77b88, m=0xb68ed908, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3143
#11 0xb68130f7 in QSingleShotTimer::timeout (this=0x9d77b88) at .moc/release-shared/qtimer.moc:76
#12 0xb681321c in QSingleShotTimer::timerEvent (this=0x9d77b88) at kernel/qtimer.cpp:298
#13 0xb680812f in QObject::event (this=0x9d77b88, e=0xbfcc8370) at kernel/qobject.cpp:1082
#14 0xb5ca6eec in QApplicationPrivate::notify_helper (this=0x8072cf0, receiver=0x9d77b88, e=0xbfcc8370) at kernel/qapplication.cpp:4084
#15 0xb5caf1ae in QApplication::notify (this=0xbfcc8648, receiver=0x9d77b88, e=0xbfcc8370) at kernel/qapplication.cpp:3631
#16 0xb6db2a3d in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#17 0xb67f79db in QCoreApplication::notifyInternal (this=0xbfcc8648, receiver=0x9d77b88, event=0xbfcc8370) at kernel/qcoreapplication.cpp:602
#18 0xb6827026 in QTimerInfoList::activateTimers (this=0x8062eec) at kernel/qcoreapplication.h:213
#19 0xb68234d0 in timerSourceDispatch (source=0x8062eb8) at kernel/qeventdispatcher_glib.cpp:164
#20 0xb4f839a8 in IA__g_main_context_dispatch (context=0x80622e8) at gmain.c:2144
#21 0xb4f87063 in g_main_context_iterate (context=0x80622e8, block=1, dispatch=1, self=0x8072250) at gmain.c:2778
#22 0xb4f87221 in IA__g_main_context_iteration (context=0x80622e8, may_block=1) at gmain.c:2841
#23 0xb6823428 in QEventDispatcherGlib::processEvents (this=0x8058458, flags={i = -1077115624}) at kernel/qeventdispatcher_glib.cpp:323
#24 0xb5d46ac5 in QGuiEventDispatcherGlib::processEvents (this=0x8058458, flags={i = -1077115576}) at kernel/qguieventdispatcher_glib.cpp:202
#25 0xb67f5ffa in QEventLoop::processEvents (this=0xbfcc85c0, flags={i = -1077115512}) at kernel/qeventloop.cpp:149
#26 0xb67f643a in QEventLoop::exec (this=0xbfcc85c0, flags={i = -1077115448}) at kernel/qeventloop.cpp:200
#27 0xb67f88e9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880
#28 0xb5ca6d67 in QApplication::exec () at kernel/qapplication.cpp:3553
#29 0x0804bf8f in main (argc=1, argv=0xbfcc8944) at /usr/src/debug/kdepim-4.2.1/kontact/src/main.cpp:218
Comment 1 Jaime Torres 2009-03-06 13:02:00 UTC
Did you the following steps?

1. Right-click on an Email and Save As...
2. After saving, click on Reply.
3. Application crashes.

This is 99% sure a duplicate of bug 182629
Comment 2 René Krell 2009-03-06 13:08:47 UTC
As far as I remember that doesn't match the sequence of actions I did before the crash.
In the message list I chose the context menu (right-click on the message) and did a direct Reply... or Reply to Author... (not sure) as the first action after starting Kontact with KMail and reading the message. I hadn't saved any message in that session.
KMail crashed immediately, in my remembering even before the composer appeared.
Comment 3 Christophe Marin 2009-09-21 23:38:11 UTC

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