Package Details: proton-mail-bin 1.12.1-1

Git Clone URL: https://aur.archlinux.org/proton-mail-bin.git (read-only, click to copy)
Package Base: proton-mail-bin
Description: Proton official desktop application for Proton Mail and Proton Calendar
Upstream URL: https://proton.me/mail
Keywords: calendar encrypted-email mail privacy privacy-mail proton proton-calendar protonmail protonmail-desktop
Licenses: GPL-3.0-or-later
Conflicts: proton-mail
Provides: proton-mail
Submitter: yochananmarqos
Maintainer: AlphaLynx
Last Packager: AlphaLynx
Votes: 45
Popularity: 1.16
First Submitted: 2024-06-25 22:36 (UTC)
Last Updated: 2026-01-30 02:17 (UTC)

Latest Comments

1 2 3 Next › Last »

lstngr commented on 2026-02-11 05:33 (UTC)

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.

AlphaLynx commented on 2026-02-05 23:12 (UTC)

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.

BitMana commented on 2026-02-04 13:20 (UTC)

FYI - Electron dropped 32-bit Linux support in 2019 so you may want to change your supported architectures.

AlphaLynx commented on 2025-10-30 20:11 (UTC)

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

vetkat commented on 2025-10-30 12:45 (UTC)

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

NextWorks commented on 2025-10-25 13:25 (UTC)

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

AlphaLynx commented on 2025-10-24 16:56 (UTC)

Thanks for the suggestion, NextWorks! Updated

NextWorks commented on 2025-10-23 10:34 (UTC)

The current symlink name “Proton Mail Beta” exceeds the 15-character limit for Linux process names, causing it to appear truncated as “Proton Mail Bet”. It may be preferable to use a shorter symlink name (e.g., protonmail) so that the process name is preserved correctly and can be matched reliably by tools such as NVIDIA’s process rules.

AlphaLynx commented on 2025-08-02 03:47 (UTC) (edited on 2025-09-02 18:55 (UTC) by AlphaLynx)

If anyone knows of or finds a way to query what the latest version binary is with nvchecker let me know! this will help me keep the package up-to-date. (I use pkgctl to check all my packages: see my PKGBUILDs, this depends on a .nvchecker.toml for each package)

edit: I found out from this comment that proton has a simple json api for version data

edit2: Apparently sometimes it doesn't work: proton-mail-bin: current version 1.9.0 is newer than 1.8.1 🙃

kjkent commented on 2025-07-27 22:07 (UTC)

@Joboy thanks! I did report it via their app feedback UI back in May, and after a short conversation, they logged it as a bug in their internal system and said that it's there, but can't give a timeline for fixing it. Mission accomplished I guess!

1 2 3 Next › Last »