You are not logged in.
Hi all,
I've been using keepassxc as my libsecret service and everything was working fine. I changed essentially created a org.freedesktop.secrets.service file in ~.local/share/dbus-1/services pointing to keepassxc and it was started automatically when some application requested a secret. A recent update changed gnome-keyrings-daemon to start as a systemd service which caused to break my setup, because gnome-keyrings-daemon was now started first. Can someone point me to the reasoning behind this decision, it's a bit annoying to break user setups like that. And more importantly can someone tell me what the canonical way of specifying the default secret service is now? I've masked gnome-keyrings-daemon.service now, but that seems more like a hack.
<rant>
The whole autostart applications and default services of desktop environments is a mess. There is not good documentation and lots of conflicting advice. Moreover every couple of years everything is changed. Also it seems the large desktop environments (gnome/kde, but gnome seems to be worse), assume that you only every use their desktop and the gui to make any setting changes so they run roughshot over every manual configuration.
</rant>
Offline
Since you didn't share your 'org.freedesktop.secrets.service' file, I assume that you don't use the
[Unit]
Before=array which allows for "some" ordering of services (along with 'After=') - I'm not a systemd geek at all... EDIT: Nevermind - we're not talking about a systemd service here (you could try and edit 'gnome-keyring-daemon.service/socket', though...)
Last edited by dogknowsnx (2022-05-29 13:49:36)
Since you didn't share your 'org.freedesktop.secrets.service' file, I assume that you don't use the
[Unit]
Before=array which allows for "some" ordering of services (along with 'After=') - I'm not a systemd geek at all... EDIT: Nevermind - we're not talking about a systemd service here (you could try and edit 'gnome-keyring-daemon.service/socket', though...)
This is a bit confusing, as I understand it dbus service files are not the same as systemd service files, even though they are named the same. for the record here's my org.freedesktop.secrets.service file:
[D-BUS Service]
Name=org.freedesktop.secrets
Exec=/usr/bin/keepassxcI obviously could change the gnome-keyring-daemon.service/socket files, but that would get broken at every update to the file, so not really a sustainable solution. Moreover, it requires root, which the old method didn't. As I said I have made it work for now, by masking gnome-keyring-daemon.service but that seems suboptimal as well. If every desktop environment installs their keyrings/wallets and other services as systemd services I'll have to mask a lot of them.
Offline
I obviously could change the gnome-keyring-daemon.service/socket files, but that would get broken at every update to the file, so not really a sustainable solution. More'over, it requires root, which the old method didn't.
In case you change your mind/want to give it a shot - 'gnome-keyring-daemon.service' is a user service that can be edited by issuing
systemctl --user edit gnome-keyring-daemon.servicewhich would create
$HOME/.config/systemd/user/gnome-keyring-daemon.service.d/override.conf(Editing a system service would create a persistent system-wide '*.service.d/override.conf')
Last edited by dogknowsnx (2022-05-29 17:41:09)