Comment 2 for bug 119263

Yep, you are right.

However, if I recall correctly, my fault was that I did not know that KGpg does not create the ${HOME}/.gnupg/gpg.conf file (it is not able to create it if the file does not exist - hence any changes in the settings, which relate to gpg.conf are ignored - like "use gpg agent").

Therefore I created the gpg.conf manually. Further KGpg had default option to search ${HOME}/.gnupg/options.cfg - which is not the default name for gnupg configuration file, neither. To solve it, I tried to set the pgp.conf manually and the result was the bug above.

Maybe there is some way how KGpg rescans the preset ${HOME}/.gnupg directory to find the new pgp.conf without the need to open the directory browser window, but I have not discovered it.