If you click an encrypted message then Kontact crashes when you do not input an key in the pinentry-dialog and then click on Cancel and then in the next Dialog click Cancel again. Reproducible: Always Steps to Reproduce: 1. Click on encrypted message 2. Click Cancel in pinentry dialog 3. Click Cancel again in Retry Dialog Actual Results: Kontact completely crashes. If you restart, the same message is shown, and you have to give the decryption pin, either you have the same effect Expected Results: Dialogs should be closed, work on like before, see the message undecrypted
Backtrace ?
Am Dienstag, 18. Juni 2013, 10:35:49 schrieben Sie: > https://bugs.kde.org/show_bug.cgi?id=321312 > > Laurent Montel <montel@kde.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |montel@kde.org > > --- Comment #1 from Laurent Montel <montel@kde.org> --- > Backtrace ? > > How can i do when the complete Desktop is frozen ?
Am Dienstag, 18. Juni 2013, 11:22:08 schrieben Sie: > https://bugs.kde.org/show_bug.cgi?id=321312 > > --- Comment #2 from Wolfgang Schindler <schindler@schintech.net> --- > Am Dienstag, 18. Juni 2013, 10:35:49 schrieben Sie: > > https://bugs.kde.org/show_bug.cgi?id=321312 > > > > Laurent Montel <montel@kde.org> changed: > > > > What |Removed |Added > > ---------------------------------------------------------------------------- > > CC| |montel@kde.org > > > > --- Comment #1 from Laurent Montel <montel@kde.org> --- > > Backtrace ? > > > > > > How can i do when the complete Desktop is frozen ? > > Excuse me, wrong bug-report, waiting for the key getting ineffective
Am Dienstag, 18. Juni 2013, 11:24:05 schrieben Sie: > https://bugs.kde.org/show_bug.cgi?id=321312 > > --- Comment #3 from Wolfgang Schindler <schindler@schintech.net> --- > Am Dienstag, 18. Juni 2013, 11:22:08 schrieben Sie: > > https://bugs.kde.org/show_bug.cgi?id=321312 > > > > --- Comment #2 from Wolfgang Schindler <schindler@schintech.net> --- > > Am Dienstag, 18. Juni 2013, 10:35:49 schrieben Sie: > > > https://bugs.kde.org/show_bug.cgi?id=321312 > > > > > > Laurent Montel <montel@kde.org> changed: > > > > > > What |Removed |Added > > > ---------------------------------------------------------------------------- > > > CC| |montel@kde.org > > > > > > --- Comment #1 from Laurent Montel <montel@kde.org> --- > > > Backtrace ? > > > > > > > > > > How can i do when the complete Desktop is frozen ? > > > > > > Excuse me, wrong bug-report, waiting for the key getting ineffective > > Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f46ea6df780 (LWP 535))] Thread 3 (Thread 0x7f46cec70700 (LWP 536)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007f46e6f29ebd in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x00007f46e6f29fc9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x00007f46e20c2e0e in start_thread (arg=0x7f46cec70700) at pthread_create.c:311 #4 0x00007f46e7c4c95d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 2 (Thread 0x7f46ce36f700 (LWP 537)): #0 0x00007f46e7c411bd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x00007f46e17f706c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f46e17f7194 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f46e9063d06 in QEventDispatcherGlib::processEvents (this=0x7f46c80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x00007f46e90340ff in QEventLoop::processEvents (this=this@entry=0x7f46ce36ee00, flags=...) at kernel/qeventloop.cpp:149 #5 0x00007f46e9034388 in QEventLoop::exec (this=this@entry=0x7f46ce36ee00, flags=...) at kernel/qeventloop.cpp:204 #6 0x00007f46e8f36390 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:542 #7 0x00007f46e8f38b6c in QThreadPrivate::start (arg=0xf12100) at thread/qthread_unix.cpp:338 #8 0x00007f46e20c2e0e in start_thread (arg=0x7f46ce36f700) at pthread_create.c:311 #9 0x00007f46e7c4c95d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 1 (Thread 0x7f46ea6df780 (LWP 535)): [KCrash Handler] #6 0x00007f46dee83d84 in KMime::Content::parent (this=this@entry=0x1db3be0) at ../../kmime/kmime_content.cpp:952 #7 0x00007f4685262146 in MessageCore::NodeHelper::nextSibling (node=node@entry=0x1db3be0) at ../../messagecore/nodehelper.cpp:32 #8 0x00007f46838ce9a4 in MessageViewer::ObjectTreeParser::parseObjectTreeInternal (this=this@entry=0x7fff9388d7f0, node=node@entry=0x1db3be0) at ../../messageviewer/objecttreeparser.cpp:296 #9 0x00007f46838cf679 in MessageViewer::ObjectTreeParser::parseObjectTree (this=this@entry=0x7fff9388d7f0, node=node@entry=0x1db3be0) at ../../messageviewer/objecttreeparser.cpp:266 #10 0x00007f46839025e0 in MessageViewer::ViewerPrivate::parseContent (this=this@entry=0x1485550, content=0x1db3be0) at ../../messageviewer/viewer_p.cpp:974 #11 0x00007f46839048cc in MessageViewer::ViewerPrivate::displayMessage (this=this@entry=0x1485550) at ../../messageviewer/viewer_p.cpp:846 #12 0x00007f4683904de6 in MessageViewer::ViewerPrivate::updateReaderWin (this=0x1485550) at ../../messageviewer/viewer_p.cpp:2185 #13 0x00007f4683907c1a in MessageViewer::ViewerPrivate::qt_static_metacall (_o=0x1485550, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at ./viewer_p.moc:234 #14 0x00007f46e9049dcf in QMetaObject::activate (sender=0x14855e0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3539 #15 0x00007f46e904f0cc in QObject::event (this=0x14855e0, e=<optimized out>) at kernel/qobject.cpp:1156 #16 0x00007f46e83e30ec in QApplicationPrivate::notify_helper (this=this@entry=0xcdaab0, receiver=receiver@entry=0x14855e0, e=e@entry=0x7fff9388e220) at kernel/qapplication.cpp:4567 #17 0x00007f46e83e5a5b in QApplication::notify (this=this@entry=0x7fff9388e620, receiver=receiver@entry=0x14855e0, e=e@entry=0x7fff9388e220) at kernel/qapplication.cpp:4428 #18 0x00007f46e9ab15e6 in KApplication::notify (this=0x7fff9388e620, receiver=0x14855e0, event=0x7fff9388e220) at ../../kdeui/kernel/kapplication.cpp:311 #19 0x00007f46e90353ae in QCoreApplication::notifyInternal (this=0x7fff9388e620, receiver=0x14855e0, event=event@entry=0x7fff9388e220) at kernel/qcoreapplication.cpp:946 #20 0x00007f46e9066842 in sendEvent (event=0x7fff9388e220, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #21 QTimerInfoList::activateTimers (this=0xccbb80) at kernel/qeventdispatcher_unix.cpp:622 #22 0x00007f46e9063674 in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:186 #23 timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:180 #24 0x00007f46e17f6d95 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x00007f46e17f70d8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x00007f46e17f7194 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x00007f46e9063ce6 in QEventDispatcherGlib::processEvents (this=0xc94b00, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #28 0x00007f46e8484f9e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #29 0x00007f46e90340ff in QEventLoop::processEvents (this=this@entry=0x7fff9388e490, flags=...) at kernel/qeventloop.cpp:149 #30 0x00007f46e9034388 in QEventLoop::exec (this=this@entry=0x7fff9388e490, flags=...) at kernel/qeventloop.cpp:204 #31 0x00007f46e9039a66 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1218 #32 0x00007f46e83e1a5c in QApplication::exec () at kernel/qapplication.cpp:3828 #33 0x00000000004033a9 in main (argc=1, argv=0x7fff9388e768) at ../../../kontact/src/main.cpp:219
we need to know, what kind of encrypted mail you look at S/MIME, PGP Mime or Inline.
It's PGP
I can't reproduce it with KDE/4.11: Steps I tried: 1. Click on encrypted message (PGP Mime) 2. Click Cancel in pinentry dialog 3. Click Cancel again in Retry Dialog Happens this to every encrypted message?
Yes, it does with every encrypted message. Encrypted with GnuPG Versions 1.4.14, 2.0.19 and 1.4.6 Please try several times. Kmail 4.10.5-1 started from kontact 4.10.5 on kubuntu 12.04 with actual software on my laptop Same on aptosid 2013-01 with actual software on my desktop Thanks for your precious time
Hi there, tried the whole thing with opensuse 12.3 and chakra running in virtual machines. No problem occurred with those distributions as you pointed out before. So it seems to be a problem with debian based distributions. Checked the versions of pinentry, they all were 0.8.1, so now what? cheers and remind me of paying you some beers somewhere someday