You are not logged in.

#1 2025-11-04 07:44:46

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)

Offline

#2 2025-11-19 12:58:46

gabx
Member
From: Geneva, Switzerland
Registered: 2011-11-20
Posts: 245
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

Offline

#3 2025-11-19 13:59:36

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 74,420

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

You in the other thread wrote:

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

Offline

#4 2025-11-19 21:11:43

gabx
Member
From: Geneva, Switzerland
Registered: 2011-11-20
Posts: 245
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

Offline

#5 2026-04-10 05:55:19

mapuo
Member
Registered: 2026-03-05
Posts: 4

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

@gabx Can you share exactly how did you resolve your issue (that I also have after upgrading to gnome 50)?
The link that you've left is pointing to the same post and here I don't see the solution.

Offline

#6 2026-04-10 10:02:23

schard
Forum Moderator
From: Hannover
Registered: 2016-05-06
Posts: 2,614
Website

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

The solution is in this thread, namely post #3 in combination with post #4's last line.

Mod note: Closing.


Inofficial first vice president of the Rust Evangelism Strike Force

Offline

#7 2026-04-10 12:22:20

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 14,898

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

Moderator Note

I've read your report, mapuo .
Run printenv HOME , if it says anything else then /home/your-username it's set incorrectly.

In case you can't find out what sets the wrong value, start a new thread .
Include a copy of the output of journalctl -b (run as root) and feel free to link to this thread.

archwiki on uploading text has info how to upload text output to public hosting sites.

Lone_Wolf


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

Board footer

Powered by FluxBB