[SOLVED]gnome-keyring potential issues

gabx · Yesterday 12:45:00

Since a few days, I have some weird behaviors on my system. No idea why, but if I am right, these issues comes after I had to edit /etc/subgid, /etc/subuid and made some user group changes . I manage my home folder with homectl
One example of issue is with evolution mail client. It worked very well and after a reboot, when I started the app, I found empty mail folders and my account settings have been removed. I created a new account entry, but when the setup was finished, nothing have been done and a pop up appeared with this content: Error creating directory /.config: Permission denied.
I have read/write access to my .config folder and all rights looks correct at first glance.

My overall machine works well, but I try to figure out why this issue. Looking at gnome keyring, I found this potential issue:

 % systemctl --user status gnome-keyring-daemon.service
● gnome-keyring-daemon.service - GNOME Keyring daemon
     Loaded: loaded (/usr/lib/systemd/user/gnome-keyring-daemon.service; disabled; preset: enabled)
     Active: active (running) since Mon 2025-11-17 13:57:50 CET; 1 day 23h ago
 Invocation: 83d6ee35560a49bb8e096fe1cbfd9208
TriggeredBy: ● gnome-keyring-daemon.socket
   Main PID: 3978 (gnome-keyring-d)
      Tasks: 5 (limit: 37973)
     Memory: 3M (peak: 3.8M)
        CPU: 359ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/gnome-keyring-daemon.service
             └─3978 /usr/bin/gnome-keyring-daemon --foreground --components=pkcs11,secrets --control-directory=/run/user/1000/keyring

Nov 19 11:12:29 magnolia gnome-keyring-daemon[3978]: couldn't delete aborted file, data may be lost: /.local/share/keyrings/login.keyring: No such file or directory
Nov 19 11:12:29 magnolia gnome-keyring-daemon[3978]: couldn't create login keyring: An error occurred on the device
Nov 19 12:06:19 magnolia gnome-keyring-daemon[3978]: couldn't write to file: /.local/share/keyrings/login.keyring: No such file or directory
Nov 19 12:06:19 magnolia gnome-keyring-daemon[3978]: couldn't delete aborted file, data may be lost: /.local/share/keyrings/login.keyring: No such file or directory
Nov 19 12:06:19 magnolia gnome-keyring-daemon[3978]: couldn't write to file: /.local/share/keyrings/login.keyring: No such file or directory
Nov 19 12:06:19 magnolia gnome-keyring-daemon[3978]: couldn't create login keyring: An error occurred on the device
Nov 19 12:06:19 magnolia gnome-keyring-daemon[3978]: couldn't delete aborted file, data may be lost: /.local/share/keyrings/login.keyring: No such file or directory
Nov 19 12:06:19 magnolia gnome-keyring-daemon[3978]: couldn't create login keyring: An error occurred on the device
Nov 19 13:23:43 magnolia gnome-keyring-daemon[3978]: The Secret Service was already initialized
Nov 19 13:23:43 magnolia gnome-keyring-daemon[3978]: The Secret Service was already initialized

----

% ps -ef | grep gnome-keyring
343:trollolo  110496  110469  0 Nov17 ?        00:00:00 /usr/bin/gnome-keyring-daemon --foreground --components=pkcs11,secrets --control-directory=/run/user/60094/keyring
613:gabx     1528708     955  0 13:57 ?        00:00:00 /usr/bin/gnome-keyring-daemon --foreground --components=pkcs11,secrets --control-directory=/run/user/1000/keyring

The /.local/share/keyrings/login.keyring file exists and is owned by me with rw attributes.
Why this gnome-keyring message? How to debug it?
Thank you for help

Last edited by gabx (Yesterday 20:44:25)

-thc · Yesterday 13:42:53

IMHO: Forget gnome-keyring. Thunderbird writes into ".thunderbird".

Check the health and consistency of your "fancyonewithsubvolumessnapshotscompressionandwhatnot" filesystem.

