Application: kmail (4.14.2) KDE Platform Version: 4.14.2 Qt Version: 4.8.6 Operating System: Linux 3.16-2-amd64 x86_64 Distribution: Debian GNU/Linux unstable (sid) -- Information about the crash: - What I was doing when the application crashed: I tryed to send a mail with a rich html signature. It contains <html><body></body></html> with html5 balises inside. - Custom settings of the application: Content-type was changed via kmail: multipart/alternative. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f70a7918800 (LWP 4520))] Thread 6 (Thread 0x7f707eff4700 (LWP 4523)): #0 0x00007f70a4bd418d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x00007f709c8b8ee4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f709c8b8ffc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f70a5576507 in QEventDispatcherGlib::processEvents (this=0x7f70780008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x00007f70a5545ae1 in QEventLoop::processEvents (this=this@entry=0x7f707eff3d80, flags=...) at kernel/qeventloop.cpp:149 #5 0x00007f70a5545e45 in QEventLoop::exec (this=this@entry=0x7f707eff3d80, flags=...) at kernel/qeventloop.cpp:204 #6 0x00007f70a543ab89 in QThread::exec (this=this@entry=0x21be580) at thread/qthread.cpp:538 #7 0x00007f70a5526483 in QInotifyFileSystemWatcherEngine::run (this=0x21be580) at io/qfilesystemwatcher_inotify.cpp:265 #8 0x00007f70a543d3ef in QThreadPrivate::start (arg=0x21be580) at thread/qthread_unix.cpp:349 #9 0x00007f70a24920a4 in start_thread (arg=0x7f707eff4700) at pthread_create.c:309 #10 0x00007f70a4bdcccd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 5 (Thread 0x7f707d04e700 (LWP 4535)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007f7098f8106f in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x00007f7098f810a9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x00007f70a24920a4 in start_thread (arg=0x7f707d04e700) at pthread_create.c:309 #4 0x00007f70a4bdcccd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 4 (Thread 0x7f7037dd8700 (LWP 4536)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007f7098ca3973 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x00007f7098fb07f6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x00007f70a24920a4 in start_thread (arg=0x7f7037dd8700) at pthread_create.c:309 #4 0x00007f70a4bdcccd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 3 (Thread 0x7f70371d7700 (LWP 4537)): #0 0x00007f70a4bd418d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x00007f709c8b8ee4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f709c8b8ffc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f70a5576507 in QEventDispatcherGlib::processEvents (this=0x7f70280008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x00007f70a5545ae1 in QEventLoop::processEvents (this=this@entry=0x7f70371d6dd0, flags=...) at kernel/qeventloop.cpp:149 #5 0x00007f70a5545e45 in QEventLoop::exec (this=this@entry=0x7f70371d6dd0, flags=...) at kernel/qeventloop.cpp:204 #6 0x00007f70a543ab89 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:538 #7 0x00007f70a543d3ef in QThreadPrivate::start (arg=0x27e8450) at thread/qthread_unix.cpp:349 #8 0x00007f70a24920a4 in start_thread (arg=0x7f70371d7700) at pthread_create.c:309 #9 0x00007f70a4bdcccd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 2 (Thread 0x7f7035062700 (LWP 4540)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007f708fad6afa in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #2 0x00007f708fad6b29 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #3 0x00007f70a24920a4 in start_thread (arg=0x7f7035062700) at pthread_create.c:309 #4 0x00007f70a4bdcccd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7f70a7918800 (LWP 4520)): [KCrash Handler] #6 QByteArray::indexOf (this=<optimized out>, ch=47 '/', from=<optimized out>) at tools/qbytearray.cpp:2314 #7 0x00007f70a1711012 in KMime::Headers::ContentType::isSubtype(char const*) const () from /usr/lib/libkmime.so.4 #8 0x00007f70a16e5414 in KMime::isSigned(KMime::Message*) () from /usr/lib/libkmime.so.4 #9 0x00007f709f72d568 in MailTransport::MessageQueueJob::Private::outboxRequestResult(KJob*) () from /usr/lib/libmailtransport.so.4 #10 0x00007f70a555bf4c in QMetaObject::activate (sender=sender@entry=0x3da00d0, m=m@entry=0x7f70a710bee0 <KJob::staticMetaObject>, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7fff76a94140) at kernel/qobject.cpp:3567 #11 0x00007f70a6d6b072 in KJob::result (this=this@entry=0x3da00d0, _t1=_t1@entry=0x3da00d0) at ./kjob.moc:207 #12 0x00007f70a6d6b0c0 in KJob::emitResult (this=0x3da00d0) at ../../kdecore/jobs/kjob.cpp:318 #13 0x00007f70a13414a0 in ?? () from /usr/lib/libakonadi-kde.so.4 #14 0x00007f70a1395589 in ?? () from /usr/lib/libakonadi-kde.so.4 #15 0x00007f70a1395cad in ?? () from /usr/lib/libakonadi-kde.so.4 #16 0x00007f70a5560641 in QObject::event (this=0x1eeda60, e=<optimized out>) at kernel/qobject.cpp:1222 #17 0x00007f70a5a7729c in QApplicationPrivate::notify_helper (this=this@entry=0x1cbe530, receiver=receiver@entry=0x1eeda60, e=e@entry=0x4ea8e30) at kernel/qapplication.cpp:4570 #18 0x00007f70a5a7dda8 in QApplication::notify (this=this@entry=0x7fff76a94bd0, receiver=receiver@entry=0x1eeda60, e=e@entry=0x4ea8e30) at kernel/qapplication.cpp:4356 #19 0x00007f70a736c09a in KApplication::notify (this=0x7fff76a94bd0, receiver=0x1eeda60, event=0x4ea8e30) at ../../kdeui/kernel/kapplication.cpp:311 #20 0x00007f70a5546f8d in QCoreApplication::notifyInternal (this=0x7fff76a94bd0, receiver=receiver@entry=0x1eeda60, event=event@entry=0x4ea8e30) at kernel/qcoreapplication.cpp:955 #21 0x00007f70a554a821 in sendEvent (event=0x4ea8e30, receiver=0x1eeda60) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #22 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x1c15220) at kernel/qcoreapplication.cpp:1579 #23 0x00007f70a554acb3 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1472 #24 0x00007f70a55763a3 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236 #25 postEventSourceDispatch (s=0x1ca24b0) at kernel/qeventdispatcher_glib.cpp:280 #26 0x00007f709c8b8c5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x00007f709c8b8f48 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x00007f709c8b8ffc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x00007f70a55764ed in QEventDispatcherGlib::processEvents (this=0x1c16b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #30 0x00007f70a5b1bb96 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #31 0x00007f70a5545ae1 in QEventLoop::processEvents (this=this@entry=0x7fff76a94810, flags=...) at kernel/qeventloop.cpp:149 #32 0x00007f70a5545e45 in QEventLoop::exec (this=this@entry=0x7fff76a94810, flags=...) at kernel/qeventloop.cpp:204 #33 0x00007f70a554b8b9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1227 #34 0x0000000000402d9b in ?? () #35 0x00007f70a4b18b45 in __libc_start_main (main=0x4022f0, argc=3, argv=0x7fff76a94df8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff76a94de8) at libc-start.c:287 #36 0x0000000000403274 in _start () Reported using DrKonqi
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12, preferably more recent), please open a new one unless it already exists. Thank you for all your input.