Arch Linux

Jocomol

Member

From: Switzerland

Registered: 2022-07-13

Posts: 35

Website

[Solved] Systemctl daemons unable to access gnome-keyring?

I've recently bought a new laptop on which, after I learned that it is optimal to have a secret service, I installed gnome-keyring which solved a multitude of issues I experienced with my earlier setup. Unfortunately the change also caused one error which makes me unable to recieve my email. I am using https://aur.archlinux.org/packages/prot … idge-nogui to sync with my protonmail account. protonmail-bridge needs access to a secret-service or pass. In my latests setups I used pass and all worked well. It also works well when I start the bridge explicitely from my CLI. But whenever I start the supplied daemon, I get the error message that the secret-service could not be used "Failed to add test credentials to keychain". Unfortunately I also seem to be unable to find out how to force this daemon to use pass instead of the installed secret-service.

Now my questions:
- Is it normal for systemd daemons to be unable to access the secret-service? If yes how can I work around this?
- What would be the solution for this specific issue?

I am glad to get some help and I am happy to post more infos or debug files.

Thank you

Last edited by Jocomol (2023-08-25 15:17:45)

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 13,408

Re: [Solved] Systemctl daemons unable to access gnome-keyring?

are you starting the bridge.service as a user service ?

https://wiki.archlinux.org/title/Systemd/User may be helpful.

Last edited by Lone_Wolf (2023-08-15 17:19:16)

---

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

Jocomol

Member

From: Switzerland

Registered: 2022-07-13

Posts: 35

Website

Re: [Solved] Systemctl daemons unable to access gnome-keyring?

I've skipped through the titles of the article but couldn't find anything which could help me. Do you have a specific section in mind?

Trilby

Inspector Parrot

Registered: 2011-11-29

Posts: 30,341

Website

Re: [Solved] Systemctl daemons unable to access gnome-keyring?

It's not a long page.  The whole thing applies.  You need to run your mail service as a user service not a system service.  (okay, really sections 1-3 as everything after that is specific examples / troubleshooting.  Note that your use case is listed in the second sentence on that page.)

Last edited by Trilby (2023-08-15 18:43:31)

---

"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Jocomol

Member

From: Switzerland

Registered: 2022-07-13

Posts: 35

Website

Re: [Solved] Systemctl daemons unable to access gnome-keyring?

Sorry I forgot to mention that, yes I am using it as a user service and not a system service. I was hoping to find something under 2.1 Environment variables but found nothing applicable. In the meantime I think I got it to work via pass by setting the password-store env var which would solve the issue for me but I still would be interested why the daemon wasn't able to use the gnome-keyring.

ayekat

Member

Registered: 2011-01-17

Posts: 1,617

Re: [Solved] Systemctl daemons unable to access gnome-keyring?

"Failed to add test credentials to keychain".

Is there more than that (a reason or something) in the error message? Could you please post the full logs for the service when it starts up (and fails)?

Does your systemd user instance have DISPLAY set?

systemctl --user show-environment

If yes, does the problem appear if you start the service manually, or only if you enable the service to auto-start with your systemd user instance?

(note: I'm currently suspecting what's described here)

---

pkgs │ hacks │ cfg │ blag

Jocomol

Member

From: Switzerland

Registered: 2022-07-13

Posts: 35

Website

Re: [Solved] Systemctl daemons unable to access gnome-keyring?

sytemctl --user show-environment: http://0x0.st/HLmY.txt

The problem appears in every case when bridge is started as a service