search

flathub / me.proton.Mail

https://flathub.org/apps/details/me.proton.Mail
2 stars 3 forks source link

Cannot open #17

Open rashadgasimli opened 2 weeks ago

rashadgasimli commented 2 weeks ago

App fails to start on Fedora Silverblue:

2:0924/124637.808283:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
12:46:37.913 (settings) › Settings saved {"spellChecker":true,"overrideError":false,"releaseCategory":"Stable","rolloutProportion":0.03518376534785417}
12:46:37.921 (main)     › App start is mac: false is windows: false isLinux: true version: 1.1.2
12:46:37.921 (main)     › Desktop features: InAppPayments:true, ThemeSelection:true, EarlyAccess:true, MultiAccount:true, LatestVersionCheck:true, InstallSource:true
12:46:37.929 (main)     › App is not default mailto client
[2:0924/124638.001231:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[2:0924/124638.001266:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
silikeite commented 2 weeks ago

Fail is independent of dbus -- adding dbus permission via Flatseal only removes the last two lines from rashadgasimli's logs but still causes an instant quit.

rashadgasimli commented 2 weeks ago

Yeah

NicBOMB commented 2 weeks ago

Fail is independent of dbus -- adding dbus permission via Flatseal only removes the last two lines from rashadgasimli's logs but still causes an instant quit.

Do NOT assign new permissions to Proton Mail. They are not required! Ignore bus.cc errors, as it's just chrome being grumpy. Not related to the real issue. https://github.com/flathub/me.proton.Pass/issues/15#issuecomment-2307613365

NicBOMB commented 2 weeks ago

The issue is with the downloaded version of Proton Mail. Version 1.2.1 is currently categorized as an "Alpha", whereas the previous releases were "Stable" and "EarlyAccess" respectively. @proletarius101 The update check should only select versions which are "Stable" to guarantee users are not running into these issues.

proletarius101 commented 2 weeks ago

The update check should only select versions which are "Stable" to guarantee users are not running into these issues.

The check has been there a while ago: https://github.com/flathub/me.proton.Mail/blob/9318e76dfcb69e55e6fc2515bf2eefa1dda27157/me.proton.Mail.yml#L53

silikeite commented 1 week ago

Checked dmesg and seems that process (Proton Mail Bet) is dumping core somewhere along libzypak-preload-host-spawn-strategy.so. (at 0xad30b and 0xad59d).

Bet seems weird -- are we on beta builds?

proletarius101 commented 1 week ago

Checked dmesg and seems that process (Proton Mail Bet) is dumping core somewhere along libzypak-preload-host-spawn-strategy.so. (at 0xad30b and 0xad59d).

Bet seems weird -- are we on beta builds?

What build are you using? You can check it by flatpak info me.proton.Mail

proletarius101 commented 1 week ago

are we on beta builds?

Yes. Proton Mail only has beta versions

cameronbosch commented 6 days ago

I can confirm that this issue is also happening for me after the recent update on Flathub...