[SOLVED] Gnome Keyring lost GPG support after update

[r7l]

Hello,

after a recent update, i've lost GPG support in Gnome Keyring. There was a minor update of gnome-keyring but it was only from gnome-keyring-42.1-r1 to gnome-keyring-42.1-r2. The keys are still there and i can see them with Seahorse but i need to enter a password every time i want to use those keys. It was working without this password popup before.

After some digging i've noted that the environment variable "GPG_AGENT_INFO" is missing now. I have another system where i haven't done the updates yet and the variable is set there and everything is working as expected. Anyone knows where this variable is set in Gentoo? I am currently assuming this might be the cause.

Thanks in advance for any help.

[sam_]

Do you have USE=gnome-keyring set on sys-auth/pambase?

[r7l]

Yes i have. This hasn't changed and sys-auth/pambase hasn't been updated or reinstalled for almost a year.

When doing a grep over /etc/pam.d i can see this:

[r7l]

The situation resolved itself. There were a couple changes with new keyring USE flags recently and i've updated them accordingly. It does work as before again.

[sunox]

Could you please describe what you did to get it working again? I believe I am facing the same problem. In trying to find a solution I noticed the new 'keyring' use flag for pinentry which I have enabled.

[r7l]

I haven't done much except for setting USE flags accordingly / selectively where i need it. There are still packages using gnome-keyring while others have keyring. Like sys-auth/pambase which still has gnome-keyring and app-crypt/pinentry only has keyring. I am not even sure if both always meant to be for the same thing.

Other then that i have not changed much. No local gnupg settings apart from defaults in /etc/gnupg. But i have to admit that it's still not working perfectly. I always have to manually trigger SSH keys once after boot. I am not able to login with scripts (like Ansible) right away to run stuff remotely without spinning up a terminal and SSH somewhere first. After that, it works as expected for the rest of the session and doesn't even matter if it would be a different SSH key for different hosts. All of them work once i've used one of them.

[sunox]

Thanks for the response.

I added the 'keyring' USE for qtkeychain which seems to enable Nextcloud to make use of the keyring. It seems that gpg is able to make use of the keyring now without me doing anything? ¯\_(ツ)_/¯ Who knows! Anyway thank you again.