zechel, thank you for your help, it was very thorough, you gave me everything on a platter, I appreciate it. I haven't set up a test system to find bugs yet, but I'll work on it later, because I see that it is necessary

After your tip, I looked through the debian package description and tried to find more bugs using namcap. I added what I found. There must be a library that namcap doesn't see (runtime loaded, maybe libsecret).

Unfortunately, I didn't have more time right now, but as soon as I get free time, I'll develop that too.

Missing runtime dependency: pcsclite (causes blank/blue window)

### Symptom

On a fresh install of keeper-password-manager 17.5.2-1, the app launches and the native window/menu bar (File, Edit, Settings, View, Window, Help) renders correctly, but the entire content area is a solid blue background — the login form never appears. No visible error is shown to the user.

### Root cause

The renderer process throws a fatal unhandled promise rejection during startup:

Uncaught (in promise) Error: libpcsclite.so.1: cannot open shared object file: No such file or directory source: file:///usr/lib/keeperpasswordmanager/resources/app.asar/vault/js/vault.js

This halts the SPA bootstrap before the login UI mounts, leaving only the splash background visible. Captured with:

keeperpasswordmanager --enable-logging=stderr --v=1

libpcsclite.so.1 is provided by the official pcsclite package (repo: extra), but it is not pulled in by any current dependency of this AUR package, so a clean Arch install does not have it.

### Fix (user side)

sudo pacman -S pcsclite

After installing, the app opens normally — no Chromium flags or GPU workarounds required.

### Suggested PKGBUILD change

Add pcsclite to depends=() so this works out of the box:

depends=('... existing deps ...' 'pcsclite')

### Environment

• Arch Linux (rolling, kernel 6.19.x)
• Hyprland on Wayland (XWayland available)
• Intel Iris Xe Graphics (TigerLake-LP)
• keeper-password-manager 17.5.2-1 (Electron 37.7.1 / Chromium 138)

Hope this helps the maintainer and saves others the troubleshooting. Thanks for packaging Keeper!

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 :)

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.