Bug 308884 - Cancel decryption crashed KMail
Summary: Cancel decryption crashed KMail
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 323916 324009 327499 329734 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-10-23 15:15 UTC by Martin Flöser
Modified: 2017-01-07 22:35 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (7.42 KB, text/plain)
2014-01-13 20:27 UTC, chooligan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Flöser 2012-10-23 15:15:35 UTC
Application: kmail (4.10 pre)
KDE Platform Version: 4.9.80 (Compiled from sources)
Qt Version: 4.8.2
Operating System: Linux 3.2.0-3-amd64 x86_64
Distribution: Debian GNU/Linux testing (wheezy)

-- Information about the crash:
- What I was doing when the application crashed:

1. Deleted top most mail of folder
2. Selection moved to a PGP encrypted mail
3. Canceled dialog to decrypt mail

Actual Behavior:
crash

Expected Behavior:
no crash

I have not yet tried to reproduce as DrKonqui does not allow to start KMail.

Current state of software (I can upgrade if wished):
kdepimlibs: 6e5ec381d10e2f6dd5f8d5e667e1752baca30f7c
kdepim: 4f79545fdbf49d04fe8efdd8d53b28a966a98b5c
kdepim-runtime: 2bf2e32434a2e5ac10d76fffb2ecf158bedaf793
akonadi: 6a6122e1fe58e5404652c4c8909d42150b4ede3b

-- 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 0x7f8cb2a2c780 (LWP 4912))]

