gnome-keyring does not autostart in Zorin OS (OnlyShowIn mismatch)

[jjdeharo]

On Zorin OS 17.3 Core, the gnome-keyring daemon does not autostart correctly when logging into the desktop session.

Cause:

• Zorin sets the desktop identifier as XDG_CURRENT_DESKTOP=zorin:GNOME.

• The autostart files in /etc/xdg/autostart/gnome-keyring-*.desktop contain:

  OnlyShowIn=GNOME;Unity;MATE;
  

• Because of this mismatch, gnome-keyring does not start automatically.

Symptoms:

• Delay (~20 seconds) when opening a terminal.

• Errors in logs:

  • gkr-pam: unable to locate daemon control file
  • gkr-pam: couldn't unlock the login keyring

• Multiple or missing gnome-keyring-daemon processes.

Workaround:
Copy the files to ~/.config/autostart/ and remove the OnlyShowIn line:

mkdir -p ~/.config/autostart
cp /etc/xdg/autostart/gnome-keyring-*.desktop ~/.config/autostart/
sed -i '/^OnlyShowIn=/d' ~/.config/autostart/gnome-keyring-*.desktop

Suggestion:
Please update the .desktop files in Zorin so they either include ZORIN in OnlyShowIn, or remove the line (as in Ubuntu). This would allow gnome-keyring to autostart properly without user intervention.

Environment:

• Zorin OS 17.3 Core (64-bit)
• Wayland session
• Intel Core i7-1360P (13th Gen)
• 32 GB RAM
• Mesa Intel Graphics (RPL-P)
• 500 GB SSD

[zenzen]

The definition for the entries "OnlyShowIn" and "NotShowIn" as per the XDG Desktop Entry Specification state:

If $XDG_CURRENT_DESKTOP is set then it contains a colon-separated list of strings. In order, each string is considered.

This means that the desktop files are valid and correctly configured. And I can see that Gnome Keyring does start normally for me without any changes. No delay in launching the terminal, either.

I suspect you may be experiencing a different issue... although the workaround you found is interesting, and possibly related.