Bug 336162 - kmail crashed when trying to open a message from the outbox
Summary: kmail crashed when trying to open a message from the outbox
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.13
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2014-06-13 09:07 UTC by RJVB
Modified: 2017-01-07 22:38 UTC (History)
0 users

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 RJVB 2014-06-13 09:07:20 UTC
Application: kmail (4.13)
KDE Platform Version: 4.13.0
Qt Version: 4.8.6
Operating System: Linux 3.13.11.2-ck1-kubuntu-amdf10-rjvb x86_64
Distribution: Ubuntu 14.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:
I had cancelled a password dialog because I noticed that a message written after clicking on a mailto: link in my browser didn't have the desired From: address. In order to change that I tried to open the message from the outbox.
I got 1 or 2 errors about a missing .signature file, which I clicked away. I also probably double-clicked the message a 2nd time because of lack of progress feedback.

-- 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 0x7f1014add800 (LWP 12373))]

Thread 5 (Thread 0x7f0fec8f6700 (LWP 12377)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007f10063d581d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x00007f10063d5859 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x00007f100f70c182 in start_thread (arg=0x7f0fec8f6700) at pthread_create.c:312
#4  0x00007f1011e4b30d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 4 (Thread 0x7f0fab764700 (LWP 12378)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007f100611620d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x00007f1006404fd6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x00007f100f70c182 in start_thread (arg=0x7f0fab764700) at pthread_create.c:312
#4  0x00007f1011e4b30d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7f0faa89c700 (LWP 12379)):
#0  0x00007f1011e3c6bd in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f1009f0fc20 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f1009eceb14 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f1009ecef7b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f1009ecf0ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f10127da7be in QEventDispatcherGlib::processEvents (this=0x7f0f9c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#6  0x00007f10127ac0af in QEventLoop::processEvents (this=this@entry=0x7f0faa89bde0, flags=...) at kernel/qeventloop.cpp:149
#7  0x00007f10127ac3a5 in QEventLoop::exec (this=this@entry=0x7f0faa89bde0, flags=...) at kernel/qeventloop.cpp:204
#8  0x00007f10126a8c5f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:537
#9  0x00007f10126ab32f in QThreadPrivate::start (arg=0x251b000) at thread/qthread_unix.cpp:349
#10 0x00007f100f70c182 in start_thread (arg=0x7f0faa89c700) at pthread_create.c:312
#11 0x00007f1011e4b30d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7f0f98f9d700 (LWP 12626)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007f0ffc3eeffb in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#2  0x00007f0ffc3ef039 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#3  0x00007f100f70c182 in start_thread (arg=0x7f0f98f9d700) at pthread_create.c:312
#4  0x00007f1011e4b30d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f1014add800 (LWP 12373)):
[KCrash Handler]
#6  QMutex::lock (this=this@entry=0x680073002f00ba) at thread/qmutex.cpp:150
#7  0x00007f10127b1139 in QCoreApplication::postEvent (receiver=0x39de950, event=0x701e6e0, priority=0) at kernel/qcoreapplication.cpp:1358
#8  0x00007f10127c187a in QMetaObject::activate (sender=sender@entry=0x39de950, m=m@entry=0x7f1013c173e0 <KMCommand::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fffd5c9f570) at kernel/qobject.cpp:3539
#9  0x00007f101397c95e in KMCommand::messagesTransfered (this=this@entry=0x39de950, _t1=_t1@entry=KMCommand::OK) at moc_kmcommands.cpp:116
#10 0x00007f1013884f33 in KMCommand::slotJobFinished (this=0x39de950) at ../../kmail/kmcommands.cpp:367
#11 0x00007f10127c187a in QMetaObject::activate (sender=sender@entry=0x5a7d840, m=m@entry=0x7f10142e9600 <KJob::staticMetaObject>, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7fffd5c9f710) at kernel/qobject.cpp:3539
#12 0x00007f1013f59622 in KJob::result (this=this@entry=0x5a7d840, _t1=_t1@entry=0x5a7d840) at ./kjob.moc:207
#13 0x00007f1013f59660 in KJob::emitResult (this=0x5a7d840) at ../../kdecore/jobs/kjob.cpp:318
#14 0x00007f10127c5c1e in QObject::event (this=0x5a7d840, e=<optimized out>) at kernel/qobject.cpp:1194
#15 0x00007f1012cdee2c in QApplicationPrivate::notify_helper (this=this@entry=0x1e25aa0, receiver=receiver@entry=0x5a7d840, e=e@entry=0x68316e0) at kernel/qapplication.cpp:4567
#16 0x00007f1012ce54a0 in QApplication::notify (this=this@entry=0x7fffd5ca00f0, receiver=receiver@entry=0x5a7d840, e=e@entry=0x68316e0) at kernel/qapplication.cpp:4353
#17 0x00007f1014519baa in KApplication::notify (this=0x7fffd5ca00f0, receiver=0x5a7d840, event=0x68316e0) at ../../kdeui/kernel/kapplication.cpp:311
#18 0x00007f10127ad4dd in QCoreApplication::notifyInternal (this=0x7fffd5ca00f0, receiver=receiver@entry=0x5a7d840, event=event@entry=0x68316e0) at kernel/qcoreapplication.cpp:953
#19 0x00007f10127b0b3d in sendEvent (event=0x68316e0, receiver=0x5a7d840) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#20 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x1db8220) at kernel/qcoreapplication.cpp:1577
#21 0x00007f10127b0fe3 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1470
#22 0x00007f10127daf83 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#23 postEventSourceDispatch (s=0x1e3fd00) at kernel/qeventdispatcher_glib.cpp:287
#24 0x00007f1009ecee04 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x00007f1009ecf048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x00007f1009ecf0ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x00007f10127da7a1 in QEventDispatcherGlib::processEvents (this=0x1e27d60, flags=...) at kernel/qeventdispatcher_glib.cpp:434
#28 0x00007f1012d80bb6 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#29 0x00007f10127ac0af in QEventLoop::processEvents (this=this@entry=0x7fffd5c9fd40, flags=...) at kernel/qeventloop.cpp:149
#30 0x00007f10127ac3a5 in QEventLoop::exec (this=this@entry=0x7fffd5c9fd40, flags=...) at kernel/qeventloop.cpp:204
#31 0x00007f10127b1b79 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225
#32 0x00007f1012cdd37c in QApplication::exec () at kernel/qapplication.cpp:3828
#33 0x0000000000402d18 in main (argc=<optimized out>, argv=<optimized out>) at ../../kmail/main.cpp:146

Reported using DrKonqi
Comment 1 Denis Kurz 2016-09-24 17:55:51 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:38:29 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.