Bug 1553014 - Unable to manipulate GnuPG keys (edit, sign, trust) in seahorse
Summary: Unable to manipulate GnuPG keys (edit, sign, trust) in seahorse
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: seahorse
Version: 27
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-08 02:59 UTC by John Webb
Modified: 2018-11-30 23:17 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-30 23:17:28 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description John Webb 2018-03-08 02:59:33 UTC
Description of problem:

When attempting to view my own photo, or add a different photo, or sign my own key or trust another installed key receive "General Error" unable to proceed.

Version-Release number of selected component (if applicable):
3.20.0

How reproducible:
Always for me.  Repeats in both Wayland and X-11.  Have tried a re-install of seahorse via dnf

Steps to Reproduce:
1. Open Seahorse (same results starting from menu or terminal)
2. Select GnuPG keys
3. select any installed key
4. right-click for 'properties' and pop-up appears.  If in terminal receive a critical warning:  (seahorse:7268): seahorse-CRITICAL **: file pgp/seahorse-gpgme-key-op.c: line 2420 (photoid_load_transit): should not be reached
seahorse-Message: couldn't load key photos: General error  (but am able to proceed)
5. select a key and attempt to Trust, receive a popup "Unable to change trust General error ---- close"
6. another example - select own key (I have a photo but does not display).  If I attempt to add a different photo, I can proceed, but once new photo selected receive error "Couldn't add photo General error ----- close"

Actual results:
Receive "General Error ..." unable to complete the operation

Expected results:
I should be able to trust or sign a key, or edit my photo.

Additional info:
gpg and gpg2 appear to work correctly from command line.  I am able to check my keys and encrypt and decrypt messages manually.

Comment 1 W. de Heiden 2018-04-10 07:44:30 UTC
Confirmed, having the same problems running Fedora 27:

ame        : seahorse
Version     : 3.20.0
Release     : 6.fc27
Architecture: x86_64
Install Date: Thu 08 Mar 2018 03:06:21 PM CET
Group       : Unspecified
Size        : 6224314
License     : GPLv2+ and LGPLv2+
Signature   : RSA/SHA256, Sat 05 Aug 2017 08:52:43 PM CEST, Key ID f55e7430f5282ee4
Source RPM  : seahorse-3.20.0-6.fc27.src.rpm
Build Date  : Fri 04 Aug 2017 09:24:11 PM CEST
Build Host  : buildhw-05.phx2.fedoraproject.org
Relocations : (not relocatable)
Packager    : Fedora Project
Vendor      : Fedora Project
URL         : https://wiki.gnome.org/Apps/Seahorse
Summary     : A GNOME application for managing encryption keys
Description :
Seahorse is a graphical interface for managing and using encryption keys.
It also integrates with nautilus, gedit and other places for encryption
operations.  It is a keyring manager.

Comment 2 Nicolas Berrehouc 2018-05-06 15:47:49 UTC
Same problem in F28 with seahorse-3.20.0-9.fc28.x86_64.

You can import with Seahorse an existing GPG key but at the end nothing appear in Seahorse.

Comment 3 John Webb 2018-06-01 11:42:02 UTC
problem persists in FC 28, Seahorse 3.20.0; perhaps even more severe in that the entire section related to gnuPGP is missing.  See bug 1577397 -> https://bugzilla.redhat.com/show_bug.cgi?id=1577397.

Comment 4 Nicolas Berrehouc 2018-08-13 16:03:00 UTC
Issue from mainstream https://gitlab.gnome.org/GNOME/seahorse/issues/4 .
"For your issue, I think (but I'm not completely sure) that the seahorse package of Fedora does not enable the compilation option for GPG keys, which is why you're not seeing them."

Can someone confirm?

Comment 5 Nicolas Berrehouc 2018-10-20 11:44:27 UTC
With seahorse-3.30-1.fc29.x86_64 it is possible to see again GPG's entries and edit them.

Comment 6 Ben Cotton 2018-11-27 13:58:23 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 7 Ben Cotton 2018-11-30 23:17:28 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.