UDPATE:
I’m closer to the problem. After wiping the drive and rebuilding system VS Code ran fine, except I was receiving a Keyring error. Something like “Keyring does not match login password”. It rejected my login password although it’s the only one I’ve set up since starting.
This post suggested the fix was:
environment.variables.XDG_RUNTIME_DIR = "/run/user/$UID"; # set the runtime directory
I tried that, which then caused VS Code to stop working with the same error as previously:
[ian@nixos:~/.nixos_working]$ code .
Warning: ‘ozone-platform-hint’ is not in the list of known options, but still passed to Electron/Chromium.
Warning: ‘enable-features’ is not in the list of known options, but still passed to Electron/Chromium.
I then removed the above line and ran nixos-rebuild, but the problem hasn’t resolved. Note, I also tried with, and without, the other code block referenced:
services.gnome.gnome-keyring.enable = true;
programs.seahorse.enable = true; # enable the graphical frontend
environment.systemPackages = [ pkgs.libsecret ]; # libsecret api needed
security.pam.services.gdm.enableGnomeKeyring = true; # load gnome-keyring at startup
which all seems to provide me with the correct keyring configuration
ps aux | grep gnome-keyring-daemon
user1 1968 0.0 0.0 311520 6708 ? Sl 15:06 0:00 /nix/store/grp8lr0h0hwflb21arri2yddkbjjzv2c-gnome-keyring-46.2/bin/gnome-keyring-daemon --daemonize --login
user1 3883 0.0 0.0 6684 2688 pts/0 S+ 15:08 0:00 grep gnome-keyring-daemon
Any ideas on where to start?