Failed to launch (could not create keychain: no keychain)

Question

Failed to launch (could not create keychain: no keychain)

foncused opened this issue a year ago · comments

Issue tracker is ONLY used for reporting bugs with technical details. "It doesn't work" or new features should be discussed with our customer support. Please use bug report function in Bridge or contact bridge@protonmail.ch.

Expected Behavior

protonmail-bridge should open and detect installed password manager.

Current Behavior

protonmail-bridge fails to launch in Arch Linux x86_64 kernel 6.6.2-arch1-1.
gnome-keyring-daemon is running.

2385400  0.0  0.0 386604  9344 ?        SLl  11:35   0:00 /usr/bin/gnome-keyring-daemon --start --foreground --components=secrets

Possible Solution

Steps to Reproduce

Download latest PKGBUILD
makepkg
pacman -U protonmail-bridge-bin-3.6.1-2-x86_64.pkg.tar.zst
protonmail-bridge (or protonmail-bridge -c)

Output:

WARN[0000] Failed to add test credentials to keychain    error="failed to create item: Object does not exist at path “/org/freedesktop/secrets/collection/login”" helper="*keychain.SecretServiceDBusHelper"
WARN[0000] Failed to add test credentials to keychain    error="Object does not exist at path “/org/freedesktop/secrets/collection/login”" helper="*secretservice.Secretservice"
INFO[0000] Migrating keychain helper                    
ERRO[Nov 28 12:19:13.385] Could not load/create vault key               error="could not create keychain: no keychain"
WARN[Nov 28 12:19:13.390] The vault key could not be retrieved; the vault will not be encrypted
...
Proton Mail Bridge is not able to detect a supported password manager
(secret-service or pass). Please install and set up a supported password manager
and restart the application.

Version Information

protonmail-bridge-bin 3.6.1-2
gnome-keyring 1:42.1-3
Qt 6.4.3

Context (Environment)

Detailed Description

Possible Implementation

LBeernaertProton · Answer 1 · Wed Nov 29 2023 17:06:46 GMT+0800 (China Standard Time)

Could you please post the output of:

dbus-send --session --dest=org.freedesktop.DBus --type=method_call --print-reply /org/freedesktop/DBus org.freedesktop.DBus.ListNames | grep secrets

foncused · Answer 2 · Wed Nov 29 2023 18:25:00 GMT+0800 (China Standard Time)

┌▪ [~]
└▪ dbus-send --session --dest=org.freedesktop.DBus --type=method_call --print-reply /org/freedesktop/DBus org.freedesktop.DBus.ListNames | grep secrets
      string "org.freedesktop.secrets"

LBeernaertProton · Answer 3 · Wed Nov 29 2023 18:28:09 GMT+0800 (China Standard Time)

Could you retry with the 3.71 pre-release version and see if the situation improves?

foncused · Answer 4 · Wed Nov 29 2023 18:36:49 GMT+0800 (China Standard Time)

No luck with protonmail-bridge-bin 3.7.1-1, I get the same output.

LBeernaertProton · Answer 5 · Wed Nov 29 2023 18:42:38 GMT+0800 (China Standard Time)

Is it possible the key ring is still locked? 🤔

foncused · Answer 6 · Wed Nov 29 2023 20:17:37 GMT+0800 (China Standard Time)

I managed to resolve this by looking over the Gnome/Keyring Arch wiki and running the following (meant for e.g. ~/.xinitrc): dbus-update-activation-environment --all

This is because I use i3.
With i3, this is better placed in ~/.config/i3/config: exec dbus-update-activation-environment --all

Then when running protonmail-bridge I was prompted to enter a default keychain credential and now Proton Mail Bridge opens as expected.

Thank you for your help.

F. Malina · Answer 7 · Wed Jan 10 2024 03:57:18 GMT+0800 (China Standard Time)

I am having the same issue and same error message and I don't use i3 and dbus-update-activation-environment --all does not resolve this for me.

$ dbus-send...
    string "org.freedesktop.secrets"

foncused · Answer 8 · Wed Jan 10 2024 04:29:40 GMT+0800 (China Standard Time)

@fmalina Are you using another window manager environment? I only ask because my solution is not technically i3 specific. If you are, and you can execute commands from its startup configuration:

If you are using sway, i3, or any window manager that does not execute

/etc/xdg/autostart/gnome-keyring-*.desktop
/etc/X11/xinit/xinitrc.d/50-systemd-user.sh
your window manager needs to execute the following commands during window manager startup. The commands do not need to be executed in any specific order.

dbus-update-activation-environment DISPLAY XAUTHORITY WAYLAND_DISPLAY
or

dbus-update-activation-environment --all

F. Malina · Answer 9 · Wed Jan 10 2024 04:43:28 GMT+0800 (China Standard Time)

I don’t use a window manager on this box at all, just a terminal. I used to use the bridge for sending password reset and signup welcome emails to my users, now I changed unlimited plan to business and I'll try SMTP instead

okanisis · Answer 10 · Mon Feb 05 2024 02:58:02 GMT+0800 (China Standard Time)

I'm on arch linux using KDE with protonmail bridge 3.8.2.

Here's the output after trying dbus-update-activation-environment --all:

Feb 04 11:55:35 systemd[2034]: Started ProtonMail Bridge - ProtonMail IMAP and SMTP Bridge.
Feb 04 11:55:35 protonmail-bridge-core[93894]: time="2024-02-04T11:55:35-07:00" level=info msg="Migrating keychain helper"
Feb 04 11:55:35 protonmail-bridge-core[93894]: WARN[Feb  4 11:55:35.342] Keychain is not available.                    keychain=SecretService