search

ProtonMail / proton-bridge

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

Crash on startup vers 3.6.1 #440

Open Zeuhrg opened 8 months ago

Zeuhrg commented 8 months ago

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

Current Behavior

Possible Solution

Steps to Reproduce

https://proton.me/mail/bridge

Version Information

3.6.1

Context (Environment)

<-- officiel kernel : Linux nomadz 6.1.0-13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1 (2023-09-29) x86_64 GNU/Linux -->

Zeuhrg commented 8 months ago

INFO[Nov 17 09:56:11.610] bridge-gui starting INFO[Nov 17 09:56:11.610] Using Qt 6.4.3 INFO[Nov 17 09:56:11.639] lock file created /home/anon/.cache/protonmail/bridge-v3/bridge-v3-gui.lock INFO[Nov 17 09:56:11.639] New Sentry reporter - id: xJ9AlIqoevy2iYz9YZV8RTabBYyaYovNNHvXLAMdFGM=. DEBU[Nov 17 09:56:11.647] Bridge executable path: /home/anon/.local/share/protonmail/bridge-v3/updates/3.6.1/bridge INFO[Nov 17 09:56:11.647] Launching bridge process with command "/home/anon/.local/share/protonmail/bridge-v3/updates/3.6.1/bridge" --grpc --parent-pid 318002 --launcher ./bridge-gui --session-id 20231117_095611610 INFO[Nov 17 09:56:11.648] Retrieving gRPC service configuration from '/home/anon/.config/protonmail/bridge-v3/grpcServerConfig.json' Erreur de segmentation

Zeuhrg commented 8 months ago

strace don't if it will help you [Uploading strace.txt…]()

LBeernaertProton commented 8 months ago

@Zeuhrg

Zeuhrg commented 7 months ago

Hi thx for support my debian is a 12.2 stable release with cinnamon and default confguration As i know Debian is Wayland

Zeuhrg commented 7 months ago

Thanks for the non support :) Solution provided by strace Debian is not supported, need QT6 widget or something else back to version 2.3.0 is working Incredible to support Ubuntu, centos (obsolete !!!!) and not Debian .... pittyful

LBeernaertProton commented 7 months ago

Hey, sorry for the lack of replies, but this seems unlikely related to lack of "debian" support. We have a colleague who is running Bridge fine on Debian 12. I personally run Bridge on Fedora 38 with Gnome Wayland without issues.

We suspect you may be missing a library that is not installed on your system with your selection of DE.

can you execute the following commands:

ldd  /usr/lib/protonmail/bridge/lib/libQt6XcbQpa.so.6
ldd  libQt6WaylandClient.so.6

and see if you are missing some dependencies?

Also, your strace link is invalid.

Zeuhrg commented 7 months ago

