flathub / ch.protonmail.protonmail-bridge

https://flathub.org/apps/details/ch.protonmail.protonmail-bridge
11 stars 7 forks source link

Cannot lauch after logging out #107

Open sith-on-mars opened 1 year ago

sith-on-mars commented 1 year ago

OS: Fedora Silverblue

Protonmail Bridge launched fine after booting up the system. However, it failed to launch after logging out from the session. It gave me the following error:

[dadstick@fedora ~]$ flatpak run ch.protonmail.protonmail-bridge
QApplication: invalid style override 'kvantum' passed, ignoring it.
    Available styles: Windows, Fusion
INFO[May 18 18:51:09.736] bridge-gui starting
INFO[May 18 18:51:09.736] Using Qt 6.3.2
ERRO[May 18 18:51:09.736] Instance already exists /var/home/dadstick/.var/app/ch.protonmail.protonmail-bridge/cache/protonmail/bridge-v3/bridge-v3-gui.lock (PID : 8 - Host : fedora - App : bridge-gui)
ERRO[May 18 18:51:14.738] Could not connect to bridge focus service for a raise call.
FATA[May 18 18:51:14.746] reportID: 81d613e79beb42fb2ea218017a156941 Captured exception: Could not connect to bridge focus service for a raise call.
FATA[May 18 18:51:16.419] Failed to launch                              error="exit status 1" exe_path=/app/lib/protonmail/bridge/bridge-gui exe_to_launch=bridge-gui launcher_path=/app/lib/protonmail/bridge/proton-bridge launcher_version=3.1.3

I'll have to reboot the system to fix it. Is there any workaround or would you be able to fix it? Thank you!

Edit: it seems to be a Flatpak specific issue, as I didn't encounter the issue with the rpm version.

A6GibKm commented 1 year ago

Delete the file /var/home/dadstick/.var/app/ch.protonmail.protonmail-bridge/cache/protonmail/bridge-v3/bridge-v3-gui.lock, this seems to be an issue on Proton's side

sith-on-mars commented 1 year ago

Thanks for the reply. The issue didn't happen when using the rpm version so it might be a Flatpak specific issue.

A6GibKm commented 1 year ago

it only happens when the app is closed in a bad way. No idea if it happens outside of flatpak, but it is an issue upstream as the file is created properly inside the sandbox.

sith-on-mars commented 1 year ago

I normally wouldn't close the app before I logged out, which I didn't expect to be considered as 'app closed in a bad way'.

A6GibKm commented 1 year ago

The app deletes the file while it is shutting down, clearly something stopped the app from deleting it.

This can happen for example when ones kills the process or uses ctrl+c when running in the terminal. I personally think it is a bad idea on their end as it is super easy to break.

bmhieserich commented 1 year ago

Tried bringing it up in the proton-bridge github, issue got immediately closed claiming it was a flatpak issue.

sith-on-mars commented 1 year ago

@bmhieserich

Edit: it seems to be a Flatpak specific issue, as I didn't encounter the issue with the rpm version.