all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 55258@debbugs.gnu.org
Subject: bug#55258: Icedove, external OpenGPG configuration and ld path
Date: Wed, 04 May 2022 10:43:30 +0200	[thread overview]
Message-ID: <87zgjx6631.fsf@jpoiret.xyz> (raw)

Hello everyone,

Currently, if you want to use a smart card with icedove, you have to
enable mail.openpgp.allow_external_gnupg in the config editor, but on
Guix, icedove will still not find the key that's on your smart card,
because it's unable to dlopen the GPGME library (understandably).

For now, my workaround is to launch icedove via

`LD_LIBRARY_PATH="$(guix build gpgme)/lib" icedove`

I outlined something similar to get icecat to be able to share desktops
under wayland [1], this time with the pipewire libraries.  This doesn't
seem like a great out-of-the-box experience for users, especially since
nothing indicates that this is the root of the problem.  Is there
anything we could do about this?

Adding all possible optional deps to LD_LIBRARY_PATH in a wrapper seems
a bit overkill, since for example PipeWire's closure is ~800 MiB,
depending for example on X libraries, and packagers won't always be able
to find 100% of the optional deps that are dlopen'd.

WDYT?

[1] https://lists.gnu.org/archive/html/guix-devel/2022-04/msg00205.html
(8735hx74qw.fsf@jpoiret.xyz)

-- 
Josselin Poiret




             reply	other threads:[~2022-05-04  8:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-04  8:43 Josselin Poiret via Bug reports for GNU Guix [this message]
2022-05-04 12:19 ` bug#55258: Icedove, external OpenGPG configuration and ld path Liliana Marie Prikler
2022-09-28 22:25 ` Jonathan Brielmaier
2022-09-29  9:31   ` Josselin Poiret via Bug reports for GNU Guix

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=87zgjx6631.fsf@jpoiret.xyz \
    --to=bug-guix@gnu.org \
    --cc=55258@debbugs.gnu.org \
    --cc=dev@jpoiret.xyz \
    /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/guix.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.