root@myhost ~ # ldd /usr/lib/protonmail/bridge/lib/libQt6XcbQpa.so.6 linux-vdso.so.1 (0x00007ffd87de6000) /lib/x86_64-linux-gnu/libsnoopy.so (0x00007fc282e41000) libxcb-icccm.so.4 => /lib/x86_64-linux-gnu/libxcb-icccm.so.4 (0x00007fc282e1a000) libxcb-image.so.0 => /lib/x86_64-linux-gnu/libxcb-image.so.0 (0x00007fc282e14000) libxcb-keysyms.so.1 => /lib/x86_64-linux-gnu/libxcb-keysyms.so.1 (0x00007fc282c00000) libxcb-randr.so.0 => /lib/x86_64-linux-gnu/libxcb-randr.so.0 (0x00007fc282e03000) libxcb-render.so.0 => /lib/x86_64-linux-gnu/libxcb-render.so.0 (0x00007fc282bf0000) libxcb-render-util.so.0 => /lib/x86_64-linux-gnu/libxcb-render-util.so.0 (0x00007fc282800000) libxcb-shape.so.0 => /lib/x86_64-linux-gnu/libxcb-shape.so.0 (0x00007fc282beb000) libxcb-shm.so.0 => /lib/x86_64-linux-gnu/libxcb-shm.so.0 (0x00007fc282be6000) libxcb-sync.so.1 => /lib/x86_64-linux-gnu/libxcb-sync.so.1 (0x00007fc282bde000) libxcb.so.1 => /lib/x86_64-linux-gnu/libxcb.so.1 (0x00007fc282bb4000) libxcb-xfixes.so.0 => /lib/x86_64-linux-gnu/libxcb-xfixes.so.0 (0x00007fc282ba9000) libxcb-xkb.so.1 => /lib/x86_64-linux-gnu/libxcb-xkb.so.1 (0x00007fc282b8c000) libxkbcommon.so.0 => /lib/x86_64-linux-gnu/libxkbcommon.so.0 (0x00007fc282b46000) libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x00007fc282a0e000) libX11-xcb.so.1 => /lib/x86_64-linux-gnu/libX11-xcb.so.1 (0x00007fc282a09000) libX11.so.6 => /lib/x86_64-linux-gnu/libX11.so.6 (0x00007fc2826be000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fc2826b9000) libxkbcommon-x11.so.0 => /lib/x86_64-linux-gnu/libxkbcommon-x11.so.0 (0x00007fc2826ae000) libQt6OpenGL.so.6 => /usr/lib/protonmail/bridge/lib/libQt6OpenGL.so.6 (0x00007fc28260f000) libQt6Gui.so.6 => /usr/lib/protonmail/bridge/lib/libQt6Gui.so.6 (0x00007fc281c00000) libGL.so.1 => /lib/x86_64-linux-gnu/libGL.so.1 (0x00007fc281b79000) libQt6Core.so.6 => /usr/lib/protonmail/bridge/lib/libQt6Core.so.6 (0x00007fc281400000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fc28260a000) libgthread-2.0.so.0 => /lib/x86_64-linux-gnu/libgthread-2.0.so.0 (0x00007fc282605000) libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fc281000000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fc281a9a000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fc2825e5000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fc28121f000) libxcb-util.so.1 => /lib/x86_64-linux-gnu/libxcb-util.so.1 (0x00007fc2825db000) libXau.so.6 => /lib/x86_64-linux-gnu/libXau.so.6 (0x00007fc2825d6000) libXdmcp.so.6 => /lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007fc280c00000) libpcre2-8.so.0 => /lib/x86_64-linux-gnu/libpcre2-8.so.0 (0x00007fc280f66000) libEGL.so.1 => /lib/x86_64-linux-gnu/libEGL.so.1 (0x00007fc2825c0000) libfontconfig.so.1 => /lib/x86_64-linux-gnu/libfontconfig.so.1 (0x00007fc280f1b000) libQt6DBus.so.6 => /usr/lib/protonmail/bridge/lib/libQt6DBus.so.6 (0x00007fc280e57000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007fc280e38000) libfreetype.so.6 => /lib/x86_64-linux-gnu/libfreetype.so.6 (0x00007fc280b35000) libGLdispatch.so.0 => /lib/x86_64-linux-gnu/libGLdispatch.so.0 (0x00007fc280a7c000) libGLX.so.0 => /lib/x86_64-linux-gnu/libGLX.so.0 (0x00007fc280a48000) libicui18n.so.56 => /usr/lib/protonmail/bridge/lib/libicui18n.so.56 (0x00007fc280400000) libicuuc.so.56 => /usr/lib/protonmail/bridge/lib/libicuuc.so.56 (0x00007fc280000000) libicudata.so.56 => /usr/lib/protonmail/bridge/lib/libicudata.so.56 (0x00007fc27e600000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fc2825b7000) /lib64/ld-linux-x86-64.so.2 (0x00007fc282f02000) libbsd.so.0 => /lib/x86_64-linux-gnu/libbsd.so.0 (0x00007fc281a84000) libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 (0x00007fc280e0d000) libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x00007fc2809f2000) libpng16.so.16 => /lib/x86_64-linux-gnu/libpng16.so.16 (0x00007fc2809bc000) libbrotlidec.so.1 => /lib/x86_64-linux-gnu/libbrotlidec.so.1 (0x00007fc2809af000) libmd.so.0 => /lib/x86_64-linux-gnu/libmd.so.0 (0x00007fc2809a2000) libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 (0x00007fc2808d2000) libbrotlicommon.so.1 => /lib/x86_64-linux-gnu/libbrotlicommon.so.1 (0x00007fc2808af000) libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x00007fc2808a3000) libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x00007fc27e4b9000) liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007fc2803d1000) libzstd.so.1 => /lib/x86_64-linux-gnu/libzstd.so.1 (0x00007fc27e3fd000) liblz4.so.1 => /lib/x86_64-linux-gnu/liblz4.so.1 (0x00007fc27e3d7000) libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x00007fc27e3af000)

