Arch Linux User Repository

Our Linux support discussion is available at https://1password.community/categories/linux-beta

1Password now signs releases, so signature checking has been added back into the PKGBUILD. If you encounter an error importing their GPG key or an error because of a missing GPG key, you may import it manually:

gpg --keyserver keyserver.ubuntu.com --recv-keys 3FEF9748469ADBE15DA7CA80AC2D62742012EA22

They've published their key on their support page, here: https://support.1password.com/cs/getting-started-linux/

You know what this seems to have been only an issue with Brave-beta. Everything else is just working without my manifests. Also, I may have been using the non-beta extension in Chromium at first, which doesn't work with the native app, so I may have mistakenly believed it wasn't working too.

It appears that the 1Password app creates the manifests in the browser config directories it finds on startup. I didn't have Brave installed, but had a config directory lying around from a previous install, and it had the manifest created in the users config directory.

I mainly use Chromium and Brave-beta. I only today realized that native app integration was supposed to be enabled on Linux, and got about finding why it wasn't working for me.

The integration started working after I added these manifests, in Chromium and Brave. I only checked Chrome afterwards, and assumed it wouldn't have been working before.

That's weird, I didn't have to do anything for 1password to integrate with the google-chrome-stable package.

Manifests can be written in user directory, which the app should do (haven't checked myself: did you enable browser integration in the settings?)

I have a patch to this PKGBUILD to create native-messaging-host configs for Chrome and Chromium, which allows the browser extensions for reliably communicate with the app.

I'm not sure what is the right way to provide submit this change to this AUR repo, but my patch can be found at https://github.com/kshlm/pkgbuilds/commit/159aed38500c055111dc838d6ddbd644e17c4298.patch

This can be applied directly onto this repo with,git am -p2 159aed38500c055111dc838d6ddbd644e17c4298.patch

I've tested this with Chrome, Chromium and Brave/Brave-beta, and this enables the extensions in these browsers to be unlocked by the desktop app.

I suggess adding "libappindicator-gtk3" as an optional dependency.

Without it, the 1password statusbar icon will not show on GNOME even with the AppIndicator extension. It wasn't super fun to figure that out.

Our Linux support discussion is available at https://1password.community/categories/linux-beta

@Feakster Thanks for the suggestion. We will keep it in mind as our Linux support continues to grow.

Would you be able to make this a multi-arch package once you start using the tar instead of the AppImage? The arm architectures have a growing user base on Arch & Manjaro.

@Orangutan We actually have some plans to base the install on a tar instead of the AppImage. While we get that ready we plan on keeping this based on the AppImage.

Wouldn’t using the .deb be nicer and simpler? It’s what packages usually do in this situation