Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Gnus hangs when calling gpg
Date: Thu, 27 Feb 2014 09:28:07 -0500	[thread overview]
Message-ID: <87eh2oeiko.fsf@lifelogs.com> (raw)
In-Reply-To: <loom.20140226T173732-417@post.gmane.org>

On Wed, 26 Feb 2014 16:45:31 +0000 (UTC) Julien Cubizolles <j.cubizolles@free.fr> wrote: 

JC> On a fresh install, gnus hangs whenever it invokes gpg with:
JC>   call-process("/usr/bin/gpg" nil (t nil) nil "--with-colons" "--list-config")
JC>   apply(call-process "/usr/bin/gpg" nil (t nil) nil ("--with-colons"
JC> "--list-config"))
JC>   epg-configuration()
JC>   (epg-check-configuration (epg-configuration))

JC> This happens when I try to byte-compile the latest git (stuck at building
JC> deuglify.el) or load 'gnus-registry.

JC> Whether  it's a problem with gpg or Emacs, I don't know. I'm running Emacs
JC> 24.3.50.2 on Ubuntu 13.10. Any idea what I should try to investigate further ?

I would first disable gpg temporarily, if possible, and test.  If it
works, you can reenable it after Gnus is up.

I'd like to avoid this, especially at the byte-compile stage.  Looks
like ./lisp/epg-config.el:epg-configuration is doing the calling to
investigate GnuPG's capabilities.  That in turn is called by
mml-smime.el and mml1991.el and mml2015.el.

Daiki Ueno should probably comment on the necessity of this invocation,
since it can hang for many reasons and I would guess is not essential to
basic Gnus usage.

JC> Julien, stuck without gnus on his shiny new computer.

The humanity! :)

Ted




  parent reply	other threads:[~2014-02-27 14:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-26 16:45 Julien Cubizolles
2014-02-26 18:29 ` Adam Sjøgren
2014-02-27 10:54 ` Matt Ford
2014-02-27 14:28 ` Ted Zlatanov [this message]
2014-03-04  5:03   ` Daiki Ueno
2014-03-05 14:05     ` Lars Ingebrigtsen
2014-03-06  3:28       ` Daiki Ueno
2014-03-06 14:10         ` Ted Zlatanov
2014-03-07  7:28           ` Daiki Ueno

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=87eh2oeiko.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).