On Tue, 31 May 2011 19:33:29 +0200, Felix Geller <fgeller at gmail.com> wrote: > I get the following trace when using show --decrypt to decrypt a > specific message (have to kill the process to actually get the trace): > > #0 0x00000001006121a6 in poll () > #1 0x000000010006d3d2 in gpg_ctx_op_step () > #2 0x000000010006e5c7 in gpg_decrypt () > #3 0x00000001000566cf in g_mime_multipart_encrypted_decrypt () > #4 0x000000010000a413 in show_message_part (part=0x10606fc20, > #state=0x7fff5fbfd1c0, format=0x10002ef80, params=0x7fff5fbfd2c0, > #first=1) at show-message.c:71 > > So I guess it ends up looping or waiting in poll(), but I can't tell why > it would do that. I guess the next step is to post to the gmime mailing > list, or?
Hey, Felix. Yeah, I unfortunately don't have any other suggestions other than asking the gmime folks. Interestingly, I see the following message in your crypto test output: Error: search term did not match precisely one message. which seems to indicate that the desired message wasn't actually delivered properly, contrary to what the emacs delivery tests are stating. Not sure how that could be related, though, since it looks like the trace that you show above definitely looks like gmime caught in a poll loop. jamie. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 835 bytes Desc: not available URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20110602/e9eb228c/attachment.pgp>