all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: owner@emacsbugs.donarmstrong.com (Emacs bug Tracking System)
To: Daiki Ueno <ueno@unixuser.org>
Subject: bug#2412: marked as done (spurious "Sign failed" errors)
Date: Sun, 03 May 2009 22:45:04 +0000	[thread overview]
Message-ID: <handler.2412.D2412.124139021530924.ackdone@emacsbugs.donarmstrong.com> (raw)
In-Reply-To: 877i6gng5o.fsf@turtle.gmx.de

[-- Attachment #1: Type: text/plain, Size: 860 bytes --]


Your message dated Mon, 04 May 2009 07:36:48 +0900
with message-id <87zldt4xvj.fsf@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 owner@emacsbugs.donarmstrong.com
immediately.)


-- 
2412: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=2412
Emacs Bug Tracking System
Contact owner@emacsbugs.donarmstrong.com with problems

[-- Attachment #2: Type: message/rfc822, Size: 7309 bytes --]



[-- Attachment #2.1.2: Type: text/plain, Size: 1290 bytes --]

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.



[-- Attachment #2.1.3: User settings --]
[-- Type: application/emacs-lisp, Size: 3572 bytes --]

[-- Attachment #3: Type: message/rfc822, Size: 3273 bytes --]

From: Daiki Ueno <ueno@unixuser.org>
To: Sven Joachim <svenjoac@gmx.de>
Cc: 2412-done@emacsbugs.donarmstrong.com, Chong Yidong <cyd@stupidchicken.com>
Subject: Re: bug#2412: spurious "Sign failed" errors
Date: Mon, 04 May 2009 07:36:48 +0900
Message-ID: <87zldt4xvj.fsf@broken.deisui.org>

Sven Joachim <svenjoac@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


      reply	other threads:[~2009-05-03 22:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87zldt4xvj.fsf@broken.deisui.org>
2009-02-20 18:03 ` bug#2412: spurious "Sign failed" errors Sven Joachim
2009-05-03 22:45   ` Emacs bug Tracking System [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=handler.2412.D2412.124139021530924.ackdone@emacsbugs.donarmstrong.com \
    --to=owner@emacsbugs.donarmstrong.com \
    --cc=ueno@unixuser.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.