Thread 3 (Thread 0x7f8c8e4d9700 (LWP 4984)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007f8ca4e8ec0d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x00007f8ca4e8ed19 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x00007f8cad001b50 in start_thread (arg=<optimized out>) at pthread_create.c:304
#4  0x00007f8cac05070d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f8c8dbd8700 (LWP 4985)):
#0  0x00007f8cac045ac3 in *__GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=2890) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f8ca0e644d4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f8ca0e645f4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f8cad3c2296 in QEventDispatcherGlib::processEvents (this=0x27d31d0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x00007f8cad3928af in QEventLoop::processEvents (this=this@entry=0x7f8c8dbd7e20, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f8cad392b38 in QEventLoop::exec (this=0x7f8c8dbd7e20, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007f8cad295d70 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#7  0x00007f8cad298d0b in QThreadPrivate::start (arg=0x27d2870) at thread/qthread_unix.cpp:307
#8  0x00007f8cad001b50 in start_thread (arg=<optimized out>) at pthread_create.c:304
#9  0x00007f8cac05070d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#10 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f8cb2a2c780 (LWP 4912)):
[KCrash Handler]
#6  KMime::Content::contents (this=0x31) at /home/martin/kde/src/kde/kdepimlibs/kmime/kmime_content.cpp:526
#7  0x00007f8ca8844ada in MessageCore::NodeHelper::nextSibling (node=0x209b1780) at /home/martin/kde/src/kde/kdepim/messagecore/nodehelper.cpp:34
#8  0x00007f8ca5b16d64 in MessageViewer::ObjectTreeParser::parseObjectTreeInternal (this=this@entry=0x7fffdd329500, node=node@entry=0x209b1780) at /home/martin/kde/src/kde/kdepim/messageviewer/objecttreeparser.cpp:296
#9  0x00007f8ca5b17617 in MessageViewer::ObjectTreeParser::stdChildHandling (this=this@entry=0x7fffdd329770, child=0x209b1780) at /home/martin/kde/src/kde/kdepim/messageviewer/objecttreeparser.cpp:1452
#10 0x00007f8ca5b17a32 in processMultiPartMixedSubtype (node=0x1fccb800, this=0x7fffdd329770) at /home/martin/kde/src/kde/kdepim/messageviewer/objecttreeparser.cpp:1485
#11 MessageViewer::ObjectTreeParser::processMultiPartMixedSubtype (this=0x7fffdd329770, node=0x1fccb800) at /home/martin/kde/src/kde/kdepim/messageviewer/objecttreeparser.cpp:1474
#12 0x00007f8ca5b1701b in MessageViewer::ObjectTreeParser::parseObjectTreeInternal (this=0x7fffdd329770, node=0x1fccb800) at /home/martin/kde/src/kde/kdepim/messageviewer/objecttreeparser.cpp:353
#13 0x00007f8ca5b4b8b0 in MessageViewer::ViewerPrivate::parseContent (this=this@entry=0x27b7a80, content=0x1fccb800) at /home/martin/kde/src/kde/kdepim/messageviewer/viewer_p.cpp:991
#14 0x00007f8ca5b4d0ec in MessageViewer::ViewerPrivate::displayMessage (this=this@entry=0x27b7a80) at /home/martin/kde/src/kde/kdepim/messageviewer/viewer_p.cpp:863
#15 0x00007f8ca5b4d606 in MessageViewer::ViewerPrivate::updateReaderWin (this=0x27b7a80) at /home/martin/kde/src/kde/kdepim/messageviewer/viewer_p.cpp:2214
#16 0x00007f8ca5b5034a in MessageViewer::ViewerPrivate::qt_static_metacall (_o=0x27b7a80, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at /home/martin/kde/build/kde/kdepim/messageviewer/viewer_p.moc:231
#17 0x00007f8cad3a954f in QMetaObject::activate (sender=0x27b7b10, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3547
#18 0x00007f8cad3a885c in QObject::event (this=0x27b7b10, e=<optimized out>) at kernel/qobject.cpp:1157
#19 0x00007f8cadd9d70c in QApplicationPrivate::notify_helper (this=this@entry=0x1ef38f0, receiver=receiver@entry=0x27b7b10, e=e@entry=0x7fffdd32a1a0) at kernel/qapplication.cpp:4556
#20 0x00007f8cadda1b8a in QApplication::notify (this=0x7fffdd32a790, receiver=0x27b7b10, e=0x7fffdd32a1a0) at kernel/qapplication.cpp:4417
#21 0x00007f8cb2455f66 in KApplication::notify (this=0x7fffdd32a790, receiver=0x27b7b10, event=0x7fffdd32a1a0) at /home/martin/kde/src/kde/kdelibs/kdeui/kernel/kapplication.cpp:311
#22 0x00007f8cad393b5e in QCoreApplication::notifyInternal (this=0x7fffdd32a790, receiver=0x27b7b10, event=0x7fffdd32a1a0) at kernel/qcoreapplication.cpp:915
#23 0x00007f8cad3c4a52 in sendEvent (event=0x7fffdd32a1a0, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#24 QTimerInfoList::activateTimers (this=0x1e62fb0) at kernel/qeventdispatcher_unix.cpp:611
#25 0x00007f8cad3c1c04 in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:186
#26 timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:180
#27 0x00007f8ca0e64205 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x00007f8ca0e64538 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x00007f8ca0e645f4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#30 0x00007f8cad3c2276 in QEventDispatcherGlib::processEvents (this=0x1dd2ad0, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#31 0x00007f8cade3e83e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#32 0x00007f8cad3928af in QEventLoop::processEvents (this=this@entry=0x7fffdd32a410, flags=...) at kernel/qeventloop.cpp:149
#33 0x00007f8cad392b38 in QEventLoop::exec (this=0x7fffdd32a410, flags=...) at kernel/qeventloop.cpp:204
#34 0x00007f8cad397cf8 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187
#35 0x0000000000403082 in main (argc=<optimized out>, argv=<optimized out>) at /home/martin/kde/src/kde/kdepim/kmail/main.cpp:148

Reported using DrKonqi
Comment 1 Martin Flöser 2012-10-23 15:17:54 UTC
Just tried to reproduce - no crash, maybe the deleting of message before is relevant
Comment 2 Laurent Montel 2012-10-24 06:51:08 UTC
I already saw this BT but never can reproduce it too.
I add it to my todo :)
Regards
Comment 3 Martin Flöser 2012-10-24 14:54:59 UTC
I found a further way to reproduce it (randomly) by just switching mail 
folders when in the folder one switches to the selected mail is the encrypted 
one.
Comment 4 Jekyll Wu 2013-08-25 16:41:51 UTC
*** Bug 324009 has been marked as a duplicate of this bug. ***
Comment 5 Jekyll Wu 2014-01-09 04:53:53 UTC
*** Bug 329734 has been marked as a duplicate of this bug. ***
Comment 6 Jekyll Wu 2014-01-09 04:54:01 UTC
*** Bug 327499 has been marked as a duplicate of this bug. ***
Comment 7 Jekyll Wu 2014-01-09 04:55:50 UTC
*** Bug 323916 has been marked as a duplicate of this bug. ***
Comment 8 chooligan 2014-01-13 20:27:02 UTC
Created attachment 84630 [details]
New crash information added by DrKonqi

kontact (4.11.3) on KDE Platform 4.11.3 using Qt 4.8.4

- What I was doing when the application crashed:

Cancel decryption crashed KMail.
Each time I cancel decryption e-mail (various e-mail account) KMail crashed.

-- Backtrace (Reduced):
#6  KMime::Content::contents (this=0x51) at ../../kmime/kmime_content.cpp:528
#7  0x00007f705930781e in MessageCore::NodeHelper::nextSibling (node=node@entry=0x1d5de00) at ../../messagecore/helpers/nodehelper.cpp:34
#8  0x00007f70578cdf2f in MessageViewer::ObjectTreeParser::parseObjectTreeInternal (this=this@entry=0x7fff1d8c57c0, node=node@entry=0x1d5de00) at ../../messageviewer/viewer/objecttreeparser.cpp:296
#9  0x00007f70578cfa19 in MessageViewer::ObjectTreeParser::parseObjectTree (this=this@entry=0x7fff1d8c57c0, node=node@entry=0x1d5de00) at ../../messageviewer/viewer/objecttreeparser.cpp:266
#10 0x00007f70578fbc68 in MessageViewer::ViewerPrivate::parseContent (this=this@entry=0x1b6c5e0, content=0x1d5de00) at ../../messageviewer/viewer/viewer_p.cpp:1007
Comment 9 Denis Kurz 2016-09-24 18:09:11 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 10 Denis Kurz 2017-01-07 22:35:02 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.