split-gpg2 with a passphrase is not loaded into agent until listing the keys from the server

[ben-grande]

Qubes OS release

R4.2

Brief summary

I do not care much about passphrase in the gpg key, but as I was testing, I discovered something.

Keys are only loaded to split-gpg2 server (using isolated gnupg homedir) after they have been accessed first, such as gpg --homedir ~/.gnupg/split-gpg/dev -k >/dev/null.

I have tested this without isolated homedir and it also happens.

Steps to reproduce

1. Generate a key with a passphrase on the split-gpg2 server.
2. Import the public key of said key to the split-gpg2 client.
3. Restart the server.
4. Try to access the private key from the client will fail (not list the key at all), pinentry will not be called (using a GUI such as pinentry-gnome3 or pinentry-fltk or pinentry-qt).
5. On the server, do a simple operation on the correct gnupg homedir such as gpg --homedir ~/.gnupg/split-gpg/dev -k >/dev/null
6. On the client, try to access the private key with gpg -K will call the GUI pinentry, entering a correct password will list the key.

Expected behavior

Load private keys on keyrings even with passphrases when calling qubes.Gpg2.

Actual behavior

Accessing the passphrase protected private key fails unless you access it on the server first (listing the keyring, not the key specifically, is enough).