You are not logged in.
Pages: 1
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/keyringThe /.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 (Today 13:03:43)
Offline
IMHO: Forget gnome-keyring. Thunderbird writes into ".thunderbird".
Check the health and consistency of your "fancyonewithsubvolumessnapshotscompressionandwhatnot" filesystem.
Offline
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.
Offline
Pages: 1