Comment 59 for bug 1771880

Thank you, very, very, much!

O 19:25, luns, 18 de dec. de 2023, Angelo Giacomini Ribas <
<email address hidden>> escribiu:

> May the Luck be with you!
>
> On Mon, 18 Dec 2023, 14:35 Damjan Jovanovic, <email address hidden>
> wrote:
>
> > I am personally working on this issue, you can follow my progress on
> > https://gitlab.gnome.org/GNOME/seahorse/-/issues/205
> >
> > So far it looks like there are a number of bugs; a simplified picture
> > looks something like this:
> >
> > seahorse: gcr_import_button_add_parsed() gnome-keyring:
> > gkr-tool-import: on_parser_parsed()
> > | |
> > | +-------------------+
> > | |
> > v v
> > gcr: gcr_importer_create_for_parsed()
> > |
> > v
> > gcr: iface->create_for_parsed()
> > |
> > v
> > gcr: _gcr_pkcs11_importer_create_for_parsed()
> > | ^ |
> > v | v
> > gcr: list_all_slots() gcr: is_slot_importable() for
> > p11-kit-trust.so
> > (loads PKCS#11 modules, (prints: "token is not importable: %s:
> write
> > protected")
> > enumerates their slots)
> > | ^ | ^
> > v | v | remote procedure call
> > p11-kit-trust.so gnome-keyring-pkcs11.so ---------------------->
> > gnome-keyring-daemon
> > | ^ (disabled by blacklist) |
> > v | v
> > trust policy module
> > gnome2-store (I kid you not)
> > | ^ |
> > v | v
> > read-only system CA certificates
> > ~/.local/share/keyrings/user.keystore
> > and blacklist
> (fails
> > to find a section)
> >
> >
> > Wish me luck...
> >
> > --
> > You received this bug notification because you are subscribed to the bug
> > report.
> > https://bugs.launchpad.net/bugs/1771880
> >
> > Title:
> > Seahorse unable to import pkcs12 certificates
> >
> > Status in seahorse:
> > New
> > 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
> >
> >
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1771880
>
> Title:
> Seahorse unable to import pkcs12 certificates
>
> Status in seahorse:
> New
> 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
>
>