I am seeing the following warning in my logs:
level=warning msg="Failed to add test credentials to keychain" error="Cannot create an item in a l ocked collection" helper="*secretservice.Secretservice"
It seems the systemd service is starting too early. I have GNOME configured for auto-login but still need to unlock the keychain on startup. Is it possible to modify the provided unit in a way that it only starts after the keychain is successfully unlocked?
Pinned Comments
luoe commented on 2023-02-25 15:59 (UTC)
When using kwallet as provider for org.freedesktop.secrets and pass for key backend for the bridge, I've needed to add a delay before starting the systemd unit after login.
systemctl --user edit --full bridge.service
Else the starting of the bridge might fail because kwallet isn't unlocked instantly after login and the GPG key for the pass repo thus is locked (Editing the systemd unit file will skip the need for manual input of the passphrase for the GPG key)
mclancy commented on 2020-06-15 16:35 (UTC)
hakayova and grimfrenzy: I managed to solve the issue of "no account found" by providing the correct PASSWORD_STORE_DIR to the systemd service.
In my case I provided: Environment="PASSWORD_STORE_DIR=/home/mclancy/.local/share/pass"
Hope this helps!
kausban commented on 2020-04-21 14:37 (UTC) (edited on 2020-04-21 14:37 (UTC) by kausban)
Minimal fork of https://aur.archlinux.org/packages/protonmail-bridge/
Compiled with 'nogui' option
Included is a user systemd service. Try: systemctl status --user bridge.service
The following is an alternative way to run the bridge in interactive cli mode encapsulated within a named screen session. Can be added to bridge.service