Bug 218973 - Kmail crashes after canceling a pinentry request (GPG decrypt)
Summary: Kmail crashes after canceling a pinentry request (GPG decrypt)
Status: RESOLVED DUPLICATE of bug 180741
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-16 19:56 UTC by Wes D
Modified: 2010-06-06 22:52 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wes D 2009-12-16 19:56:37 UTC
Application that crashed: kmail
Version of the application: 1.12.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-16-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
If my gpg key cache time expires and I switch mailboxes into a mailbox where the previously viewed email was encrypted using GPG, it will ask me for my private key password.  If I'm not interested in decrypting it, and instead want to view a different message, I hit "Cancel"; pinentry goes away.  It then shows a message showing that the email failed to decrypt, do I want to try again?  If I hit "cancel" at that point, Kmail will crash, 100%.

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[KCrash Handler]
#6  0x0146a957 in typeinfo for DwDispositionType () from /usr/lib/libmimelib.so.4
#7  0x00bdfea8 in KMReaderWin::parseMsg (this=0x9cb4a17, aMsg=0xbad3698) at ../../kmail/kmreaderwin.cpp:1678
#8  0x00bcd4d9 in KMReaderWin::displayMessage (this=0x9cb4a18) at ../../kmail/kmreaderwin.cpp:1605
#9  0x00bcd6cb in KMReaderWin::updateReaderWin (this=0x9cb4a18) at ../../kmail/kmreaderwin.cpp:1545
#10 0x00bd996b in KMReaderWin::setMsg (this=0x9cb4a18, aMsg=0xbad3698, force=true) at ../../kmail/kmreaderwin.cpp:1347
#11 0x00bda7cf in KMReaderWin::slotMessageArrived (this=0x9cb4a18, msg=0xbad3698) at ../../kmail/kmreaderwin.cpp:935
#12 0x00bdabdd in KMReaderWin::qt_metacall (this=0x9cb4a18, _c=QMetaObject::InvokeMetaMethod, _id=34, _a=0xbfaf0b28) at ./kmreaderwin.moc:196
#13 0x07582263 in QMetaObject::activate (sender=0xb1c5e90, from_signal_index=4, to_signal_index=4, argv=0xbfaf0b28) at kernel/qobject.cpp:3113
#14 0x07582ec2 in QMetaObject::activate (sender=0xb1c5e90, m=0x11d04d0, local_signal_index=0, argv=0xbfaf0b28) at kernel/qobject.cpp:3187
#15 0x00df5423 in KMail::FolderJob::messageRetrieved (this=0xb1c5e90, _t1=0xbad3698) at ./folderjob.moc:99
#16 0x00e01ec4 in KMail::ImapJob::slotGetMessageResult (this=0xb1c5e90, job=0xa7bc190) at ../../kmail/imapjob.cpp:460
#17 0x00e0660f in KMail::ImapJob::qt_metacall (this=0xb1c5e90, _c=QMetaObject::InvokeMetaMethod, _id=12, _a=0xbfaf0cc8) at ./imapjob.moc:82
#18 0x07582263 in QMetaObject::activate (sender=0xa7bc190, from_signal_index=7, to_signal_index=7, argv=0xbfaf0cc8) at kernel/qobject.cpp:3113
#19 0x07582ec2 in QMetaObject::activate (sender=0xa7bc190, m=0x34fd68, local_signal_index=3, argv=0xbfaf0cc8) at kernel/qobject.cpp:3187
#20 0x001e9fe3 in KJob::result (this=0xa7bc190, _t1=0xa7bc190) at ./kjob.moc:188
#21 0x001ea469 in KJob::emitResult (this=0xa7bc190) at ../../kdecore/jobs/kjob.cpp:304
#22 0x0164f660 in KIO::SimpleJob::slotFinished (this=0xa7bc190) at ../../kio/kio/job.cpp:477
#23 0x0164fb7a in KIO::TransferJob::slotFinished (this=0xa7bc190) at ../../kio/kio/job.cpp:948
#24 0x0164d8a3 in KIO::TransferJob::qt_metacall (this=0xa7bc190, _c=QMetaObject::InvokeMetaMethod, _id=47, _a=0xbfaf0f2c) at ./jobclasses.moc:343
#25 0x07582263 in QMetaObject::activate (sender=0xa091098, from_signal_index=8, to_signal_index=8, argv=0x0) at kernel/qobject.cpp:3113
#26 0x07582ec2 in QMetaObject::activate (sender=0xa091098, m=0x1801f64, local_signal_index=4, argv=0x0) at kernel/qobject.cpp:3187
#27 0x01719557 in KIO::SlaveInterface::finished (this=0xa091098) at ./slaveinterface.moc:165
#28 0x0171d44d in KIO::SlaveInterface::dispatch (this=0xa091098, _cmd=104, rawdata=...) at ../../kio/kio/slaveinterface.cpp:175
#29 0x01719a13 in KIO::SlaveInterface::dispatch (this=0xa091098) at ../../kio/kio/slaveinterface.cpp:91
#30 0x0170baea in KIO::Slave::gotInput (this=0xa091098) at ../../kio/kio/slave.cpp:322
#31 0x0170dee3 in KIO::Slave::qt_metacall (this=0xa091098, _c=QMetaObject::InvokeMetaMethod, _id=30, _a=0xbfaf120c) at ./slave.moc:76
#32 0x07582263 in QMetaObject::activate (sender=0xa092310, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113
#33 0x07582ec2 in QMetaObject::activate (sender=0xa092310, m=0x17fe8a0, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187
#34 0x01615f97 in KIO::Connection::readyRead (this=0xa092310) at ./connection.moc:86
#35 0x01617d5e in KIO::ConnectionPrivate::dequeue (this=0xa092388) at ../../kio/kio/connection.cpp:82
#36 0x01617e8e in KIO::Connection::qt_metacall (this=0xa092310, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xb4528c0) at ./connection.moc:73
#37 0x0757af0b in QMetaCallEvent::placeMetaCall (this=0xa2d0ac0, object=0xa092310) at kernel/qobject.cpp:477
#38 0x0757c5fe in QObject::event (this=0xa092310, e=0xa2d0ac0) at kernel/qobject.cpp:1111
#39 0x0669cf54 in QApplicationPrivate::notify_helper (this=0x99c27b8, receiver=0xa092310, e=0xa2d0ac0) at kernel/qapplication.cpp:4056
#40 0x066a467c in QApplication::notify (this=0xbfaf1b40, receiver=0xa092310, e=0xa2d0ac0) at kernel/qapplication.cpp:3603
#41 0x00873bfa in KApplication::notify (this=0xbfaf1b40, receiver=0xa092310, event=0xa2d0ac0) at ../../kdeui/kernel/kapplication.cpp:302
#42 0x0756c6cb in QCoreApplication::notifyInternal (this=0xbfaf1b40, receiver=0xa092310, event=0xa2d0ac0) at kernel/qcoreapplication.cpp:610
#43 0x0756d2b2 in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x990bfa8) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#44 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x990bfa8) at kernel/qcoreapplication.cpp:1247
#45 0x0756d47d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140
#46 0x075973ff in QCoreApplication::sendPostedEvents (s=0x9934278) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#47 postEventSourceDispatch (s=0x9934278) at kernel/qeventdispatcher_glib.cpp:210
#48 0x05271e78 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#49 0x05275720 in ?? () from /lib/libglib-2.0.so.0
#50 0x05275853 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#51 0x0759702c in QEventDispatcherGlib::processEvents (this=0x990c180, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#52 0x0673dbe5 in QGuiEventDispatcherGlib::processEvents (this=0x990c180, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#53 0x0756ac79 in QEventLoop::processEvents (this=0xbfaf1a04, flags=) at kernel/qeventloop.cpp:149
#54 0x0756b0ca in QEventLoop::exec (this=0xbfaf1a04, flags=...) at kernel/qeventloop.cpp:201
#55 0x0756d53f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#56 0x0669cdd7 in QApplication::exec () at kernel/qapplication.cpp:3525
#57 0x0804a702 in main (argc=3, argv=0xbfaf1cf4) at ../../kmail/main.cpp:146

Reported using DrKonqi
Comment 1 Dario Andres 2009-12-17 00:36:46 UTC
This looks like bug 180741. Can you check
https://bugs.kde.org/show_bug.cgi?id=180741#c41 ? Thanks
Comment 2 Wes D 2009-12-17 18:38:31 UTC
It's entirely possible.  If I disable the preview pane in Kmail prefs, the problem doesn't appear.  To clarify

-Disable preview pane
-Click on message that is GPG encrypted to my private key from a friend
-PINEntry window pops up
-I hit Cancel
-GPG Warning "Invalid Passphrase" pops up, from Kmail
-I hit Cancel
-Message window opens with standard blue markup and "Message could not be decrypted" as the message body.
-Kmail does *not* crash.

So it appears to be related to the preview pane, but I don't know enough about it to say if it's related explicitly to 180741 or 208245
Comment 3 Christophe Marin 2010-06-06 22:52:10 UTC

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