root@myhost ~ # ldd libQt6WaylandClient.so.6 ldd: ./libQt6WaylandClient.so.6: No such file or directory

root@myhost ~ # find / -name libQt6WaylandClient.so.6 /root/.local/share/protonmail/bridge-v3/updates/3.6.1/lib/libQt6WaylandClient.so.6 /usr/lib/x86_64-linux-gnu/libQt6WaylandClient.so.6 /usr/lib/protonmail/bridge/lib/libQt6WaylandClient.so.6

Zeuhrg commented 7 months ago

strace.log

LBeernaertProton commented 7 months ago

Is there any particular reason why you are running this with the root user?

Zeuhrg commented 7 months ago

yes there is a reason

LBeernaertProton commented 7 months ago

Can you try running this without root to make sure it's not that?

Zeuhrg commented 7 months ago

whatever the user, it is the same

LBeernaertProton commented 7 months ago

I just booted up a VM with Debian 12 and Cinammon. This version of cinnamon doesn't not have wayland support. According to this article that is only available on version 6. Debian ships with 5.6.8.

I had no issues running the Bridge in this context.

It could also be that you may have a GPU that does not support the modern rendering features of Qt6.

You can try to start bridge in software renderer mode.

protonmail-bridge --software-renderer
Zeuhrg commented 6 months ago

Hi, Thx for support, réinstalled my Debian , and another on VM under KVM, same result withthe option software-renderer

i confirm for w11/ wayland

echo $XDG_SESSION_TYPE

x11

Under a kvm Guest with defautl install under debioan 12.2 fresh install (basic install with cinnamon)

root@deb:~# protonmail-bridge qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: wayland, vkkhrdisplay, minimalegl, offscreen, wayland-egl, linuxfb, eglfs, minimal, vnc, xcb.

FATA[Dec 22 08:49:20.205] Failed to launch error="signal: aborted" exe_path=/usr/lib/protonmail/bridge/bridge-gui exe_to_launch=bridge-gui launcher_path=/usr/lib/protonmail/bridge/proton-bridge launcher_version=3.7.1

SOLUTION : i installed gnome/stable and restarted the UI with Gnome : it works

Wayland is only supported with kde or gnome (argh..) Switch to Gnome or KDE ?????? :-1:

I returned to 2.3 of bridge

Finally : It could be good to choose common libraries used by majority of distrib for a program like this (bridge). And as you said "use a "modern" librairy lowers the usability of a program And please, stop assimilate Ubuntu and Debian , since years now they are very distincts and ubuntu has always been based ond SID/Debian (not stable)

source : https://wiki.debian.org/Wayland (see unsupported)

LBeernaertProton commented 6 months ago 
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

This means that there are missing xlib dependencies on your machine. This command should solve the problem.

apt install libxcb-*
Zeuhrg commented 6 months ago

Sorry , doesn't work :( But i succeed to make it work with a second VM (end of this post)

With my debian (cinnamon without Gnome) :+1: INFO[Jan 08 09:36:23.536] bridge-gui starting INFO[Jan 08 09:36:23.537] Using Qt 6.4.3 INFO[Jan 08 09:36:23.556] lock file created /root/.cache/protonmail/bridge-v3/bridge-v3-gui.lock INFO[Jan 08 09:36:23.556] New Sentry reporter - id: 6oyBeyE6iNfzcSJI+8hkUl2LkzZPFgyF8enrCoMlGPI=. DEBU[Jan 08 09:36:23.567] Bridge executable path: /usr/lib/protonmail/bridge/bridge INFO[Jan 08 09:36:23.567] Launching bridge process with command "/usr/lib/protonmail/bridge/bridge" --grpc --parent-pid 28389 --session-id 20240108_093623190 --launcher /usr/lib/protonmail/bridge/proton-bridge INFO[Jan 08 09:36:23.567] Retrieving gRPC service configuration from '/root/.config/protonmail/bridge-v3/grpcServerConfig.json' FATA[Jan 8 09:36:23.593] Failed to launch error="signal: segmentation fault" exe_path=/usr/lib/protonmail/bridge/bridge-gui exe_to_launch=bridge-gui launcher_path=/usr/lib/protonmail/bridge/proton-bridge launcher_version=3.7.1

with a VM with a VM debian with cinnamon + Gnome : it works

delner commented 5 months ago

On my desktop Ubuntu 22.04.3 with the latest version (3.8.2):

$ protonmail-bridge --log-level debug
INFO[Feb 02 21:08:22.496] bridge-gui starting
INFO[Feb 02 21:08:22.496] Using Qt 6.4.3
INFO[Feb 02 21:08:22.516] lock file created /home/usernamehere/.cache/protonmail/bridge-v3/bridge-v3-gui.lock
INFO[Feb 02 21:08:22.516] New Sentry reporter - id: 4aQoV9Di/YWTzsZCPziRwhSyZrKdFPus65Moz07Sduw=.
DEBU[Feb 02 21:08:22.526] Bridge executable path: /usr/lib/protonmail/bridge/bridge
INFO[Feb 02 21:08:22.526] Launching bridge process with command "/usr/lib/protonmail/bridge/bridge" --grpc --parent-pid 150253 --log-level debug --session-id 20240202_210822162 --launcher /usr/lib/protonmail/bridge/proton-bridge
INFO[Feb 02 21:08:22.526] Retrieving gRPC service configuration from '/home/usernamehere/.config/protonmail/bridge-v3/grpcServerConfig.json'
time="2024-02-02T21:08:22-05:00" level=info msg="Migrating keychain helper"
WARN[Feb  2 21:08:22.596] Keychain is not available.                    keychain=Pass
INFO[Feb 02 21:08:22.841] Connecting to gRPC service
INFO[Feb 02 21:08:22.843] Connection to gRPC server at unix:///tmp/bridge0233. attempt #1
INFO[Feb 02 21:08:22.845] Successfully connected to gRPC server.
INFO[Feb 02 21:08:22.845] Client config file was saved to '/home/usernamehere/.config/protonmail/bridge-v3/grpcClientConfig_0.json'
DEBU[Feb 02 21:08:22.846] checkTokens()
INFO[Feb 02 21:08:22.846] gRPC token was validated
INFO[Feb 02 21:08:22.846] Connected to backend via gRPC service.
DEBU[Feb 02 21:08:22.846] version()
DEBU[Feb 02 21:08:22.846] EventStreamReader started
DEBU[Feb 02 21:08:22.846] goos()
DEBU[Feb 02 21:08:22.846] logsPath()
DEBU[Feb 02 21:08:22.847] licensePath()
DEBU[Feb 02 21:08:22.847] mailServerSettings()
DEBU[Feb 02 21:08:22.847] getUserList()
FATA[Feb  2 21:08:24.008] Failed to launch                              error="signal: segmentation fault (core dumped)" exe_path=/usr/lib/protonmail/bridge/bridge-gui exe_to_launch=bridge-gui launcher_path=/usr/lib/protonmail/bridge/proton-bridge launcher_version=3.8.2

And some more info about the env:

$ ldd /usr/lib/protonmail/bridge/lib/libQt6XcbQpa.so.6
    linux-vdso.so.1 (0x00007ffe39f36000)
    libxcb-icccm.so.4 => /lib/x86_64-linux-gnu/libxcb-icccm.so.4 (0x00007faa94287000)
    libxcb-image.so.0 => /lib/x86_64-linux-gnu/libxcb-image.so.0 (0x00007faa94281000)
    libxcb-keysyms.so.1 => /lib/x86_64-linux-gnu/libxcb-keysyms.so.1 (0x00007faa9427c000)
    libxcb-randr.so.0 => /lib/x86_64-linux-gnu/libxcb-randr.so.0 (0x00007faa94269000)
    libxcb-render.so.0 => /lib/x86_64-linux-gnu/libxcb-render.so.0 (0x00007faa9425a000)
    libxcb-render-util.so.0 => /lib/x86_64-linux-gnu/libxcb-render-util.so.0 (0x00007faa94251000)
    libxcb-shape.so.0 => /lib/x86_64-linux-gnu/libxcb-shape.so.0 (0x00007faa9424c000)
    libxcb-shm.so.0 => /lib/x86_64-linux-gnu/libxcb-shm.so.0 (0x00007faa94247000)
    libxcb-sync.so.1 => /lib/x86_64-linux-gnu/libxcb-sync.so.1 (0x00007faa9423d000)
    libxcb.so.1 => /lib/x86_64-linux-gnu/libxcb.so.1 (0x00007faa94213000)
    libxcb-xfixes.so.0 => /lib/x86_64-linux-gnu/libxcb-xfixes.so.0 (0x00007faa94209000)
    libxcb-xkb.so.1 => /lib/x86_64-linux-gnu/libxcb-xkb.so.1 (0x00007faa941e9000)
    libxkbcommon.so.0 => /lib/x86_64-linux-gnu/libxkbcommon.so.0 (0x00007faa941a2000)
    libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x00007faa94068000)
    libX11-xcb.so.1 => /lib/x86_64-linux-gnu/libX11-xcb.so.1 (0x00007faa94063000)
    libX11.so.6 => /lib/x86_64-linux-gnu/libX11.so.6 (0x00007faa93f23000)
    libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007faa93f1e000)
    libxkbcommon-x11.so.0 => /lib/x86_64-linux-gnu/libxkbcommon-x11.so.0 (0x00007faa93f11000)
    libQt6OpenGL.so.6 => /usr/lib/protonmail/bridge/lib/libQt6OpenGL.so.6 (0x00007faa93e72000)
    libQt6Gui.so.6 => /usr/lib/protonmail/bridge/lib/libQt6Gui.so.6 (0x00007faa93400000)
    libGL.so.1 => /opt/amdgpu-pro/lib/x86_64-linux-gnu/libGL.so.1 (0x00007faa93dd0000)
    libQt6Core.so.6 => /usr/lib/protonmail/bridge/lib/libQt6Core.so.6 (0x00007faa92c00000)
    libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007faa93dcb000)
    libgthread-2.0.so.0 => /lib/x86_64-linux-gnu/libgthread-2.0.so.0 (0x00007faa93dc4000)
    libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007faa92800000)
    libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007faa93319000)
    libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007faa932f9000)
    libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007faa92400000)
    libxcb-util.so.1 => /lib/x86_64-linux-gnu/libxcb-util.so.1 (0x00007faa93dbb000)
    libXau.so.6 => /lib/x86_64-linux-gnu/libXau.so.6 (0x00007faa93db3000)
    libXdmcp.so.6 => /lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007faa93dab000)
    libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007faa93283000)
    libEGL.so.1 => /opt/amdgpu-pro/lib/x86_64-linux-gnu/libEGL.so.1 (0x00007faa92bf7000)
    libfontconfig.so.1 => /lib/x86_64-linux-gnu/libfontconfig.so.1 (0x00007faa92bad000)
    libQt6DBus.so.6 => /usr/lib/protonmail/bridge/lib/libQt6DBus.so.6 (0x00007faa92ae9000)
    libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007faa92acd000)
    libfreetype.so.6 => /lib/x86_64-linux-gnu/libfreetype.so.6 (0x00007faa92738000)
    libicui18n.so.56 => /usr/lib/protonmail/bridge/lib/libicui18n.so.56 (0x00007faa91e00000)
    libicuuc.so.56 => /usr/lib/protonmail/bridge/lib/libicuuc.so.56 (0x00007faa91a00000)
    libicudata.so.56 => /usr/lib/protonmail/bridge/lib/libicudata.so.56 (0x00007faa90000000)
    librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007faa92ac8000)
    /lib64/ld-linux-x86-64.so.2 (0x00007faa94357000)
    libbsd.so.0 => /lib/x86_64-linux-gnu/libbsd.so.0 (0x00007faa92ab0000)
    libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 (0x00007faa92a7f000)
    libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007faa92a76000)
    libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x00007faa926ea000)
    libpng16.so.16 => /lib/x86_64-linux-gnu/libpng16.so.16 (0x00007faa92a3b000)
    libbrotlidec.so.1 => /lib/x86_64-linux-gnu/libbrotlidec.so.1 (0x00007faa92a2d000)
    libmd.so.0 => /lib/x86_64-linux-gnu/libmd.so.0 (0x00007faa926dd000)
    libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 (0x00007faa92339000)
    libbrotlicommon.so.1 => /lib/x86_64-linux-gnu/libbrotlicommon.so.1 (0x00007faa926ba000)
    liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007faa9268d000)
    libzstd.so.1 => /lib/x86_64-linux-gnu/libzstd.so.1 (0x00007faa8ff31000)
    liblz4.so.1 => /lib/x86_64-linux-gnu/liblz4.so.1 (0x00007faa9266d000)
    libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x00007faa92662000)
    libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x00007faa8fdf3000)
    libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x00007faa9263a000)

