Bug 490766

SUMMARY
When trying to "reply to all", KMail sometimes freezes with a stack trace in GpgME::Key::update(). This looks like a deadlock.

STEPS TO REPRODUCE
1. Browse a long mailbox (EWS if that matters)
2. For each message, try to "reply to all"
3. KMail will eventually freeze

OBSERVED RESULT
KMail freezes before showing the mail composer, stack trace below.
Once you've found an email creating the freeze, this is reproducible every time.

EXPECTED RESULT
The mail composer appears in all cases.

SOFTWARE/OS VERSIONS
KMail commit da64f2fe1d667e924e981b17956148f81228dc81 from Mon Jul 8 07:14:10 2024 +0200. This is version kmail2 6.1.40 alpha (24.07.40).

ADDITIONAL INFORMATION

#0  0x0000799b13118bcf in __GI___poll (fds=0x570566608cc0, nfds=2, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x0000799a7cfdeff5 in  () at /lib/x86_64-linux-gnu/libgpgme.so.11
#2  0x0000799a7cfb2132 in  () at /lib/x86_64-linux-gnu/libgpgme.so.11
#3  0x0000799a7cfc0e2e in gpgme_op_keylist_next () at /lib/x86_64-linux-gnu/libgpgme.so.11
#4  0x0000799a7cfc38e7 in gpgme_get_key () at /lib/x86_64-linux-gnu/libgpgme.so.11
#5  0x0000799a7e5c699e in GpgME::Context::key(char const*, GpgME::Error&, bool) () at /lib/x86_64-linux-gnu/libgpgmepp.so.6
#6  0x0000799a7e5caff8 in GpgME::Key::update() () at /lib/x86_64-linux-gnu/libgpgmepp.so.6
#7  0x0000799a679fe852 in KMComposerWin::runKeyResolver() (this=0x570568dbb520) at /home/louis/Personal/kde6/src/kmail/src/editor/kmcomposerwin.cpp:3745
#8  0x0000799a67a0217e in KMComposerWin::slotRecipientEditorFocusChanged() (this=0x570568dbb520) at /home/louis/Personal/kde6/src/kmail/src/editor/kmcomposerwin.cpp:4218
#9  0x0000799a67a020d0 in KMComposerWin::slotRecipientEditorLineAdded(KPIM::MultiplyingLine*) (this=0x570568dbb520, line_=0x5705665da670) at /home/louis/Personal/kde6/src/kmail/src/editor/kmcomposerwin.cpp:4202