Sheikh Limon

@DOsinga I am currently trying to apply for the Builder Fellowship Program on Block, so I'm gonna get a PR in for you to check when I'm done finalizing the...

I've been looking at the code and the keyring error happens in `try_store_secret()` in `configure.rs`. We could detect the keyring failure and automatically fall back to file-based storage with a...

> yeah that makes sense. hadn't heard of Builder Fellowship Program on Block - I'm not involved but feel free to mention my name if relevant will do... thank you...

Working as I test it. Anyways, I have made changes to handle the error gracefully, and add automatic fallback to file-based storage when keyring is unavailable. Currently testing the fix...

> well, weird behavior from systemctl: > > ``` > % systemctl --user enable gcr-ssh-agent.socket > Failed to enable unit: Unit /.config/systemd/user/sockets.target.wants/gcr-ssh-agent.socket does not exist > > % ls -al...

> Both are installed > > ``` > gabx@magnolia ➤➤ share/keyrings % systemctl --user status gnome-keyring-daemon.socket > ● gnome-keyring-daemon.socket - GNOME Keyring daemon > Loaded: loaded (/usr/lib/systemd/user/gnome-keyring-daemon.socket; enabled; preset: enabled)...

@The-Best-Codes I just noticed the previous PR addressing this. But shouldn't quotes be the standard approach? Edit: #5868 I guess this was a linux and ui problem since it's placed...

Thanks for the clarification! Yes, using `${HOME}` instead of `~` absolutely fixes the original issue. `~` does not expand inside quotes in POSIX shells, so switching to `${HOME}` was the...

Good point. The rest of the paths are hard-coded, but quoting is still recommended because ${HOME} itself is user-controlled and the entire expansion is subject to word splitting or globbing...

@DOsinga, this fix should work. I tested this using LLM, but wasn't able to replicate the said error on my machine as yesterday. Tried disabling even the keyring, but `goose...