This hasn't been working for months. Runs fine on a headless LXC though, so maybe GUI related?

Zeuhrg commented 5 months ago

For me, no chance to work with recent versions. I'm stuck with 2.3.0, but it works perfectly

LBeernaertProton commented 5 months ago

We had one customer service report of a user in a similar situation and the cause of their problem was the amd binary GPU driver. Once they switched over to the mesa driver the situation resolved itself.

If it is a GPU hardware/driver related problem, you can try to start bridge with --software-renderer and see if that works.

delner commented 5 months ago

I tried protonmail-bridge --log-level debug --software-renderer but the same segmentation fault occurs at the same step.

$ protonmail-bridge --log-level debug --software-renderer
INFO[Feb 06 22:37:25.497] bridge-gui starting
INFO[Feb 06 22:37:25.497] Using Qt 6.4.3
...
DEBU[Feb 06 22:37:25.846] getUserList()
FATA[Feb  6 22:37:29.476] Failed to launch                              error="signal: segmentation fault (core dumped)" exe_path=/usr/lib/protonmail/bridge/bridge-gui exe_to_launch=bridge-gui launcher_path=/usr/lib/protonmail/bridge/proton-bridge launcher_version=3.8.2

FWIW, I am using AMD's drivers, and have the Mesa drivers installed on my system. But I think switching to Mesa drivers would be an undesirable solution anyways, if I need the AMD drivers for particular games or applications.

LBeernaertProton commented 5 months ago

@delner Could you attach your logs (or mail to me - see github commits for address) the logs in debug level?

Can you also list the hardware (GPU/iGPU) on your system?

delner commented 5 months ago

Sure thing. I can share the full log of the above command... it isn't very long.

protonmail-bridge --log-level debug --software-renderer
INFO[Feb 08 22:39:07.182] bridge-gui starting
INFO[Feb 08 22:39:07.182] Using Qt 6.4.3
INFO[Feb 08 22:39:07.201] lock file created /home/david/.cache/protonmail/bridge-v3/bridge-v3-gui.lock
INFO[Feb 08 22:39:07.201] New Sentry reporter - id: 4aQoV9Di/YWTzsZCPziRwhSyZrKdFPus65Moz07Sduw=.
DEBU[Feb 08 22:39:07.212] Bridge executable path: /usr/lib/protonmail/bridge/bridge
INFO[Feb 08 22:39:07.212] Launching bridge process with command "/usr/lib/protonmail/bridge/bridge" --grpc --parent-pid 63816 --log-level debug --software-renderer --session-id 20240208_223906838 --launcher /usr/lib/protonmail/bridge/proton-bridge
INFO[Feb 08 22:39:07.212] Retrieving gRPC service configuration from '/home/david/.config/protonmail/bridge-v3/grpcServerConfig.json'
time="2024-02-08T22:39:07-05:00" level=info msg="Migrating keychain helper"
WARN[Feb  8 22:39:07.281] Keychain is not available.                    keychain=Pass
INFO[Feb 08 22:39:07.427] Connecting to gRPC service
INFO[Feb 08 22:39:07.429] Connection to gRPC server at unix:///tmp/bridge3307. attempt #1
INFO[Feb 08 22:39:07.431] Successfully connected to gRPC server.
INFO[Feb 08 22:39:07.431] Client config file was saved to '/home/david/.config/protonmail/bridge-v3/grpcClientConfig_0.json'
DEBU[Feb 08 22:39:07.431] checkTokens()
INFO[Feb 08 22:39:07.431] gRPC token was validated
INFO[Feb 08 22:39:07.431] Connected to backend via gRPC service.
DEBU[Feb 08 22:39:07.432] version()
DEBU[Feb 08 22:39:07.432] EventStreamReader started
DEBU[Feb 08 22:39:07.432] goos()
DEBU[Feb 08 22:39:07.432] logsPath()
DEBU[Feb 08 22:39:07.432] licensePath()
DEBU[Feb 08 22:39:07.432] mailServerSettings()
DEBU[Feb 08 22:39:07.433] getUserList()
FATA[Feb  8 22:39:08.748] Failed to launch                              error="signal: segmentation fault (core dumped)" exe_path=/usr/lib/protonmail/bridge/bridge-gui exe_to_launch=bridge-gui launcher_path=/usr/lib/protonmail/bridge/proton-bridge launcher_version=3.8.2

GPU: AMD Radeon™ RX 7900 XTX

