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 782612 - First attempt to sign a key fails with General Error
First attempt to sign a key fails with General Error
Product: seahorse
Classification: Applications
Component: general
Other Windows
: Normal normal
: ---
Assigned To: Seahorse Maintainer
Seahorse Maintainer
Depends on:
Reported: 2017-05-14 09:05 UTC by Kjo Hansi Glaz
Modified: 2018-08-03 19:53 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Kjo Hansi Glaz 2017-05-14 09:05:21 UTC
When I open seahorse, I select a key and I try to sign that key, then I get a "General Error" the first time. When I try again to sign the same key then everything goes fine.

Seahorse version is 3.20.0-3.1 (that is upstream seahorse 3.20.0 with cdfc5b2 applied)

Seahorse output:

(seahorse:10389): seahorse-CRITICAL **: file
pgp/seahorse-gpgme-key-op.c: line 551 (sign_transit): should not be reached

I think that a part of the fix for the new status line KEY_CONSIDERED introduced in gpg 2.1.13 is still missing.
Comment 1 Kjo Hansi Glaz 2017-05-14 13:07:50 UTC
My assumption that this issue was related to KEY_CONSIDERED seems wrong. Seahorse status in sign_transit (pgp/seahorse-gpgme-key-op.c) is GPGME_STATUS_PINENTRY_LAUNCHED. That explains why this only happens on the 1st launch. On the 2nd launch, the passphrase is cached and pinentry is not launched.
Comment 2 Kjo Hansi Glaz 2017-05-14 15:22:08 UTC
This bug looks similar to #769957 (

Comment 3 GNOME Infrastructure Team 2018-08-03 19:53:25 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: