ProtonMail / proton-bridge

Proton Mail Bridge application
GNU General Public License v3.0
1.15k stars 156 forks source link

Bridge takes 3 minutes to startup unless gnome-keyring-daemon is killed beforehand #472

Open g-regex opened 5 months ago

g-regex commented 5 months ago

Hi! Since I have started using proton-mail-bridge (about 2 years ago), I have been experiencing this issue with every version of the bridge (currently 3.10.0):

When gnome-keyring-daemon is running, the bridge takes about 3 minutes to startup, reporting warnings that it failed to add test credentials. If gnome-keyring-daemon is not running, the bridge starts up without any delay.

Behaviour with gnome-keyring-daemon running (added the date command to show the delay):

$ date +%H:%M:%S && proton-mail-bridge -c
23:02:43
INFO[0000] Migrating keychain helper
WARN[Apr 19 23:03:44.539] Failed to add test credentials to keychain    error="timed out after 10s" helper="*keychain.SecretServiceDBusHelper"
WARN[Apr 19 23:05:59.136] Failed to add test credentials to keychain    error="Error calling StartServiceByName for org.freedesktop.secrets: Timeout was reached" helper="*secretservice.Secretservice"

            Welcome to Proton Mail Bridge interactive shell

Behaviour when killing gnome-keyring-daemon beforehand:

$ date +%H:%M:%S && killall gnome-keyring-daemon && proton-mail-bridge -c
23:19:27
INFO[0000] Migrating keychain helper

            Welcome to Proton Mail Bridge interactive shell

System information

proton-mail-bridge version: 3.10.0 (built from source) System uname: Linux-6.6.21-gentoo-x86_64-Intel-R-_Core-TM-_i5-5250U_CPU_@_1.60GHz-with-glibc2.38

Versions of dependencies:

I have searched the GitHub issues but could not find anything similar. Is this a known problem and, if so, is there a better workaround (or fix) than killing gnome-keyring-daemon?