Patrice84 commented 9 months ago

Summary

Protonmail-bridge does not start and I got the following message : Cannot connect to Go backend via gRPC: Connection to the gRPC server failed because of a timeout And until that message appears, I have my panel blocked, and you cannot get Menu or click on anything.

Steps to reproduce

Start Protonmail-bridge

Expected result

Basically nothing apart from the icon going into the tray (Budgie DE)

Actual result

Once the above message appears and is clicked, you can use the desktop normally, but the bridge obviously does not work (with Evolution in my case).

Environment

[X] Is system up to date?

Repo

Shannon (stable)

Desktop Environment

Budgie

System details

Rapport d’informations du système

Détails du compte rendu

Date de génération : 2023-12-08 15:22:10

Hardware Information:

Modèle du matériel : Gigabyte Technology Co., Ltd. X470 AORUS ULTRA GAMING
Mémoire : 64,0 Gio
Processeur : AMD Ryzen™ 7 2700 × 16
Carte graphique : AMD Radeon™ RX 6750 XT
Capacité du disque : 5,3 To

Software Information:

Version du micrologiciel : F64e
Nom du système d’exploitation : Fedora Linux 39 (Workstation Edition)
Construction du système d’exploitation : (null)
Type de système d’exploitation : 64 bits
Version de GNOME : 45.2
Système de fenêtrage : Wayland
Version du noyau : Linux 6.6.4-200.fc39.x86_64

As I am with Fedora when writing this bug.

Other comments

No response

GZGavinZhao commented 9 months ago

I've been using the Flatpak version and it works great for me.

ReillyBrogan commented 9 months ago

I've managed to fix this issue locally, it was caused by a behavioral change in Qt 6.6.1. Qt changed how they load the OpenSSL providers which requires a corresponding change to the Protonmail GUI. I'll get the fix merged into unstable tomorrow and the fixed version will be in the next sync.

Patrice84 commented 9 months ago

Thanks @ReillyBrogan. I'll see this next sync. @GZGavinZhao : thanks for the flatpak tip. Anyway, I try to avoid flatpak when there is a distrib app.

ReillyBrogan commented 8 months ago

Hi! I think I tracked down the actual cause of this issue as an issue with our build of qt6-base v6.6.1 and the openssl_hash feature of it (d8ca3d199d66b4c3dc8d558f7dfdd369f86eb340). I've now fixed that in the qt6-base package itself, and so have removed the patch that was working around the issue in the protonmail-bridge package (ef5556b96f103a0ed4ab7504fa4405ec801a1484). Please test this after the sync and let me know if it's still working or not. If not I'll add the patch back and cherry-pick it to stable so it's not broken long.

CC @FriesischScott.

FriesischScott commented 8 months ago

Seems to work perfectly for me. They also released 3.8.1 so I'll prepare an update. They keep tagging pre-releases and then later updating them to proper releases so the Github notifications for releases are useless..

getsolus / packages

Protonmail-bridge #996