Sovran_Systems/Sovran_SystemsOS
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix GNOME Keyring permission issue: move tmpfiles rules to user level

Browse Source 
Agent-Logs-Url: https://github.com/naturallaw777/staging_alpha/sessions/3ed85d6b-ada9-48e1-941f-1150e1491157

Co-authored-by: naturallaw777 <99053422+naturallaw777@users.noreply.github.com>
This commit is contained in:
copilot-swe-agent[bot]
2026-04-30 16:32:36 +00:00
committed by GitHub
parent 976d8f3609
commit bfc60eeb2c
1 changed files with 5 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
configuration.nix
+5 -7
View File
@@ -70,13 +70,11 @@
security.pam.services.gdm-password.enableGnomeKeyring = true;
security.pam.services.gdm-autologin.enableGnomeKeyring = true;
# Declaratively guarantee the GNOME Keyring default pointer exists.
# The 'f' directive creates the file only when it is absent, so legacy
# machines that already have a valid pointer are never overwritten.
# The content 'login' tells pam_gnome_keyring which keyring to unlock on login.
systemd.tmpfiles.rules = [
"d /home/free/.local/share/keyrings 0700 free users -"
"f /home/free/.local/share/keyrings/default 0600 free users - login\n"
# Declaratively guarantee the GNOME Keyring default pointer exists for the free user.
# Running this at the user level prevents root from corrupting ~/.local permissions on fresh installs.
systemd.user.tmpfiles.rules = [
"d %h/.local/share/keyrings 0700 - - - -"
"f %h/.local/share/keyrings/default 0600 - - - login\n"
];
# ── Audio ──────────────────────────────────────────────────