Bug 1254651 - seahorse-nautilus use a different version of gpg than seahorse
seahorse-nautilus use a different version of gpg than seahorse
Status: CLOSED EOL
Product: Fedora
Classification: Fedora
Component: seahorse-nautilus (Show other bugs)
22
x86_64 Linux
unspecified Severity unspecified
: ---
: ---
Assigned To: Rui Matos
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-08-18 11:03 EDT by Erwan GEORGET
Modified: 2016-07-19 13:33 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-07-19 13:33:38 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Error indicating that seahorse-nautilus didn't find an usable key (482.71 KB, image/png)
2015-08-18 11:03 EDT, Erwan GEORGET
no flags Details
Test data (153.53 KB, image/png)
2015-08-18 13:31 EDT, Erwan GEORGET
no flags Details

  None (edit)
Description Erwan GEORGET 2015-08-18 11:03:56 EDT
Created attachment 1064345 [details]
Error indicating that seahorse-nautilus didn't find an usable key

Description of problem:
seahorse-nautilus fail to find an usable key, as seahorse use gnupg 1.4.19, and seahorse-nautilus use gnupg 2.1.7.

Version-Release number of selected component (if applicable):
seahorse-nautilus 3.11.92
seahorse 3.16.0
GNUPG 1.4.19 and 2.1.7


How reproducible:
Happened on my two PC.

Steps to Reproduce:
1. create a new GNUPG key with seahorse
2. Install seahorse-nautilus
3. Try to encrypt/sign a folder or a file


Actual results:
Error indicating that seahorse-nautilus didn't find an usable key (see screenshot)


Expected results:
seahorse-nautilus asking to select which key to use
Comment 1 Erwan GEORGET 2015-08-18 13:22:58 EDT
I've done some more test with gnupg.

Test environment :

- Fedora 22 (updated, update-testing activated)
- Seahorse 3.16.0-1
- seahorse-nautilus 3.11.92-3

Data used :
- Some gnupg 2.x keys
- Some gnupg 1.4.x keys

Test 0 : initial situation

-> Seahorse only show gnupg 1.4.x keys
-> Seahorse say he is using GNUPG (/usr/bin/gpg) 1.4.19
-> If I try to create a new key, seahorse create it, but it's very long (1-2 minutes)

Test 1 : removing gnupg 1.4.x (sudo dnf remove -y gnupg)

-> Seahorse now only show gnupg 2.x keys
-> Seahorse still say he is using GNUPG (/usr/bin/gpg) 1.4.19
-> If I try to create a new key, I get an error and cannot create it.

Test 2 : Rebooting the computer

-> Seahorse only show gnupg 2.x keys
-> Seahorse still say he is using GNUPG (/usr/bin/gpg) 1.4.19
-> If I try to create a new key, I get an error and cannot create it.

Test 3 : re-installing gnupg 1.4 (sudo dnf install -y gnupg)

-> Seahorse only show gnupg 2.x keys
-> Seahorse still say he is using GNUPG (/usr/bin/gpg) 1.4.19
-> If I try to create a new key, I get an error and cannot create it.

Test 4 : Rebooting the computer (again)

-> Seahorse only show gnupg 2.x keys
-> Seahorse still say he is using GNUPG (/usr/bin/gpg) 1.4.19
-> If I try to create a new key, I get an error and cannot create it.

Test 4 : Rebuilding gnupg keydb (gpg --rebuild-keydb-caches)

-> Seahorse now only show gnupg 1.4.x keys, gpg 2.x keys are hidden
-> Seahorse still say he is using GNUPG (/usr/bin/gpg) 1.4.19
-> If I try to create a new key, I get an error and cannot create it.
Comment 2 Erwan GEORGET 2015-08-18 13:31:46 EDT
Created attachment 1064384 [details]
Test data
Comment 3 Fedora End Of Life 2016-07-19 13:33:38 EDT
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.