GNU bug report logs - #2412
spurious "Sign failed" errors

Previous Next

Package: emacs;

Reported by: Sven Joachim <svenjoac <at> gmx.de>

Date: Fri, 20 Feb 2009 18:10:07 UTC

Severity: normal

Merged with 3953

Done: Chong Yidong <cyd <at> stupidchicken.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (Emacs bug Tracking System)
To: Daiki Ueno <ueno <at> unixuser.org>
Subject: bug#2412: marked as done (spurious "Sign failed" errors)
Date: Sun, 03 May 2009 22:45:04 +0000
[Message part 1 (text/plain, inline)]
Your message dated Mon, 04 May 2009 07:36:48 +0900
with message-id <87zldt4xvj.fsf <at> broken.deisui.org>
and subject line Re: bug#2412: spurious "Sign failed" errors
has caused the Emacs bug report #2412,
regarding spurious "Sign failed" errors
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact help-debbugs <at> gnu.org
immediately.)


-- 
2412: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=2412
Emacs Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: Sven Joachim <svenjoac <at> gmx.de>
To: undisclosed-recipients:;
Subject: spurious "Sign failed" errors
Date: Fri, 20 Feb 2009 19:03:44 +0100 (MET)
[Message part 3 (text/plain, inline)]
Gnus v5.13
GNU Emacs 23.0.60.1 (i486-pc-linux-gnu, GTK+ Version 2.12.11)
 of 2008-11-30 on turtle, modified by Debian
200 news.motzarella.org InterNetNews NNRP server INN 2.4.5 ready (posting ok).

I'm experiencing painful, but not always reproducible problems with
sending or previewing signed mails.  Often I get an error "Sign failed"
and a backtrace like this:

,----
| Debugger entered--Lisp error: (error "Sign failed")
|   signal(error ("Sign failed"))
|   byte-code("<snipped>" [mml2015-epg-secret-key-id-list error password-cache-remove signal] 4)
|   mml2015-epg-sign((part (sign . "pgpmime") (tag-location . 186) (contents . "Nur ein Test.\n")))
|   mml2015-sign((part (sign . "pgpmime") (tag-location . 186) (contents . "Nur ein Test.\n")))
|   mml-pgpmime-sign-buffer((part (sign . "pgpmime") (tag-location . 186) (contents . "Nur ein Test.\n")))
|   mml-generate-mime-1((part (sign . "pgpmime") (tag-location . 186) (contents . "Nur ein Test.\n")))
|   mml-generate-mime()
|   message-encode-message-body()
|   mml-to-mime()
|   mml-preview(nil)
|   call-interactively(mml-preview nil nil)
`----

If this happens during sending, the message actually is signed and sent,
but no copy lands in my archive folder. :-(

I'm using gpg-agent with pinentry-gtk2 for the passphrase.


[Message part 4 (application/emacs-lisp, inline)]
[Message part 5 (message/rfc822, inline)]
From: Daiki Ueno <ueno <at> unixuser.org>
To: Sven Joachim <svenjoac <at> gmx.de>
Cc: 2412-done <at> debbugs.gnu.org, Chong Yidong <cyd <at> stupidchicken.com>
Subject: Re: bug#2412: spurious "Sign failed" errors
Date: Mon, 04 May 2009 07:36:48 +0900
Sven Joachim <svenjoac <at> gmx.de> writes:

>> -    (accept-process-output (epg-context-process context) 1)))
>> +    (accept-process-output (epg-context-process context) 1))
>> +  (sleep-for 0.1))
>
> That seems to do the trick.  At least, I had no problem in ~15 attempts
> to preview/send signed messages, whereas without your patch the "Sign
> failed" error would happen about every second time.

Thanks for testing.  I've checked in the patch.

Regards,
-- 
Daiki Ueno


This bug report was last modified 15 years and 201 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.