And some other potentially useful outputs:

$ sudo lshw -c video
  *-display                 
       description: VGA compatible controller
       product: Advanced Micro Devices, Inc. [AMD/ATI]
       vendor: Advanced Micro Devices, Inc. [AMD/ATI]
       physical id: 0
       bus info: pci@0000:03:00.0
       logical name: /dev/fb0
       version: c8
       width: 64 bits
       clock: 33MHz
       capabilities: pm pciexpress msi vga_controller bus_master cap_list rom fb
       configuration: depth=32 driver=amdgpu latency=0 mode=2560x1440 resolution=2560,1440 visual=truecolor xres=2560 yres=1440
       resources: iomemory:f00-eff iomemory:f80-f7f irq:154 memory:f000000000-f7ffffffff memory:f800000000-f80fffffff ioport:f000(size=256) memory:fc700000-fc7fffff memory:fc800000-fc81ffff
  *-display
       description: VGA compatible controller
       product: Advanced Micro Devices, Inc. [AMD/ATI]
       vendor: Advanced Micro Devices, Inc. [AMD/ATI]
       physical id: 0
       bus info: pci@0000:18:00.0
       version: c1
       width: 64 bits
       clock: 33MHz
       capabilities: pm pciexpress msi msix vga_controller bus_master cap_list
       configuration: driver=amdgpu latency=0
       resources: iomemory:f80-f7f iomemory:f80-f7f irq:137 memory:f820000000-f82fffffff memory:f830000000-f8301fffff ioport:d000(size=256)
$ sudo lspci -nnk | egrep -i --color 'vga|3d|2d' -A3 | grep 'in use'
    Kernel driver in use: amdgpu
    Kernel driver in use: amdgpu
$ sudo apt list --installed | grep -i amdgpu-pro

amdgpu-pro-core/now 23.20-1646757.22.04 all [installed,local]
amdgpu-pro-lib32/now 23.20-1646757.22.04 amd64 [installed,local]
amdgpu-pro-oglp/now 23.20-1646757.22.04 amd64 [installed,local]
amdgpu-pro-oglp/now 23.20-1646757.22.04 i386 [installed,local]
amdgpu-pro/now 23.20-1646757.22.04 amd64 [installed,local]
amf-amdgpu-pro/now 1.4.31-1646757.22.04 amd64 [installed,local]
libamdenc-amdgpu-pro/now 1.0-1646757.22.04 amd64 [installed,local]
libegl1-amdgpu-pro-oglp/now 23.20-1646757.22.04 amd64 [installed,local]
libegl1-amdgpu-pro-oglp/now 23.20-1646757.22.04 i386 [installed,local]
libgl1-amdgpu-pro-oglp-dri/now 23.20-1646757.22.04 amd64 [installed,local]
libgl1-amdgpu-pro-oglp-dri/now 23.20-1646757.22.04 i386 [installed,local]
libgl1-amdgpu-pro-oglp-ext/now 23.20-1646757.22.04 amd64 [installed,local]
libgl1-amdgpu-pro-oglp-gbm/now 23.20-1646757.22.04 amd64 [installed,local]
libgl1-amdgpu-pro-oglp-glx/now 23.20-1646757.22.04 amd64 [installed,local]
libgl1-amdgpu-pro-oglp-glx/now 23.20-1646757.22.04 i386 [installed,local]
libgles1-amdgpu-pro-oglp/now 23.20-1646757.22.04 amd64 [installed,local]
libgles1-amdgpu-pro-oglp/now 23.20-1646757.22.04 i386 [installed,local]
libgles2-amdgpu-pro-oglp/now 23.20-1646757.22.04 amd64 [installed,local]
libgles2-amdgpu-pro-oglp/now 23.20-1646757.22.04 i386 [installed,local]
vulkan-amdgpu-pro/now 23.20-1646757.22.04 amd64 [installed,local]
vulkan-amdgpu-pro/now 23.20-1646757.22.04 i386 [installed,local]
delner commented 5 months ago

Also, this is interesting, decided to try running the same command, but with sudo aka sudo protonmail-bridge --log-level debug --software-renderer, and this time it pestered me with a Keychain window

image

Cancelling out of it 5 or so times eventually makes the UI show up, but unhappy.

image

Still, that looks like progress. (Same behavior if I don't include --software-renderer.) I presume when I'm running it without sudo its not able to get keychain access and then its segfaulting before the UI displays.