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 707690 - Importing PGP key fails because seahorse tries to use gpg instead of gpg2
Importing PGP key fails because seahorse tries to use gpg instead of gpg2
Status: RESOLVED NOTGNOME
Product: seahorse
Classification: Applications
Component: libcryptui
3.8.x
Other Linux
: Normal normal
: ---
Assigned To: Stef Walter
Seahorse Maintainer
Depends on:
Blocks:
 
 
Reported: 2013-09-07 15:11 UTC by Christian Stadelmann
Modified: 2017-01-23 22:55 UTC
See Also:
GNOME target: ---
GNOME version: 3.7/3.8


Description Christian Stadelmann 2013-09-07 15:11:29 UTC 
I am using Gnome 3.8 on Fedora 19

I tried to import a public PGP key from a file

Error message:
„Import fehlgeschlagen: Kindprozess »/usr/bin/gpg« konnte nicht ausgeführt werden (Datei oder Verzeichnis nicht gefunden)“
translation:
"Import failed: could not execute child process »/usr/bin/gpg« (file or directory not found)"

The reason is simple: My Fedora 19 has /usr/bin/gpg2 (gnupg2 2.0.x) installed and NOT gnupg 1.4.x which the importer tries to use.
Comment 1 Stef Walter 2013-09-09 13:20:34 UTC 
It seems like Fedora is building things incorrectly, or choosing dependencies incorrectly. At build time we check for both gpg and gpg2. We use the path for the one that's available.
Comment 2 Christian Stadelmann 2013-09-09 16:40:48 UTC 
Ok, thanks a lot. Reported as https://bugzilla.redhat.com/show_bug.cgi?id=1005916.
Comment 3 indolering 2017-01-23 22:55:43 UTC 
Importing and managing keys on Fedora has been broken for going on 4 years now.  @Stef, do you think you could pop over to the RedHat bugzilla ticket and give their package managers some pointers?