"Failed to launch" errors

[Hampo]

With no changes, I got a "Failed to launch" error on 25th Feb. When I noticed today and tried to restart, I got the same error:

FATA[Feb 25 15:08:59.795] Failed to launch                              error="exit status 127" exe_path=/root/.local/share/protonmail/bridge-v3/updates/3.22.0/bridge exe_to_launch=bridge launcher_path=/root/.local/share/protonmail/bridge-v3/updates/3.22.0/proton-bridge launcher_version=3.22.0
FATA[Feb 25 15:08:59.796] Failed to launch                              error="exit status 1" exe_path=/root/.local/share/protonmail/bridge-v3/updates/3.22.0/proton-bridge launcher_path=/usr/lib/protonmail/bridge/proton-bridge launcher_version=3.19.0
FATA[Feb 27 16:31:24.339] Failed to launch                              error="exit status 127" exe_path=/root/.local/share/protonmail/bridge-v3/updates/3.22.0/bridge exe_to_launch=bridge launcher_path=/root/.local/share/protonmail/bridge-v3/updates/3.22.0/proton-bridge launcher_version=3.22.0
FATA[Feb 27 16:31:24.341] Failed to launch                              error="exit status 1" exe_path=/root/.local/share/protonmail/bridge-v3/updates/3.22.0/proton-bridge launcher_path=/usr/lib/protonmail/bridge/proton-bridge launcher_version=3.19.0

[rtsundland]

Seeing the same with:

/root/.local/share/protonmail/bridge-v3/updates/3.22.0/bridge: error while loading shared libraries: libfido2.so.1: cannot open shared object file: No such file or directory

[NoelleAttachedStorage]

I also had this working for quite awhile and noticed my Unraid machine was not sending emails to me anymore and missed a log error. My logs also say the same.

[Pietro395]

Same problemi for me

[strongjz]

Same error here using latest today.

Environment

Docker image: 
        "Image": "sha256:aacf2de9029dab11ca7ebfea4614c37b9cd58323c47c4773bd3f15d13ce62868",

cat /etc/os-release
PRETTY_NAME="Ubuntu 24.04.4 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04.4 LTS (Noble Numbat)"

Linux hulk 6.17.0-14-generic #14~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Jan 15 15:52:10 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

Log error

docker compose logs -f
protonmail-bridge-1  | + [[ '' == init ]]
protonmail-bridge-1  | + rm -f faketty
protonmail-bridge-1  | + socat TCP-LISTEN:25,fork TCP:127.0.0.1:1025
protonmail-bridge-1  | + socat TCP-LISTEN:143,fork TCP:127.0.0.1:1143
protonmail-bridge-1  | + mkfifo faketty
protonmail-bridge-1  | + cat faketty
protonmail-bridge-1  | + protonmail-bridge --cli
protonmail-bridge-1  | /root/.local/share/protonmail/bridge-v3/updates/3.22.0/bridge: error while loading shared libraries: libfido2.so.1: cannot open shared object file: No such file or directory
protonmail-bridge-1  | FATA[Mar 12 14:21:04.612] Failed to launch                              error="exit status 127" exe_path=/root/.local/share/protonmail/bridge-v3/updates/3.22.0/bridge exe_to_launch=bridge launcher_path=/root/.local/share/protonmail/bridge-v3/updates/3.22.0/proton-bridge launcher_version=3.22.0
protonmail-bridge-1  | FATA[Mar 12 14:21:04.613] Failed to launch                              error="exit status 1" exe_path=/root/.local/share/protonmail/bridge-v3/updates/3.22.0/proton-bridge launcher_path=/usr/lib/protonmail/bridge/proton-bridge launcher_version=3.19.0

[NoelleAttachedStorage]

I actually switched to the fork in this thread and it's back to working again

#135 (comment)

[strongjz]

yea, if thats the case, ill just build it and use my own fork then :(

[rcarey1999]

Facing this same issue. What release can I go to when it last worked?

[Deanosim]

Yeah same for me, I hadn't used the container in Unraid for awhile so I didn't notice but I guess yeah use a fork or fork it yourself, I personally will either use another bridge, fork this one, or just make my own dockerfile.

[fiveangle]

ibid