After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 787543 - [patch] graphical pinentry broken because _gcr_gnupg_process_run_async does not pass required environment variables
[patch] graphical pinentry broken because _gcr_gnupg_process_run_async does n...
Status: RESOLVED OBSOLETE
Product: gcr
Classification: Core
Component: General
3.20.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME keyring maintainer(s)
GNOME keyring maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2017-09-11 12:10 UTC by intrigeri
Modified: 2021-05-17 13:19 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
_gcr_gnupg_process_run_async: pass display to GnuPG (1.71 KB, patch)
2017-09-11 12:10 UTC, intrigeri 		needs-work Details | Review

Description intrigeri 2017-09-11 12:10:09 UTC 
Created attachment 359521 [details] [review]
_gcr_gnupg_process_run_async: pass display to GnuPG

As reported on https://bugs.debian.org/869416, graphical pinentry (except pinentry-gnome3, that cheats as it uses GNOME Shell :) fail to start when Seahorse needs them.

I've investigated this problem with NIIBE Yutaka (a friendly Debian & GnuPG upstream developer) and he identified the root cause.

Patch attached :)
Comment 1 Stef Walter 2017-09-11 12:13:01 UTC 
Review of attachment 359521 [details] [review]:

The base gcr library should not have a GTK+ dependency. Many of its callers expect this. 

Could we just pass the DISPLAY environment variable through to have the same effect?
Comment 2 intrigeri 2017-09-11 12:50:19 UTC 
Hi Stef! Thanks for looking into it. I don't know if passing $DISPLAY has the same effect as passing --display, so I've pointed NIIBE to your comment.
Comment 3 GNOME Infrastructure Team 2021-05-17 13:19:45 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gcr/-/issues/80.