Questions[gnome-keyring](ubuntu)

I'm trying to import a certificate into seahorse/gnome-keyring on Ubuntu 18.04, but the seahorse gui application won't let me, the 'import' button is greyed out:

Screenshot

As seen in the screenshot, mouse hovering the "import" button shows the message "Cannot import because there are no compatible importers".

How can I fix it to be able to import certificates and keys to seahorse?

Because that problem, I'm currently unable to digitally sign documents with LibreOffice.

This problem doesn't occur on Ubuntu 16.04 LTS, as I've just tested on my wife's laptop, it happens only in my Laptop with Ubuntu 18.04 LTS.

Thanks.

I'm on 18.04 and have successfully enabled fingerprint login. I would like to use my fingerprint not only to login but if possible also to:

1. Authenticate in the terminal when I do a sudo command
2. Authenticate in Gnome (i.e. when installing an application etc)
3. Unlocking keyring items (this is the only point I could find info about and apparently this one is not possible)

Output of grep print /etc/pam.d -R:

/etc/pam.d/gdm-fingerprint:auth required    pam_fprintd.so
/etc/pam.d/gdm-fingerprint:password required       pam_fprintd.so

Content of /etc/pam.d/gdm-fingerprint

#%PAM-1.0
auth    requisite       pam_nologin.so
auth    required    pam_succeed_if.so user != root quiet_success
auth    required    pam_fprintd.so
auth    optional        pam_gnome_keyring.so
@include common-account
# SELinux needs to be the first session rule. This ensures that any 
# lingering context has been cleared. Without this it is possible 
# that a module could execute code in the wrong domain.
session [success=ok ignore=ignore module_unknown=ignore default=bad]        pam_selinux.so close
session required        pam_loginuid.so
# SELinux needs to intervene at login time to ensure that the process
# starts in the proper default security context. Only sessions which are
# intended to run in the user's context should be run after this.
session [success=ok ignore=ignore module_unknown=ignore default=bad]        pam_selinux.so open
session optional        pam_keyinit.so force revoke
session required        pam_limits.so
session required        pam_env.so readenv=1
session required        pam_env.so readenv=1 user_readenv=1 envfile=/etc/default/locale
@include common-session
session optional        pam_gnome_keyring.so auto_start
password required       pam_fprintd.so

Content of /etc/pam.d/sudo

#%PAM-1.0
session    required   pam_env.so readenv=1 user_readenv=0
session    required   pam_env.so readenv=1 envfile=/etc/default/locale user_readenv=0
@include common-auth
@include common-account
@include common-session-noninteractive

I read through all the related answers, but they do not apply to Ubuntu 14.04.

I have no .gnome2 folder and no Passwords and Encryption keys item in the system settings. I tried to crawl through every possible menu, but I could not find out how to do it.

The popup usually pops out when I start Chromium.

I am trying to start a program using wine on Ubuntu LTS 12.04 64 bit

When I do this, I get the following error message...

/usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux->gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or >directory

When I try to symlink the 64 bit libraries, of course, I get the following...

jackie@jackie-Latitude-E6410:~/tmp/AC$ wine TTG.exe
p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: 
/usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: wrong ELF class: ELFCLASS64
wine: Unhandled page fault on read access to 0x00000000 at address (nil) (thread 0009), 
starting debugger...
err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0x7bc47aac

Is there a package that installs the 32-bit as well as the 64bit?

UPDATE:

Appears to be a bug in Ubuntu w/ 1.4

https://launchpad.net/~ubuntu-wine/+archive/ppa

I used these steps and my application worked

http://www.noobslab.com/2012/04/install-wine-152-on-ubuntu.html

Not sure exactly why but it appears to ignore the error if you use the 1.5.

Can someone please explain what Ubuntu's keychain or keyring is, as well as use cases for it?