On Mon, 19 Oct 2020 09:46:44 -0000
Sebastien Bacher <[email protected]> wrote:

> Thank you for your bug report, when you write 'won't import', what do
> you do and what error do you get exacly? is it raising an error
> dialog? action as if it was importing but the content is missing?
> could you also provide some details on the gpg you are trying to
> import (dsa, rsa, length)
>
> ** Changed in: seahorse (Ubuntu)
>    Importance: Undecided => Low
>
> ** Changed in: seahorse (Ubuntu)
>        Status: New => Incomplete
>

I hope this is not too contorted.  I tried 3 keys, a RSA 2048
key created in 2012, a DSA 1024 key created in 2007, and a RSA 2048 key
created in 2019.  The "Import Key" menu option in Seahorse wont import
either a binary nor an armored (asc) version for any of these keys. For either 
key version of any key an error message pops up "The information in this key 
has not yet been verified" and underneath the message are the details of the 
key. In the upper right corner "Import" appears and clicking on it does 
nothing.  The key is not imported.

In the file manager window a double click of the asc version of the key
or using the menu choice "Open with Import Key" will import the key. A
message apperars "the key blaa blaa has been imported".  And infact it
has. With the binary version of the key "keyfile.pgp" nothing works, no
error message no nothing.  This binary version can be imported using a
terminal. As was noted in the other bug report, the sucessfully added
keys are only listed after Seahorse is stopped and restarted.

And finally Seahorse menu option "Export" will only export a binary
version of keys even thought one of the choices is to export the key as
an armored ".asc" version.

I hope this is clear and detailed enough.

Larry

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to seahorse in Ubuntu.
https://bugs.launchpad.net/bugs/1900347

Title:
  Doesn't import gpg keys Doesn't export armored (asc) gpg keys

Status in seahorse package in Ubuntu:
  Incomplete

Bug description:
  Very similar to bug # 1577198.  Seahorse (Passwords and Keys) won't
  import gpg keys.  But if I double click on the gpg key in the file
  manager it will show as imported after I restart Seahorse. After keys
  are imported (using the double click method or CLI) they can only be
  exported as binary keys i.e. keyname.pgp.  If I try the option to
  export as a keyname.asc version (armored) I only get the same binary
  key.  Everything works fine with gpg in a terminal.

  This is with a fresh install of 20.04.1,  Seahorse 3.36-1 with
  Seahorse-daemon and Seahorse-nautilis installed. The Gnupg version is
  2.2.19

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: seahorse 3.36-1
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 18 11:32:13 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-10-09 (8 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: seahorse
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1900347/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to