Cannot open

[rashadgasimli]

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]

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]

Yeah

[NicBOMB]

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]

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]

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]

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]

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]

are we on beta builds?

Yes. Proton Mail only has beta versions

[cameronbosch]

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

[dperson]

It's been working for me until the update today. Version info below:

❯  flatpak info me.proton.Mail

Proton Mail - Secure email that protects your privacy

          ID: me.proton.Mail
         Ref: app/me.proton.Mail/x86_64/stable
        Arch: x86_64
      Branch: stable
     Version: 1.2.4
     License: GPL-3.0
      Origin: flathub
  Collection: org.flathub.Stable
Installation: system
   Installed: 225.1 MB
     Runtime: org.freedesktop.Platform/x86_64/23.08
         Sdk: org.freedesktop.Sdk/x86_64/23.08

      Commit: 97d855f0571e69bf713fcc36105e806214c8cecd8da40a5f57f9ede2a9bcf1bc
      Parent: ab9296732cbe7b01aa1bc9ce89a336c79ebe242904b6451dbaf7e04ec30c392b
     Subject: proton-mail: Update ProtonMail.deb to 1.2.4 (0d4c6b46)
        Date: 2024-11-06 09:52:11 +0000

Nothing useful in the flatpak run me.proton.Mail output, or the log file (.var/app/me.proton.Mail/config/Proton\ Mail/logs/main.log same info).

❯  flatpak run me.proton.Mail
[2:1106/104837.299902: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
10:48:37.411 (settings) › Settings saved {"spellChecker":true,"overrideError":false,"releaseCategory":"Stable","rolloutProportion":0.8398178205202502}
10:48:37.436 (main)     › App start is mac: false is windows: false isLinux: true version: 1.2.4 params [ '/app/proton-mail/Proton Mail Beta' ]
10:48:37.437 (main)     › Desktop features: InAppPayments:true, ThemeSelection:true, EarlyAccess:true, MultiAccount:true, LatestVersionCheck:true, InstallSource:true, MailtoTelemetry:true
10:48:37.444 (protocol) › Checking default mailto
10:48:37.445 (protocol) › Missing proton-mail.desktop file
10:48:37.445 (protocol) › App default mailto client status {
  isDefault: false,
  wasChecked: false,
  shouldBeDefault: false,
  wasDefaultInPast: false,
  lastReport: { wasDefault: false, timestamp: 0 }
}
[2:1106/104837.495643: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:1106/104837.495679: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

[dperson]

Running: sudo flatpak update --commit=ab9296732cbe7b01aa1bc9ce89a336c79ebe242904b6451dbaf7e04ec30c392b me.proton.Mail To downgrade to the 2024-10-04 version worked around the issue for me.

Now running: flatpak mask me.proton.Mail To stop it updating to the broken version...

[proletarius101]

I'm unable to reproduce this. But you may try if you can run mv ~/.var/app/me.proton.Mail ~/.var/app/me.proton.Mail.bk to and if it can start Proton Mail again.

[dperson]

It's all just cache really, so I'd just deleted it as a trouble-shooting step prior to rolling the flatpak back. Exactly the same behaviour.

-------- Original Message --------On 11/7/24 04:09, proletarius101 - notifications at github.com wrote: I'm unable to reproduce this. But you may try if you can run mv ~/.var/app/me.proton.Mail ~/.var/app/me.proton.Mail.bk to and if it can start Proton Mail again.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

[proletarius101]

It's all just cache really, so I'd just deleted it as a trouble-shooting step prior to rolling the flatpak back. Exactly the same behaviour.

In case you are using Wayland, please try

flatpak run --nosocket=wayland me.proton.Mail --ozone-platform-hint=x11

[AtiusAmy]

Seems like I can also do flatpak run me.proton.Mail --enable-features=UseOzonePlatform,WaylandWindowDecorations --ozone-platform-hint=auto and it launched fine

[AtiusAmy]

I just added ELECTRON_OZONE_PLATFORM_HINT=wayland to flatseal environment and it worked 🥳

[proletarius101]

I just added ELECTRON_OZONE_PLATFORM_HINT=wayland to flatseal environment and it worked 🥳

Did you try to start it at least once with x11? My experiment indicates that it only will start on Wayland only after it starts once on X11

[AtiusAmy]

ah yeah I've tried starting with X11 and it worked, but I didn't want to use Xwayland, so I switched

[proletarius101]

OK. I'm just thinking about how to make it work out of the box.

[proletarius101]

It's reproducible even without Flatpak

[proletarius101]

I encourage you to report this to Proton as well, if you want their attention on this issue. Only them can fix it.

[dperson]

Thanks so much! Temporarily removing my /var/lib/flatpak/overrides/global with:

[Context]
sockets=wayland;

[Environment]
ELECTRON_OZONE_PLATFORM_HINT=auto

Did get it to start, and it continued to do so after putting it back in place. I also updated my prior report to Proton about the issue with what was actually triggering it, how to reproduce it, and the work around.