Arch Linux

wannabee

Member

Registered: 2023-12-22

Posts: 10

gnome-keyring-daemon is using the wrong prefix on the first login

When i login to my gnome desktop using gdm gnome-keyring-daemon fails to load my keyrings.

It seems that it is trying to load the keyrings but using a wrong prefix:

● gnome-keyring-daemon.service - GNOME Keyring daemon
     Loaded: loaded (/usr/lib/systemd/user/gnome-keyring-daemon.service; disabled; preset: enabled)
     Active: active (running) since Sat 2025-11-01 09:19:42 CET; 17s ago
 Invocation: a5b2ac60ae144ab5980018f78cc70db0
TriggeredBy: ● gnome-keyring-daemon.socket
   Main PID: 2740 (gnome-keyring-d)
      Tasks: 5 (limit: 76494)
     Memory: 1.4M (peak: 2.6M)
        CPU: 55ms
     CGroup: /user.slice/user-60156.slice/user@60156.service/app.slice/gnome-keyring-daemon.service
             └─2740 /usr/bin/gnome-keyring-daemon --foreground --components=pkcs11,secrets --control-directory=/run/user/60156/keyring

Nov 01 09:19:42 simonlaptop gnome-keyring-daemon[2740]: unable to create keyring dir: /.local/share/keyrings
Nov 01 09:19:42 simonlaptop gnome-keyring-daemon[2740]: unable to create keyring dir: /.local/share/keyrings
Nov 01 09:19:42 simonlaptop gnome-keyring-daemon[2740]: unable to create keyring dir: /.local/share/keyrings
Nov 01 09:19:42 simonlaptop gnome-keyring-daemon[2740]: unable to create keyring dir: /.local/share/keyrings
Nov 01 09:19:42 simonlaptop gnome-keyring-daemon[2740]: couldn't write to file: /.local/share/keyrings/login.keyring: No such file or directory
Nov 01 09:19:42 simonlaptop gnome-keyring-daemon[2740]: couldn't write to file: /.local/share/keyrings/login.keyring: No such file or directory
Nov 01 09:19:42 simonlaptop gnome-keyring-daemon[2740]: couldn't delete aborted file, data may be lost: /.local/share/keyrings/login.keyring: No such file or directory
Nov 01 09:19:42 simonlaptop gnome-keyring-daemon[2740]: couldn't delete aborted file, data may be lost: /.local/share/keyrings/login.keyring: No such file or directory
Nov 01 09:19:42 simonlaptop gnome-keyring-daemon[2740]: couldn't create login keyring: An error occurred on the device
Nov 01 09:19:42 simonlaptop gnome-keyring-daemon[2740]: couldn't create login keyring: An error occurred on the device
[simon@simonlaptop home]$ systemctl --user enable gnome-keyring-daemon
Failed to enable unit: Unit /.config/systemd/user/default.target.wants/gnome-keyring-daemon.service does not exist

I am using systemd-homed and when i logout and login again everything is working fine.
How can i best debug this? Am i missing a service that i need to enable?

Last edited by wannabee (2025-11-04 07:47:27)

gabx

Member

From: Geneva, Switzerland

Registered: 2011-11-20

Posts: 231

Website

Re: gnome-keyring-daemon is using the wrong prefix on the first login

did you solved your issue? I have same one on my machine

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 70,360

Re: gnome-keyring-daemon is using the wrong prefix on the first login

Nov 01 09:19:42 simonlaptop gnome-keyring-daemon[2740]: unable to create keyring dir: /.local/share/keyrings
Nov 01 09:19:42 simonlaptop gnome-keyring-daemon[2740]: couldn't write to file: /.local/share/keyrings/login.keyring: No such file or directory

looks like a broken $HOME

The /.local/share/keyrings/login.keyring file exists and is owned by me with rw attributes.

Really?

stat /.local

That is a directory directly under the root partition and you should™ not own anything there.
This should™ be ~/.local/share/keyrings

printenv

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

gabx

Member

From: Geneva, Switzerland

Registered: 2011-11-20

Posts: 231

Website

Re: gnome-keyring-daemon is using the wrong prefix on the first login

I solved my issue as explained here: https://bbs.archlinux.org/viewtopic.php?id=309974
The HOME variable was not set correctly as returned by

systemctl --user show-environment | grep HOME

I found HOME=/ instead of HOME=/home/gabx