Arch Linux User Repository

Hi, release notes: https://docs.keeper.io/en/release-notes/desktop/web-vault-+-desktop-app/vault-release-17.3.1 https://docs.keeper.io/en/release-notes/desktop/web-vault-+-desktop-app/vault-release-17.3.2

Hi,

Release notes: https://docs.keeper.io/en/release-notes/desktop/web-vault-+-desktop-app/vault-release-17.3

Hi,

Vault was released today (2025.02.06) with version 17.0.0. Previous version: 16.11.3 Theoretically a big version change, but I only see the electron version change as big.

I use it often on linux and android, I haven't experienced any problems so far. Please let me know if you experience any problems.

Release notes: https://docs.keeper.io/en/release-notes/desktop/web-vault-+-desktop-app/vault-release-17.0.0

Hi. Former maintainer here.

The issue is that the software is built for x86_64 (and the stuff it depends on and comes with is, too) and you run arm64. Different CPU architecture. Having a maintainer who is enthusiastic about ARM won't change that incompatibility.

Also. This application is a glorified version of the Keeper Web Vault you access via web browser. That's why Electron is mentioned.

I recommended you contact Keeper directly. If they will build it for ARM, it can then be implemented here (and you can be said ARM enthusiast and maintainer). :)

Maybe someday a second person will try to install Keeper on aarch64 Linux and they'll think about supporting it :)

Keeper password manager is an electron-based application, so you may see chrome references.

You don't need to install the chrome browser for electron applications, because chromium and nodejs contain all the necessary components embedded in a binary: https://www.electronjs.org/docs/latest/

Keeper did not create an arm64 debian package: https://keepersecurity.com/desktop_electron/SHASUM256.txt This PKGBUILD always downloads the amd64 debian package, no matter if you change the platform:

source=("https://keepersecurity.com/desktop_electron/Linux/repo/deb/keeperpasswordmanager_${pkgver}_amd64.deb"

If you download the debian package and unpack it (or e.g. makepkg -s), you can see in the control.tar.xz/control file that the architecture of the package is amd64. From this, I think that this package cannot be run on arm-based machines. If I'm wrong, I'll be happy :)

Looking at this with fresh eyes, it may be simply that the Keeper .deb being retrieved is for amd64, and I am on arm64. Likely for this package, one does not simply set arch=aarch64.

I see many references in /usr/lib/keeperpasswordmanager/ to chrome and chromium. Is this referring to the Google products? Is it relying on Chrome to be installed on the machine? I do not have Chrome installed.

I may try starting from the top, now that I have a little better understanding. I'll pacman -R the package, do a fresh git clone, update the sha512 with the bumpversion.sh script that I failed to notice the first time, add aarch64, and makepkg -sic. No chmods this time, as that didn't make a difference and I am not updating from a previous version. I'll report my results here. Maybe I just missed something the first time.

@brnl: Thanks for reply. For context, I'm running Manjaro because it shipped with Pinebook Pro, and I had no reason to change. Had for a couple years, but only now committing to Linux as daily driver. This is only the third package I have tried to install from AUR. I have only ever followed advice from Arch forums; didn't even know pamac existed LOL.

If I recall correctly, I had to add aarch64 as a target, and update the sha512 for the latest version in the PKGBUILD. Then I built with: $ makepkg -sic

@forgetfulSpies: If applicable; Please don't forget to run pamac as normal user for AUR builds. Running with sudo might sometimes result in unexpected problems.