Arch Linux User Repository

1Password for Arch Linux - Stable

The source is signed with the GPG key 3FEF9748469ADBE15DA7CA80AC2D62742012EA22 and can be seen on the install-linux guide.

Getting Started

Our getting started guide can be found at https://support.1password.com/install-linux/#arch-linux

Support

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

Beta Releases

Our beta releases can be found at 1password-beta. Beta releases are more likely to have regressions than our stable releases.

aarch64 builds can be obtained through https://downloads.1password.com/linux/tar/stable/aarch64/1password-latest.tar.gz

If the PKGBUILD could be adapted for this, it would be great.

Thanks for providing this package!

I checked the PKGBUILD before installing and thought I should mention that for those of us who build their AUR packages in a chroot or otherwise isolated environment, the "first 10 human users of the system" are unlikely to match the target system.

It looks like the PolicyKit file generated at build time only surfaces this data in an annotation, so it's not a security issue, but it might be worth considering an install script instead?

Can we enable wayland support of 1password via add flags:

--ozone-platform-hint=auto

Beautiful application and seamless install - thank you @1password

Edit: Turns out I broke something on my end, sorry for any inconvenience caused.

You don't need to chmod the helper after installation via the install script; you can just do this when packaging and install the file with the right mode bits.

Here's a patch:

diff --git a/1password.install b/1password.install
index e752514..156badc 100755
--- a/1password.install
+++ b/1password.install
@@ -9,12 +9,6 @@ app_group_exists() {
     fi
 }

-set_chromesandbox_permissions() {
-    # chrome-sandbox requires the setuid bit to be specifically set.
-    # See https://github.com/electron/electron/issues/17972
-    chmod 4755 /opt/1Password/chrome-sandbox
-}
-
 setup_browser_helper() {
     # Setup the Core App Integration helper binary with the correct permissions and group
     HELPER_PATH="/opt/1Password/1Password-KeyringHelper"
@@ -46,12 +40,10 @@ pre_upgrade() {
 }

 post_install() {
-    set_chromesandbox_permissions
     setup_browser_helper
 }

 post_upgrade() {
-    set_chromesandbox_permissions
     setup_browser_helper
 }

diff --git a/PKGBUILD b/PKGBUILD
index 2e5a93e..680429f 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -46,4 +46,8 @@ package() {
     # Symlink /usr/bin executable to opt
     install -dm0755 "${pkgdir}"/usr/bin
     ln -s /opt/1Password/1password "${pkgdir}"/usr/bin/1password
+
+    # chrome-sandbox requires the setuid bit to be specifically set.
+    # See https://github.com/electron/electron/issues/17972
+    chmod 4755 "${pkgdir}"/opt/1Password/chrome-sandbox
 }

@1Password why did you remove the ability to use Polkit authentication on first startup?

Hi, what version of electron is this using? I would like to enable Wayland support for Electron-based apps (such as 1Password 8) and to do so, I need to know the version to name the config file (see: https://wiki.archlinux.org/title/wayland#Electron). Does 1Password pick up config files from the $USER/.config/ directory, or will I have to do something else to get Wayland working with it?

You don't need to chmod the helper via the install script (e.g.: at install time), you can just do this when packaging.

Here's a diff:

diff --git a/1password.install b/1password.install
index e752514..156badc 100755
--- a/1password.install
+++ b/1password.install
@@ -9,12 +9,6 @@ app_group_exists() {
     fi
 }

-set_chromesandbox_permissions() {
-    # chrome-sandbox requires the setuid bit to be specifically set.
-    # See https://github.com/electron/electron/issues/17972
-    chmod 4755 /opt/1Password/chrome-sandbox
-}
-
 setup_browser_helper() {
     # Setup the Core App Integration helper binary with the correct permissions and group
     HELPER_PATH="/opt/1Password/1Password-KeyringHelper"
@@ -46,12 +40,10 @@ pre_upgrade() {
 }

 post_install() {
-    set_chromesandbox_permissions
     setup_browser_helper
 }

 post_upgrade() {
-    set_chromesandbox_permissions
     setup_browser_helper
 }

diff --git a/PKGBUILD b/PKGBUILD
index 2e5a93e..680429f 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -46,4 +46,8 @@ package() {
     # Symlink /usr/bin executable to opt
     install -dm0755 "${pkgdir}"/usr/bin
     ln -s /opt/1Password/1password "${pkgdir}"/usr/bin/1password
+
+    # chrome-sandbox requires the setuid bit to be specifically set.
+    # See https://github.com/electron/electron/issues/17972
+    chmod 4755 "${pkgdir}"/opt/1Password/chrome-sandbox
 }

I noticed there's some gitlab CI set up in the repo. Is there somewhere better to send an MR instead of a patch here?

Please stop flagging this package as out-of-date for beta releases. If you want the beta versions go to 1password-beta