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 769957 - Unable to change expiration date
Unable to change expiration date
Status: RESOLVED OBSOLETE
Product: seahorse
Classification: Applications
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Seahorse Maintainer
Seahorse Maintainer
Depends on:
Blocks:
 
 
Reported: 2016-08-15 21:18 UTC by tdruiva
Modified: 2018-08-03 19:51 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
error window (126.93 KB, image/png)
2016-08-15 21:18 UTC, tdruiva 		Details

Description tdruiva 2016-08-15 21:18:31 UTC 
Created attachment 333382 [details]
error window

Hey,

I'm trying to use Seahorse to update the expiration date of a key but I'm not able to it.

When I try to update, like to set to never expire or if I put some specific date I'm receiving the error: "Couldn't change expiry date" "General error".

Tks
Comment 1 Link Dupont 2016-09-17 06:23:10 UTC 
Extracting the error from journal, this line gets printed when the reported "General error" dialog pops up.

(seahorse:31482): seahorse-CRITICAL **: file pgp/seahorse-gpgme-key-op.c: line 1117 (edit_expire_transit): should not be reached
Comment 2 Kjo Hansi Glaz 2017-05-14 15:21:01 UTC 
At the time of the seahorse-CRITRICAL status = 88, which is referenced in gpgme.h.in: GPGME_STATUS_PINENTRY_LAUNCHED = 88.

This bug looks similar to #782612 (https://bugzilla.gnome.org/show_bug.cgi?id=782612).

kpgp just ignore these: https://cgit.kde.org/kgpg.git/commit/?id=fd934f1763f33e862dc5385a4f77072e80336faa
Comment 3 GNOME Infrastructure Team 2018-08-03 19:51:57 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/seahorse/issues/152.