Thanks for the quick update!

awesome, electron40 has been released! so I've upgraded to it

I flagged it out of date. I upgraded by getting electron v40 from the AUR. You could make that (https://aur.archlinux.org/packages/electron40-bin) a dependency. When running the 1.12.1 version, there is a constant reminder from Proton that it's out of date.

The new version requires electron v40 but that's not packaged in extra yet. Should I force it to run on electron39 and upgrade anyway? or wait for electron40 to be available?

Hi, since a few weeks, I get a blank window on Sway (independent of how I launch proton-mail, command line or rofi). The last logs printed by the app are:

thread '<unnamed>' panicked at ../../third_party/rust/chromium_crates_io/vendor/skrifa-v0_29/src/outline/glyf/hint/engine/outline.rs:650:12:
attempt to multiply with overflow
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
06:21:52.677 (main)         › request-load-time average: 14ms deviation: 9ms max: 29ms count: 11
06:22:42.776 (flag-manager) › Checking flags
Error sending from webFrameMain:  Error: Render frame was disposed before WebFrameMain could be accessed
    at s._sendInternal (node:electron/js2c/browser_init:2:94432)
    at b._sendInternal (node:electron/js2c/browser_init:2:78733)
    at node:electron/js2c/browser_init:2:110262
    at new Promise (<anonymous>)
    at Object.invokeInWebContents (node:electron/js2c/browser_init:2:109991)
    at b.executeJavaScript (node:electron/js2c/browser_init:2:81144)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)

which seems to be a similar issue as this ferdium-bin comment by user leny. Similarly to leny, I'm able to solve the issue by installing aur/electron37-bin and not extra/electron37. I lack the technical know how to understand where the issue comes from, however.

No, this package itself is architecture independent. since the app.asar doesn't contain any compiled native modules, the package can be built and run on any arch. check out the electron package guidelines and the PKGBUILD arch for details.

I'm not sure where those conflicts are coming from. I usually keep debug builds off, but I was able to build and install pgadmin4-desktop-debug, pgadmin4-server-debug, and proton-mail-bin-debug together...

$ pacman -Q pgadmin4-desktop-debug pgadmin4-server-debug proton-mail-bin-debug
pgadmin4-desktop-debug 9.8-1
pgadmin4-server-debug 9.9-1
proton-mail-bin-debug 1.9.1-2

There seems to be file conflicts with pgadmin4-desktop-debug (although the fault may be with pgadmin4-desktop-debug, since pgadmin4-desktop are getting the same errors).

$ yay -S proton-mail-bin

... snip ...

Package (2)            Old Version  New Version  Net Change

proton-mail-bin        1.9.0-1      1.9.1-2       10.94 MiB
proton-mail-bin-debug               1.9.1-2        2.74 MiB

... snip ...

error: failed to commit transaction (conflicting files)
proton-mail-bin-debug: /usr/lib/debug/.build-id/0f/d60263ae423cc17f40668f900829657636fd90 exists in filesystem (owned by pgadmin4-desktop-debug)
proton-mail-bin-debug: /usr/lib/debug/.build-id/0f/d60263ae423cc17f40668f900829657636fd90.debug exists in filesystem (owned by pgadmin4-desktop-debug)
... and some more ...

Errors occurred, no packages were upgraded.
 -> error installing: [/home/vetkat/.cache/yay/proton-mail-bin/proton-mail-bin-1.9.1-2-x86_64.pkg.tar.zst /home/vetkat/.cache/yay/proton-mail-bin/proton-mail-bin-debug-1.9.1-2-x86_64.pkg.tar.zst] - exit status 1

Thanks for the fast response! :) i appreciated your support now is working as expected