Bug 190043

Summary: crashes when canceling the message after cancelling pinentry dialogue (gpg)
Product: [Unmaintained] kmail Reporter: Sune Vuorela <debian>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: andresbajotierra
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Debian testing   
OS: Unspecified   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Sune Vuorela 2009-04-19 11:56:32 UTC
Version:            (using KDE 4.2.2)
Installed from:    Debian testing/unstable Packages

Hi!

Doing the following steps:
Configure your kmail with gpg and pinentry and stuff
Click on a gpg encrypted email
Wait for pinentry dialog
Click cancel
Wait for popup
Click on a different email while popup still around
Click cancel on popup.
SigSegv

Expected behaviour: no crash ;)


Application: KMail (kmail), signal SIGSEGV

Thread 1 (Thread 0xb4114700 (LWP 22222)):
[KCrash Handler]
#6  0xb73c717b in KMReaderWin::parseMsg (this=0xaa08d80, aMsg=0xae6ec38) at ../../kmail/kmreaderwin.cpp:1628
#7  0xb73b38c8 in KMReaderWin::displayMessage (this=0xaa08d80) at ../../kmail/kmreaderwin.cpp:1555
#8  0xb73b3ae0 in KMReaderWin::updateReaderWin (this=0xaa08d80) at ../../kmail/kmreaderwin.cpp:1495
#9  0xb73c20d0 in KMReaderWin::qt_metacall (this=0xaa08d80, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbff97318) at ./kmreaderwin.moc:164
#10 0xb7026be0 in QMetaObject::activate (sender=0xaa08dd0, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3031
#11 0xb7027962 in QMetaObject::activate (sender=0xaa08dd0, m=0xb70f50c4, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3101
#12 0xb7061867 in QTimer::timeout (this=0xaa08dd0) at .moc/release-shared/moc_qtimer.cpp:126
#13 0xb702d58e in QTimer::timerEvent (this=0xaa08dd0, e=0xbff977ac) at kernel/qtimer.cpp:257
#14 0xb70216bf in QObject::event (this=0xaa08dd0, e=0xbff977ac) at kernel/qobject.cpp:1120
#15 0xb670779c in QApplicationPrivate::notify_helper (this=0x9ea59d8, receiver=0xaa08dd0, e=0xbff977ac) at kernel/qapplication.cpp:3803
#16 0xb670f61e in QApplication::notify (this=0xbff97ac8, receiver=0xaa08dd0, e=0xbff977ac) at kernel/qapplication.cpp:3393
#17 0xb7d9ab7d in KApplication::notify (this=0xbff97ac8, receiver=0xaa08dd0, event=0xbff977ac) at ../../kdeui/kernel/kapplication.cpp:307
#18 0xb70120e1 in QCoreApplication::notifyInternal (this=0xbff97ac8, receiver=0xaa08dd0, event=0xbff977ac) at kernel/qcoreapplication.cpp:587
#19 0xb7040041 in QTimerInfoList::activateTimers (this=0x9ea7764) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:209
#20 0xb703c690 in timerSourceDispatch (source=0x9ea7730) at kernel/qeventdispatcher_glib.cpp:160
#21 0xb49f0718 in IA__g_main_context_dispatch (context=0x9ea76b0) at /build/buildd-glib2.0_2.20.0-3-i386-JnKxca/glib2.0-2.20.0/glib/gmain.c:1814
#22 0xb49f3c7b in g_main_context_iterate (context=0x9ea76b0, block=1, dispatch=1, self=0x9e9ea98) at /build/buildd-glib2.0_2.20.0-3-i386-JnKxca/glib2.0-2.20.0/glib/gmain.c:2448
#23 0xb49f3df8 in IA__g_main_context_iteration (context=0x9ea76b0, may_block=1) at /build/buildd-glib2.0_2.20.0-3-i386-JnKxca/glib2.0-2.20.0/glib/gmain.c:2511
#24 0xb703c5e8 in QEventDispatcherGlib::processEvents (this=0x9ea3690, flags={i = -1074169560}) at kernel/qeventdispatcher_glib.cpp:319
#25 0xb67a0d75 in QGuiEventDispatcherGlib::processEvents (this=0x9ea3690, flags={i = -1074169512}) at kernel/qguieventdispatcher_glib.cpp:198
#26 0xb70107aa in QEventLoop::processEvents (this=0xbff979d0, flags={i = -1074169448}) at kernel/qeventloop.cpp:143
#27 0xb701096a in QEventLoop::exec (this=0xbff979d0, flags={i = -1074169384}) at kernel/qeventloop.cpp:194
#28 0xb7013025 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845
#29 0xb6707617 in QApplication::exec () at kernel/qapplication.cpp:3331
#30 0x0804a6a0 in main (argc=) at ../../kmail/main.cpp:146
Comment 1 Dario Andres 2009-04-19 15:23:40 UTC
Marking as duplicate of bug 180741

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