pam_gnome_keyring.so starts a new gnome-keyring-daemon every login
I use pam_gnome_keyring.so to start the gnome-keyring-daemon through SSHD login. I'm running on Fedora 28 with gnome-keyring-3.28.2-1.fc28
When I log into an SSH session, an instance of gnome-keyring-daemon is launched, regardless of whether a previous gnome-keyring-daemon is already running. Additionally, they do not seem to be reaped properly when the login session ends.
This is problematic, as I use the gnome-keyring-daemon as my SSH agent, and eventually the multiple gnome-keyring-dameons begin to conflict, preventing proper functionality of the SSH agent.
I also see the following message in the journal upon the first gnome-keyring-daemon being started:
gnome-keyring-daemon[...]: couldn't set environment variable in session GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Destination does not exist
Further more, once I log in again, I see the following:
gnome-keyring-daemon[...]: failed to unlock login keyring on startup gnome-keyring-daemon[...]: another secret service is running gnome-keyring-daemon[...]: couldn't set environment variable in session GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Destination does not exist
I'm suspicious that maybe somehow the failure to set up the environment leads to future sessions failing to notice that the gnome-keyring-daemon is already running.
I'm happy to collect any further debugging information requested, but I don't really know what to do next.