Bug 256545 - Kontact crash while sending receipt confirmation
Summary: Kontact crash while sending receipt confirmation
Status: RESOLVED DUPLICATE of bug 254750
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-10 19:55 UTC by Alexis Kauffmann
Modified: 2010-11-22 20:10 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 Alexis Kauffmann 2010-11-10 19:55:45 UTC
Application: kontact (4.4.6)
KDE Platform Version: 4.5.1 (KDE 4.5.1)
Qt Version: 4.7.0
Operating System: Linux 2.6.35-22-generic x86_64
Distribution: Ubuntu 10.10

-- Information about the crash:
I received a professional email that asked for a confirmation receipt. Kontact then crashed when I clicked "Yes" after Kmail asked me if I wanted it to send the confirmation. This problem had not occurred before. After Kontact restarted, i coild successfully send the confirmation receipt, no problem at all.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[Current thread is 1 (Thread 0x7fbef230f780 (LWP 2460))]

Thread 2 (Thread 0x7fbec5669710 (LWP 2757)):
#0  0x00007fbeea447c9d in __pthread_mutex_unlock_usercnt (mutex=0x215f1c8) at pthread_mutex_unlock.c:52
#1  __pthread_mutex_unlock (mutex=0x215f1c8) at pthread_mutex_unlock.c:290
#2  0x00007fbee80b4b51 in g_main_context_prepare () from /lib/libglib-2.0.so.0
#3  0x00007fbee80b4e78 in ?? () from /lib/libglib-2.0.so.0
#4  0x00007fbee80b545c in g_main_context_iteration () from /lib/libglib-2.0.so.0
#5  0x00007fbeefa861e6 in QEventDispatcherGlib::processEvents (this=0x1147110, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:417
#6  0x00007fbeefa58a02 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#7  0x00007fbeefa58dec in QEventLoop::exec (this=0x7fbec5668d90, flags=) at kernel/qeventloop.cpp:201
#8  0x00007fbeef9632fd in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:490
#9  0x00007fbeefa385f8 in QInotifyFileSystemWatcherEngine::run (this=0x1f93530) at io/qfilesystemwatcher_inotify.cpp:248
#10 0x00007fbeef96627e in QThreadPrivate::start (arg=0x1f93530) at thread/qthread_unix.cpp:266
#11 0x00007fbeea444971 in start_thread (arg=<value optimized out>) at pthread_create.c:304
#12 0x00007fbeef34e91d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#13 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fbef230f780 (LWP 2460)):
[KCrash Handler]
#6  DwHeaders::FindField (this=0x30, aFieldName=0x45eedf8 "X-KMail-Identity") at ../../mimelib/headers.cpp:314
#7  0x00007fbed3d47902 in KMMessage::headerField (this=0x44cad30, aName=<value optimized out>, encodingMode=KMMessage::MessageCharsetEncoding) at ../../kmail/kmmessage.cpp:1949
#8  0x00007fbed3d4ad54 in KMMessage::identityUoid (this=0x44cad30) at ../../kmail/kmmessage.cpp:1379
#9  0x00007fbed3d5b39b in KMMessage::createMDN (this=0x44cad30, a=KMime::MDN::ManualAction, d=KMime::MDN::Displayed, allowGUI=true, m=) at ../../kmail/kmmessage.cpp:1159
#10 0x00007fbed3e28a93 in KMReaderWin::slotTouchMessage (this=0x16f7530) at ../../kmail/kmreaderwin.cpp:1889
#11 0x00007fbed3e401b4 in KMReaderWin::qt_metacall (this=0x16f7530, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff58eb2ff0) at ./kmreaderwin.moc:210
#12 0x00007fbeefa71b27 in QMetaObject::activate (sender=0x16f7618, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x1) at kernel/qobject.cpp:3280
#13 0x00007fbeefa6b8f9 in QObject::event (this=0x16f7618, e=0x45eedf8) at kernel/qobject.cpp:1183
#14 0x00007fbef040ffdc in QApplicationPrivate::notify_helper (this=0x115ac70, receiver=0x16f7618, e=0x7fff58eb3740) at kernel/qapplication.cpp:4396
#15 0x00007fbef0415aed in QApplication::notify (this=0x7fff58eb3aa0, receiver=0x16f7618, e=0x7fff58eb3740) at kernel/qapplication.cpp:4277
#16 0x00007fbef1162156 in KApplication::notify (this=0x7fff58eb3aa0, receiver=0x16f7618, event=0x7fff58eb3740) at ../../kdeui/kernel/kapplication.cpp:310
#17 0x00007fbeefa59cdc in QCoreApplication::notifyInternal (this=0x7fff58eb3aa0, receiver=0x16f7618, event=0x7fff58eb3740) at kernel/qcoreapplication.cpp:732
#18 0x00007fbeefa896f2 in sendEvent (this=0x115e4b0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#19 QTimerInfoList::activateTimers (this=0x115e4b0) at kernel/qeventdispatcher_unix.cpp:602
#20 0x00007fbeefa864c8 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#21 idleTimerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:231
#22 0x00007fbee80b1342 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#23 0x00007fbee80b52a8 in ?? () from /lib/libglib-2.0.so.0
#24 0x00007fbee80b545c in g_main_context_iteration () from /lib/libglib-2.0.so.0
#25 0x00007fbeefa86193 in QEventDispatcherGlib::processEvents (this=0x1128e90, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:415
#26 0x00007fbef04c2a4e in QGuiEventDispatcherGlib::processEvents (this=0x30, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#27 0x00007fbeefa58a02 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#28 0x00007fbeefa58dec in QEventLoop::exec (this=0x7fff58eb39e0, flags=) at kernel/qeventloop.cpp:201
#29 0x00007fbeefa5cebb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#30 0x0000000000403b4e in main (argc=<value optimized out>, argv=<value optimized out>) at ../../../kontact/src/main.cpp:224

Reported using DrKonqi
Comment 1 Alexis Kauffmann 2010-11-10 21:09:20 UTC
After this report, Kontact has become unstable and has unexpectedly crashed 3 times by now for no apparent reason.
Comment 2 Dario Andres 2010-11-22 20:10:47 UTC
[Comment from a bug triager]
This issue is being tracked at bug 254750. Merging. Thanks

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