seth · Yesterday 14:00:18

You probably want to report this as duplicate of https://bbs.archlinux.org/viewtopic.php?id=309974 and continue over there to concentrate the efforts.

gabx · Yesterday 18:51:14

seth wrote:

You probably want to report this as duplicate of https://bbs.archlinux.org/viewtopic.php?id=309974 and continue over there to concentrate the efforts.

sure

gabx · Yesterday 18:52:55

-thc wrote:

IMHO: Forget gnome-keyring. Thunderbird writes into ".thunderbird".
Check the health and consistency of your "fancyonewithsubvolumessnapshotscompressionandwhatnot" filesystem.

I don't understand at all your thunderbird story, sorry! Any reason to forget gnome-keyring? Bloated? Broken?

-thc · Yesterday 19:34:11

Never mind.

gabx · Yesterday 20:29:58

I have been confused by /.local/share/keyrings/login.keyrings and ~/.local/share/keyrings/login.keyrings. The first doesn't exist for sure ! I own the second one.
So I don't understand why gnome-keyring is trying to write to /.local: Any typo in some of my configuration file?
I find another weird entry in XDG_DATA_DIRS: /.local/share/flatpak/exports/share . Again an entry with this /.local folder.

% systemctl --user show-environment | grep HOME
2:HOME=/    <--- NOT GOOD
% systemctl --user import-environment HOME
% gabx@magnolia ➤➤ ~ % systemctl --user show-environment | grep HOME
2:HOME=/home/gabx
systemctl --user status gnome-keyring-daemon.service
● gnome-keyring-daemon.service - GNOME Keyring daemon
     Loaded: loaded (/usr/lib/systemd/user/gnome-keyring-daemon.service; disabled; preset: enabled)
     Active: active (running) since Wed 2025-11-19 21:39:48 CET; 7s ago
 Invocation: 6f2af6248d7c41d1b5b2b7315966d30e
TriggeredBy: ● gnome-keyring-daemon.socket
   Main PID: 1674961 (gnome-keyring-d)
      Tasks: 5 (limit: 37973)
     Memory: 2M (peak: 2.5M)
        CPU: 19ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/gnome-keyring-daemon.service
             └─1674961 /usr/bin/gnome-keyring-daemon --foreground --components=pkcs11,secrets --control-directory=/run/user/1000/keyring

Nov 19 21:39:48 magnolia systemd[955]: Started GNOME Keyring daemon.
Nov 19 21:39:48 magnolia gnome-keyring-daemon[1674961]: gnome-keyring-daemon: no process capabilities, insecure memory might get used
Nov 19 21:39:48 magnolia gnome-keyring-daemon[1674961]: GNOME_KEYRING_CONTROL=/run/user/1000/keyring

Issue is solved

Last edited by gabx (Yesterday 20:43:48)

seth · Yesterday 20:32:14

XDG_DATA_DIRS: /.local/share/flatpak/exports/share

is most likely the flatschpak fuckup that causes this (hence the request for printenv in the other thread…)
Figure where that's set and fix that, https://wiki.archlinux.org/title/Environment_variables
Also probably post the entire printenv output - at least everything that has some sort of path in it.

Arch Linux

#1 Yesterday 12:45:00

[SOLVED]gnome-keyring potential issues

#2 Yesterday 13:42:53

Re: [SOLVED]gnome-keyring potential issues

#3 Yesterday 14:00:18

Re: [SOLVED]gnome-keyring potential issues

#4 Yesterday 18:51:14

Re: [SOLVED]gnome-keyring potential issues

#5 Yesterday 18:52:55

Re: [SOLVED]gnome-keyring potential issues

#6 Yesterday 19:34:11

Re: [SOLVED]gnome-keyring potential issues

#7 Yesterday 20:29:58

Re: [SOLVED]gnome-keyring potential issues

#8 Yesterday 20:32:14

Re: [SOLVED]gnome-keyring potential issues

Board footer