This bug was fixed in the package gcr - 3.41.1-4

---------------
gcr (3.41.1-4) unstable; urgency=medium

  * debian/patches/gitlab_meson_resource.patch:
    - cherry pick a fix proposed upstream to fix a regression in the port
      to meson where one the gresource files isn't include anymore which
      is needed for pkcs11 certificates import. (lp: #1771880)
      Thanks Damjan Jovanovic for working on the issue

 -- Sebastien Bacher <seb...@ubuntu.com>  Wed, 20 Dec 2023 10:59:16
+0100

** Changed in: gcr (Ubuntu)
       Status: Fix Committed => Fix Released

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

Title:
  Seahorse unable to import pkcs12 certificates

Status in seahorse:
  New
Status in gcr package in Ubuntu:
  Fix Released
Status in gnome-keyring package in Ubuntu:
  Triaged
Status in seahorse package in Ubuntu:
  Triaged
Status in gnome-keyring package in Fedora:
  New
Status in seahorse package in Fedora:
  Unknown

Bug description:
  seahorse 3.20.0-5 / gnome-keyring 3.28.0.2-1ubuntu1.18.04.1 / Ubuntu
  18.04 LTS / GNOME 3.28.1

  When trying to import a certificate into seahorse/gnome-keyring on
  Ubuntu 18.04, seahorse GUI application shows the 'import' button
  greyed out, while mouse hovering the "import" button shows the message
  "Cannot import because there are no compatible importers".

  This problem doesn't occur on Ubuntu 16.04 LTS (Seahorse 3.18.0), as
  I've just tested on my wife's laptop, but happens in my Laptop with
  Ubuntu 18.04 LTS (Seahorse 3.20.0-5).

  Because that problem, it's not possible to digitally sign documents
  with LibreOffice.

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to