Created attachment 1749827 [details] /varlog/messages snippet for the VNC scenario Description of problem: gnome-keyring-daemon fails to lock the keyring in GNOME sessions started from a remote display, either via VNC or XDMCP Version-Release number of selected component (if applicable): gnome-keyring-pam-3.28.2-1.el8.x86_64 gnome-keyring-3.28.2-1.el8.x86_64 seahorse-3.20.0-9.el8.x86_64 (for tests) How reproducible: Always Steps to Reproduce: 1. Configure remote access via VNC and/or XDMCP, following the instructions in at least one of these documents: - How do I setup VNC based on xinetd with XDMCP for GDM? https://access.redhat.com/solutions/2516 - How to configure a RHEL to allow remote access to GDM via XDMCP? https://access.redhat.com/solutions/2736 - Are there any changes to the default vncserver configuration in RHEL8.3? https://access.redhat.com/solutions/5544351 Notice that the three access methods can be configured simultaneously on the same machine. 2. Start the VNC session or log in via GDM 3. Open the "Passwords and Keys" application (seahorse) a "Login" tab should appear. Actual results: The the "Login" does not appear. Expected results: The the "Login" does not appear in searhorse. Additional info: Attaching /var/log/messages snippets corresponding to the three scenarios. The problem can be partially circumvented by adding an autostart file at /etc/xdg/autostart/gnome-keyring-replace.desktop that replaces the running daemon but it does not automatically unlock the keyring, since there is no secure way to provide the user password.
Created attachment 1749829 [details] /varlog/messages snippet for the VNC + xinetd + XDMCP scenario
Created attachment 1749830 [details] /varlog/messages snippet for the XDMCP scenario
Created attachment 1749831 [details] /etc/xdg/autostart/gnome-keyring-replace.desktop workaround
I am able to reproduce this, workaround also works.