Arch Linux User Repository

@DodoGTA, I'm guessing they reset the tags yes, because if you try to build it with checksums, it fails the package integrity, since it dosent match the correct checksum, but I built the package on my other pc and it worked fine so im guessing Proton did some trickery. NodeJS LTS solution is still needed to run, it should be easy enough to implement. Im sorry for how this recent AUR events effected the community and you, I wish you all the best.

@FluffyToast Why would an out-of-date package require skipping checksums to be buildable? I assume Proton (AG) once again reset the tags in their Git repository (and that's why the checksums don't match)

As for the general buildability issues, I'm currently very concerned about potential malicious npm packages infecting my main build/general use system; especially with current events in the AUR (and so I haven't actually built the package in a while)

I'll probably end up using the NodeJS LTS workaround just to make this package work again (because it's a way easier solution)

Notice to everyone (ig), if you wanna run this package while it has not been updated you need to run your installer (I'm gonna give example for makepkg) with "--skipchecksums" otherwise its impossible to build while the package is out of date.

@DodoGTA Electron40 has been released, I built it and it seems to be running without issues, so i guess it can be changed depends array. Also having nodejs-lts-jod works beautifully while nodejs-26 does not seems to work (on all distros).

pkgname=proton-pass
pkgver=1.37.1
pkgrel=3
pkgdesc="Open-source and secure identity manager"
arch=('aarch64' 'x86_64')
url="https://proton.me/pass"
license=('GPL-3.0-or-later')
- depends=('bash' 'gcc-libs' 'glibc' 'electron')
+ depends=('bash' 'gcc-libs' 'glibc' 'electron40')
makedepends=('rust' 'yarn')
conflicts=('proton-pass-bin')
source=("${pkgname}-${pkgver}.tar.gz::https://github.com/ProtonMail/WebClients/archive/refs/tags/${pkgname}@${pkgver}.tar.gz"
        "proton-pass.desktop")

With the new changes, I no longer need npm to build this package. However, it still freezes with the default nodejs package installed (nodejs-26). The only way I found to overcome this hurdle is by adding nodejs-lts-jod to the makedepends array.

In addition, I still think it would be nice to include the hack I mentioned here to replace the Wayland icon with the Proton Pass icon on the window frame. I don't know if this occurs in all window managers, but it does on KDE Plasma. Please check these screenshots to better understand what I'm talking about.

Thanks.

@DodoGTA, I had to add npm to the makedepends array to pass this error: https://pastebin.com/4Vb41pvq

From there the code compiles well but it hangs up on the packaging step of the yarn exec command within the build() function. After a long waiting time with no activity, I have to press Ctrl+C to cancel the process. This is what I get: https://pastebin.com/6UaisFfh

At this point, when I run makepkg -crs to build the app, the following packages are installed on my box:

==> Installing missing dependencies...
resolving dependencies...
looking for conflicting packages...

Packages (8) ada-3.4.4-1  node-gyp-12.3.0-1  nodejs-26.2.0-1  nodejs-nopt-10.0.0-1  semver-7.8.1-1  simdjson-1:4.6.4-1  npm-11.14.1-1  yarn-1.22.22-2

Further looking into, I noticed that both Debian and Red Hat oficial binaries distributed by Proton use Electron39 and Nodejs v22 which seems to be the most widely adopted versions right now in Arch. This is what I found on the DEB and RPM packages:

[musikolo@MyPC tmp]$ strings proton-pass_1.37.0_amd64/usr/lib/proton-pass/Proton\ Pass | grep "Electron v\|node.js/v"
Electron v39.8.4
node.js/v22.22.1
[musikolo@MyPC tmp]$ strings proton-pass-1.37.0-1.x86_64/usr/lib/proton-pass/Proton\ Pass | grep "Electron v\|node.js/v"
Electron v39.8.4
node.js/v22.22.1

Finnally, by replacing electron with electron39 in the depends dependency array and adding nodejs-lts-jod to the makedepends array, I was able to build this package successfully!

[musikolo@MyPC proton-pass]$ diff -Nru PKGBUILD.orig PKGBUILD
--- PKGBUILD.orig       2026-05-23 04:34:39.000000000 -0500
+++ PKGBUILD    2026-05-23 16:50:28.878988923 -0500
@@ -11,8 +11,8 @@
 arch=('aarch64' 'x86_64')
 url="https://proton.me/pass"
 license=('GPL-3.0-or-later')
-depends=('bash' 'gcc-libs' 'glibc' 'electron')
-makedepends=('rust' 'yarn')
+depends=('bash' 'gcc-libs' 'glibc' 'electron39')
+makedepends=('rust' 'yarn' 'npm' 'nodejs-lts-jod')
 conflicts=('proton-pass-bin')
 source=("${pkgname}-${pkgver}.tar.gz::https://github.com/ProtonMail/WebClients/archive/refs/tags/${pkgname}@${pkgver}.tar.gz"
         "proton-pass.desktop")

I hope it helps.

@DodoGTA, I found better way to handle the issues with the logo icon that not only doesn't require changing the proton-pass.desktop file, but it also solves the issue with Wayland icon on Electron window frame. All it takes is applying the following hack in the prepare() function of the PKGBUILD file:

# HACK: Set Proton Pass icon on the window frame
sed -i 's@opacity: 1,@opacity: 1, icon: "/usr/share/proton-pass/assets/logo.png",@' applications/pass-desktop/src/main.ts

However, to make it look really nice, it would be nice to convert the logo.svg file into PNG format and use it here. If you could do this it would be fantastic!

Regards.

@DodoGTA, I noticed Proton Pass starts in a separate Wayland window which displays the W yellow Wayland icon on the taskbar. Since that looks awful, I played with a few things and I think I found a way to correct this issue. All it takes is applying the following changes in the proton-pass.desktop file:

diff --git a/proton-pass-orig.desktop b/proton-pass.desktop
index 82b9332..77692bb 100644
--- a/proton-pass-orig.desktop
+++ b/proton-pass.desktop
@@ -2,7 +2,8 @@
 Name=Proton Pass
 Comment=Proton Pass desktop application
 GenericName=Password Manager
-Exec=proton-pass %U
+Path=/usr/share/proton-pass
+Exec=electron app.asar
 Icon=proton-pass
 Type=Application
 StartupNotify=true

Please consider adding this enhancement. Thanks for maintaining this package.

Regards.

@jordanbcx I guess the Proton (AG) team reset their tags again (anyway I updated the checksum)

Edit build files with updated integrity if it fails:

sha256sums=('9d53fbcbe607657818f8c32bc2a4cf22ab399c11fc1045490053879b739f1171' '501210c67fc921a2fb4ba591980192ad1da60e26fb6b2fd7d68aad4075eafac7')