Comment 9 for bug 1577198

Ok! So the bug is still here but for me a little bit different. Being on Ubuntu 19.10 with its own Gnome the situation is the following.

Originally the system has just 'gpg' not 'gpg2' BUT basically the original 'gpg' is 'gpg2' as it's version is 'gpg (GnuPG) 2.2.12'. After installing gpg2 there is no so much change it just gave me a symlink from 'gpg2' to the system original 'gpg'. So basically now on 19.10 the 2 gpg is the same.

Let's check the keyring thingie. It is not too surprising that both of them use the same home dir: 'Home: /home/{user}/.gnupg' and of course the same keyring: /home/{user}/.gnupg/pubring.kbx. And because between the 2 thing there is any differences.

So what about Seahorse. Ubuntu 19.10 has 'Seahorse 3.32.2'. If I import a key from CLI through 'gpg' or 'gpg2' the key will be available int the mentioned keyring and CLI gpg can use it. But if I import the key from the Seahorse GUI the result what you all mentioned. Seems succeed but after the 'successfully imported' message there is no new key in Seahorse. Moreover the successfully imported key is also not in the gpg keyring verifying from CLI. Seahorse tells the everything ok on the import but the corresponding key is nowhere.

BUT! if you restart your gnome user session, VOILA the missing key appearing in Seahorse.

Sadly restarting the seahorse daemon not do the work so we really need to logout and login again.

This is very interesting as seems Seahorse not use directly the gpg keyring (something like PAM in Samba processes what otherwise I never understand completely), but a maintainer process sync their content.

So what I (we) know now that Seahorse simply not use gpg keyring as I simply import anything in vain in Seahorse that not appear in gpg keyring verified from CLI (and as the topic bug tells it also sadly not appear in Seahorse itself:D but in this case who know were are they?!...). Also in vain, if I imported anything in CLI gpg, the result is perfect in CLI gpg, but not appear in Seahorse.

And partly therefore the other thing is the conclusion, that Seahorse use 2 different backend for itself and those both are different from CLI gpg keyring (what is not so nice). One backend is used by the GUI and another is in real processes. And what I can see that the 2 backend sync each other at user login (something like as PAM with Samba).

Very interesting working method and it would be really nice to have a fix on it as the current result is more then uncomfortable. But if at least the GUI could communicate this also would be more than nothing.

Thanks for your attention and efforts also in advance!