Bug 202115 - Cancel on pinentry (gpg) occasionally crashes
Summary: Cancel on pinentry (gpg) occasionally crashes
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 204445 210649 238358 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-07-31 18:07 UTC by Wes D
Modified: 2012-08-19 10:54 UTC (History)
4 users (show)

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 Wes D 2009-07-31 18:07:37 UTC
Version:            (using KDE 4.2.2)
OS:                Linux
Installed from:    Ubuntu Packages

When receiving an encrypted message, KMail prompts for your GPG passphrase via the pinentry window.  If the last opened message on an IMAP server (haven't tested POP3) was GPG encrypted, it prompts for the PIN.  When I'm not interested in entering the password or viewing that particular message, I'll hit cancel.  I then get a decryption failure notice, and hit cancel again.

Sometimes (50% of the time, or so) hitting cancel the first time causes KMail to crash.  Almost 100% of the time if pinentry runs a second time and I hit cancel *at any time after that point*, Kmail/Kontact will crash.


Application: Kontact (kontact), signal SIGSEGV

Thread 1 (Thread 0xb481f700 (LWP 12007)):
[KCrash Handler]
#6  0x08f1b0d8 in ?? ()
#7  0xb10167a8 in KMReaderWin::displayMessage (this=0x8f4ef10) at /build/buildd/kdepim-4.2.2/kmail/kmreaderwin.cpp:1555
#8  0xb10169d0 in KMReaderWin::updateReaderWin (this=0x8f121c0) at /build/buildd/kdepim-4.2.2/kmail/kmreaderwin.cpp:1495
#9  0xb1024059 in KMReaderWin::setMsg (this=0x8f121c0, aMsg=0xb4ef060, force=true) at /build/buildd/kdepim-4.2.2/kmail/kmreaderwin.cpp:1297
#10 0xb1024fa7 in KMReaderWin::slotMessageArrived (this=0x8f121c0, msg=0xb4ef060) at /build/buildd/kdepim-4.2.2/kmail/kmreaderwin.cpp:907
#11 0xb10252aa in KMReaderWin::qt_metacall (this=0x8f121c0, _c=QMetaObject::InvokeMetaMethod, _id=34, _a=0xbfa0656c) at /build/buildd/kdepim-4.2.2/obj-i486-linux-gnu/kmail/kmreaderwin.moc:193
#12 0xb5c18ca8 in QMetaObject::activate (sender=0xb4cd6e8, from_signal_index=4, to_signal_index=4, argv=0xbfa0656c) at kernel/qobject.cpp:3069
#13 0xb5c19932 in QMetaObject::activate (sender=0xb4cd6e8, m=0xb1679850, local_signal_index=0, argv=0xbfa0656c) at kernel/qobject.cpp:3143
#14 0xb1258553 in KMail::FolderJob::messageRetrieved (this=0xb4cd6e8, _t1=0xb4ef060) at /build/buildd/kdepim-4.2.2/obj-i486-linux-gnu/kmail/folderjob.moc:99
#15 0xb1266527 in KMail::ImapJob::slotGetMessageResult (this=0xb4cd6e8, job=0xaa7c030) at /build/buildd/kdepim-4.2.2/kmail/imapjob.cpp:460
#16 0xb126b024 in KMail::ImapJob::qt_metacall (this=0xb4cd6e8, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfa066ec) at /build/buildd/kdepim-4.2.2/obj-i486-linux-gnu/kmail/imapjob.moc:82
#17 0xb5c18ca8 in QMetaObject::activate (sender=0xaa7c030, from_signal_index=7, to_signal_index=7, argv=0xbfa066ec) at kernel/qobject.cpp:3069
#18 0xb5c19932 in QMetaObject::activate (sender=0xaa7c030, m=0xb5f8af08, local_signal_index=3, argv=0xbfa066ec) at kernel/qobject.cpp:3143
#19 0xb5e3c883 in KJob::result (this=0xaa7c030, _t1=0xaa7c030) at /build/buildd/kde4libs-4.2.2/obj-i486-linux-gnu/kdecore/kjob.moc:188
#20 0xb5e3cd29 in KJob::emitResult (this=0xaa7c030) at /build/buildd/kde4libs-4.2.2/kdecore/jobs/kjob.cpp:294
#21 0xb6f65ab5 in KIO::SimpleJob::slotFinished (this=0xaa7c030) at /build/buildd/kde4libs-4.2.2/kio/kio/job.cpp:489
#22 0xb6f66d23 in KIO::TransferJob::slotFinished (this=0xaa7c030) at /build/buildd/kde4libs-4.2.2/kio/kio/job.cpp:966
#23 0xb6f67e0b in KIO::TransferJob::qt_metacall (this=0xaa7c030, _c=QMetaObject::InvokeMetaMethod, _id=7, _a=0xbfa06928) at /build/buildd/kde4libs-4.2.2/obj-i486-linux-gnu/kio/jobclasses.moc:343
#24 0xb5c18ca8 in QMetaObject::activate (sender=0x95c7d78, from_signal_index=8, to_signal_index=8, argv=0x0) at kernel/qobject.cpp:3069
#25 0xb5c19932 in QMetaObject::activate (sender=0x95c7d78, m=0xb710fe64, local_signal_index=4, argv=0x0) at kernel/qobject.cpp:3143
#26 0xb7023937 in KIO::SlaveInterface::finished (this=0x95c7d78) at /build/buildd/kde4libs-4.2.2/obj-i486-linux-gnu/kio/slaveinterface.moc:165
#27 0xb7027677 in KIO::SlaveInterface::dispatch (this=0x95c7d78, _cmd=104, rawdata=@0xbfa06af4) at /build/buildd/kde4libs-4.2.2/kio/kio/slaveinterface.cpp:175
#28 0xb7023e17 in KIO::SlaveInterface::dispatch (this=0x95c7d78) at /build/buildd/kde4libs-4.2.2/kio/kio/slaveinterface.cpp:91
#29 0xb70141bd in KIO::Slave::gotInput (this=0x95c7d78) at /build/buildd/kde4libs-4.2.2/kio/kio/slave.cpp:322
#30 0xb7016713 in KIO::Slave::qt_metacall (this=0x95c7d78, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfa06c08) at /build/buildd/kde4libs-4.2.2/obj-i486-linux-gnu/kio/slave.moc:76
#31 0xb5c18ca8 in QMetaObject::activate (sender=0x95d0160, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3069
#32 0xb5c19932 in QMetaObject::activate (sender=0x95d0160, m=0xb710c940, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3143
#33 0xb6f2bea7 in KIO::Connection::readyRead (this=0x95d0160) at /build/buildd/kde4libs-4.2.2/obj-i486-linux-gnu/kio/connection.moc:86
#34 0xb6f2d813 in KIO::ConnectionPrivate::dequeue (this=0x95cd308) at /build/buildd/kde4libs-4.2.2/kio/kio/connection.cpp:82
#35 0xb6f2dbf6 in KIO::Connection::qt_metacall (this=0x95d0160, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x8dc4cf0) at /build/buildd/kde4libs-4.2.2/obj-i486-linux-gnu/kio/connection.moc:73
#36 0xb5c118fb in QMetaCallEvent::placeMetaCall (this=0xb795950, object=0x95d0160) at kernel/qobject.cpp:489
#37 0xb5c133a0 in QObject::event (this=0x95d0160, e=0xb795950) at kernel/qobject.cpp:1118
#38 0xb60d3e9c in QApplicationPrivate::notify_helper (this=0x89fa210, receiver=0x95d0160, e=0xb795950) at kernel/qapplication.cpp:4084
#39 0xb60dc19e in QApplication::notify (this=0xbfa073c8, receiver=0x95d0160, e=0xb795950) at kernel/qapplication.cpp:3631
#40 0xb6cf794d in KApplication::notify (this=0xbfa073c8, receiver=0x95d0160, event=0xb795950) at /build/buildd/kde4libs-4.2.2/kdeui/kernel/kapplication.cpp:307
#41 0xb5c02a3b in QCoreApplication::notifyInternal (this=0xbfa073c8, receiver=0x95d0160, event=0xb795950) at kernel/qcoreapplication.cpp:602
#42 0xb5c03695 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x89ce428) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#43 0xb5c0388d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1132
#44 0xb5c2e7ef in postEventSourceDispatch (s=0x89eeb20) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#45 0xb4cd5b88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#46 0xb4cd90eb in ?? () from /usr/lib/libglib-2.0.so.0
#47 0xb4cd9268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#48 0xb5c2e438 in QEventDispatcherGlib::processEvents (this=0x89d3238, flags={i = -1080003944}) at kernel/qeventdispatcher_glib.cpp:323
#49 0xb6175365 in QGuiEventDispatcherGlib::processEvents (this=0x89d3238, flags={i = -1080003896}) at kernel/qguieventdispatcher_glib.cpp:202
#50 0xb5c0106a in QEventLoop::processEvents (this=0xbfa07340, flags={i = -1080003832}) at kernel/qeventloop.cpp:149
#51 0xb5c014aa in QEventLoop::exec (this=0xbfa07340, flags={i = -1080003768}) at kernel/qeventloop.cpp:200
#52 0xb5c03959 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880
#53 0xb60d3d17 in QApplication::exec () at kernel/qapplication.cpp:3553
#54 0x0804c072 in main (argc=1, argv=0xbfa076c4) at /build/buildd/kdepim-4.2.2/kontact/src/main.cpp:218
Comment 1 Dario Andres 2009-07-31 20:45:32 UTC
This looks related to bug 180741. Thanks
Comment 2 Christophe Marin 2009-08-19 21:43:27 UTC
*** Bug 204445 has been marked as a duplicate of this bug. ***
Comment 3 Christophe Marin 2009-11-15 01:25:37 UTC
*** Bug 210649 has been marked as a duplicate of this bug. ***
Comment 4 Christophe Marin 2010-06-06 22:51:14 UTC
*** Bug 238358 has been marked as a duplicate of this bug. ***
Comment 5 Myriam Schweingruber 2012-08-19 10:54:00 UTC
Thank you for your report. Kmail1 is currently unmaintained and the code has changed sufficiently in Kmail2 so the backtraces are not really useful anymore. Should you experience the same crash in Kmail 4.8.5 or later, please open a new report for Kmail2. Thank you for your understanding