Unlocking cosmic with fingerprint does not prompt for keyring password

[NateWright]

I am using cosmic on NixOS unstable. When I unlock with a password after forcing fingerprint auth to fail, then it successfully unlocks gnome-keyring. If I use my fingerprint to unlock, then it does not prompt to unlock gnome-keyring (like gnome would) and I cannot unlock it from seahorse. I am not sure if this is a nixos-cosmic issue or a cosmic one.

[NateWright]

Manually starting gnome-keyring has this error.

[nwright@nwright-framework:~]$ gnome-keyring-daemon --replace --foreground --components=secrets
discover_other_daemon: 0** Message: 11:35:05.914: Replacing daemon, using directory: /run/user/1001/keyring
GNOME_KEYRING_CONTROL=/run/user/1001/keyring

** (gnome-keyring-daemon:5017): WARNING **: 11:35:28.397: couldn't create system prompt: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.keyring.SystemPrompter exited with status 1

[ChanceHarrison]

I am able to reproduce this issue.

Reading the Arch Wiki's page on GNOME Keyring pointed me to the issue. Paraphrasing/extrapolating accordingly:

The problem is that someone (ideally cosmic-session, maybe nixos-cosmic, or you can do it yourself) needs to update the DBus activation environment with the appropriate variables so the GUI prompts (e.g., for a password) can be triggered accordingly.

If you run dbus-update-activation-environment DISPLAY XAUTHORITY WAYLAND_DISPLAY (or -all) you should be able to see system prompts when invoked. You may also need to restart gnome-keyring-daemon.

Aside from upstream "fixing" this, it is still an open question in my mind as to what to do about it in nixos-cosmic.

I tried adding ${lib.getBin pkgs.dbus}/bin/dbus-update-activation-environment --all as a preStart on the cosmic-greeter-daemon.service), but it wasn't happy about this because it seems that units/services don't get populated with the expected environment variables.

I was able to use home manager to add that line to my .zshrc (my user's login shell) as initExtra and it solved my issue, but I'm sure there must be something better.