1password desktop + Firefox extension on Fedora Asahi (M1)

minttamas · February 19

I'm running Fedora Asahi on my M1 macbook pro. I was able to install the 1password desktop app arm64 version and I can open it (although, I had to set WAYLAND_DISPLAY, but it runs fine).

However, the Firefox extension does not detect the desktop app, e.g. it stays locked when the app is unlocked, and it doesn't defer unlocking to the app when I try to unlock it. It acts as if the app is not installed at all. I disabled SELinux and ensured that firefox is running as a native app (not a flatpak or snap). Did anyone manage to run it successfully?

The desktop app prints the following logs. I don't know if the errors and that one warning are really consequential. It's odd that it's trying to connect to an X server though.

$ env -u WAYLAND_DISPLAY 1password
INFO  2024-02-17T22:16:50.781 ThreadId(10) [1P:foundation/op-log/src/lib.rs:673] Removed 10 old log files
INFO  2024-02-17T22:16:50.784 ThreadId(10) [client:typescript] Client starting.
ERROR 2024-02-17T22:16:51.394 ThreadId(10) [1P:op-crash-reporting/src/crash_report.rs:181] Failed to load crash reports from disk: Os { code: 2, kind: NotFound, message: "No such file or directory" }
INFO  2024-02-17T22:16:51.399 ThreadId(10) [1P:op-localization/src/lib.rs:227] system locale detected as 'en-US'
INFO  2024-02-17T22:16:51.400 ThreadId(10) [1P:op-localization/src/lib.rs:253] selected translations for EN_US based on detected locale en-US
INFO  2024-02-17T22:16:51.400 ThreadId(10) [status:op-app/src/app.rs:560] App::new(1Password for Linux/81023003 (EN_US), /home/$USER/.config/1Password/1password.sqlite, /home/$USER/.config/1Password/1password_resources.sqlite)
INFO  2024-02-17T22:16:51.431 ThreadId(10) [1P:data/op-db/src/common/mod.rs:120] Core DB Table Integrity Check Succeeded
INFO  2024-02-17T22:16:51.437 ThreadId(10) [1P:data/op-db/src/common/mod.rs:134] Core DB Integrity Check Succeeded
INFO  2024-02-17T22:16:51.437 ThreadId(10) [1P:data/op-db/src/core_db/db.rs:163] Starting Core DB at version: 30
INFO  2024-02-17T22:16:51.439 ThreadId(10) [1P:data/op-db/src/common/mod.rs:120] Resources DB Table Integrity Check Succeeded
INFO  2024-02-17T22:16:51.439 ThreadId(10) [1P:data/op-db/src/common/mod.rs:134] Resources DB Integrity Check Succeeded
INFO  2024-02-17T22:16:51.440 ThreadId(10) [1P:data/op-db/src/resources_db/db.rs:131] Starting Resources DB at version: 1
ERROR 2024-02-17T22:16:51.442 ThreadId(10) [1P:/builds/dev/core/core/ssh/op-ssh-config/src/lib.rs:183] Failed to start ssh config file watcher: Io(Os { code: 2, kind: NotFound, message: "No such file or directory" })
INFO  2024-02-17T22:16:51.445 tokio-runtime-worker(ThreadId(8)) [1P:native-messaging/op-native-core-integration/src/lib.rs:329] Starting IPC listener on 1Password-BrowserSupport
INFO  2024-02-17T22:16:51.445 tokio-runtime-worker(ThreadId(8)) [1P:native-messaging/op-native-core-integration/src/lib.rs:341] Active native core integration is awaiting messages
INFO  2024-02-17T22:16:51.445 tokio-runtime-worker(ThreadId(1)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/$USER/.config/google-chrome/NativeMessagingHosts/com.1password.1password.json
INFO  2024-02-17T22:16:51.445 tokio-runtime-worker(ThreadId(1)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/$USER/.config/google-chrome-beta/NativeMessagingHosts/com.1password.1password.json
INFO  2024-02-17T22:16:51.446 tokio-runtime-worker(ThreadId(1)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/$USER/.config/google-chrome-unstable/NativeMessagingHosts/com.1password.1password.json
INFO  2024-02-17T22:16:51.446 tokio-runtime-worker(ThreadId(1)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/$USER/.config/chromium/NativeMessagingHosts/com.1password.1password.json
INFO  2024-02-17T22:16:51.446 tokio-runtime-worker(ThreadId(1)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/$USER/.config/microsoft-edge-dev/NativeMessagingHosts/com.1password.1password.json
INFO  2024-02-17T22:16:51.446 tokio-runtime-worker(ThreadId(1)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/$USER/.config/BraveSoftware/Brave-Browser/NativeMessagingHosts/com.1password.1password.json
INFO  2024-02-17T22:16:51.446 tokio-runtime-worker(ThreadId(1)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/$USER/.config/vivaldi/NativeMessagingHosts/com.1password.1password.json
INFO  2024-02-17T22:16:51.446 tokio-runtime-worker(ThreadId(1)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/$USER/.config/vivaldi-snapshot/NativeMessagingHosts/com.1password.1password.json
INFO  2024-02-17T22:16:51.447 tokio-runtime-worker(ThreadId(1)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/$USER/.mozilla/native-messaging-hosts/com.1password.1password.json
INFO  2024-02-17T22:16:51.447 tokio-runtime-worker(ThreadId(1)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:83] Successfully installed all native messaging manifests.
INFO  2024-02-17T22:16:51.448 tokio-runtime-worker(ThreadId(1)) [1P:ssh/op-agent-controller/src/desktop.rs:438] Starting filesystem watcher for SSH agent configuration directories...
ERROR 2024-02-17T22:16:51.449 tokio-runtime-worker(ThreadId(1)) [1P:/builds/dev/core/core/ssh/op-agent-controller/src/desktop.rs:439] Io(Os { code: 2, kind: NotFound, message: "No such file or directory" })
INFO  2024-02-17T22:16:51.788 tokio-runtime-worker(ThreadId(1)) [1P:op-app/src/app/backend/lock_screen.rs:92] System unlock is enabled: true
WARN  2024-02-17T22:16:51.791 tokio-runtime-worker(ThreadId(13)) [1P:foundation/op-linux/src/kernel_keyring.rs:840] failed to initialize keyring helper, its functionality will be unavailable: Io(Error { kind: UnexpectedEof, message: "failed to fill whole buffer" })
INFO  2024-02-17T22:16:51.791 tokio-runtime-worker(ThreadId(1)) [1P:op-app/src/app/backend/lock_screen.rs:117] Sys auth status NotSetup
INFO  2024-02-17T22:16:57.621 tokio-runtime-worker(ThreadId(3)) [1P:op-app/src/app/backend/lock_screen.rs:92] System unlock is enabled: true
INFO  2024-02-17T22:16:57.698 tokio-runtime-worker(ThreadId(1)) [1P:/builds/dev/core/core/data/ext/op-account-ext-settings-authentication/src/lib.rs:187] loaded settings authentication key: a8877e4de81237c1
INFO  2024-02-17T22:16:57.717 tokio-runtime-worker(ThreadId(1)) [1P:data/ext/op-account-ext-items/src/lib.rs:262] loaded 1305 items in 7 vaults for account: WOP2ONKAIJFBJNETIGBQWQL3KY
ERROR 2024-02-17T22:16:57.719 tokio-runtime-worker(ThreadId(1)) [1P:op-auto-lock/src/linux.rs:209] Could not connect to the X server: XcbEventError
INFO  2024-02-17T22:16:57.720 tokio-runtime-worker(ThreadId(1)) [1P:op-settings/src/store/json_store.rs:685] initializing settings authentication with key a8877e4de81237c1
INFO  2024-02-17T22:16:57.720 tokio-runtime-worker(ThreadId(1)) [1P:op-app/src/app/backend/unlock.rs:133] Lock state changed: Unlocked
INFO  2024-02-17T22:16:57.720 tokio-runtime-worker(ThreadId(1)) [1P:op-app/src/app/backend/unlock.rs:164] Processing unlocked account WOP2ONKAIJFBJNETIGBQWQL3KY
INFO  2024-02-17T22:16:57.738 tokio-runtime-worker(ThreadId(3)) [1P:data/op-account-system-unlock/src/lib.rs:518] Adding system unlock key. Verifying keysets can be decrypted.
INFO  2024-02-17T22:16:57.741 tokio-runtime-worker(ThreadId(3)) [1P:data/op-account-system-unlock/src/lib.rs:524] Adding system unlock key. Encrypting muk.
INFO  2024-02-17T22:16:57.741 ThreadId(15) [1P:data/op-account-system-unlock/src/lib.rs:530] Adding system unlock key. Updating account.
INFO  2024-02-17T22:16:58.776 tokio-runtime-worker(ThreadId(2)) [1P:op-b5-client/src/internal/unauthorized_session.rs:1261] Verifying device secret (MFA) with server...
INFO  2024-02-17T22:16:58.943 tokio-runtime-worker(ThreadId(2)) [1P:op-b5-client/src/internal/unauthorized_session.rs:917] Device secret was verified
INFO  2024-02-17T22:16:58.943 tokio-runtime-worker(ThreadId(2)) [1P:op-b5-client/src/internal/unauthorized_session.rs:935] No new device secret was given as current one is still valid and verified
INFO  2024-02-17T22:16:59.596 tokio-runtime-worker(ThreadId(1)) [1P:data/ext/op-account-ext-syncer/src/lib.rs:249] The B5 Notifier for (WOP2ONKAIJFBJNETIGBQWQL3KY) has connected, now monitoring for events.
INFO  2024-02-17T22:16:59.891 tokio-runtime-worker(ThreadId(2)) [1P:op-syncer/src/sync_job.rs:313] synced account WOP2ONKAIJFBJNETIGBQWQL3KY (0.946008787s)
INFO  2024-02-17T22:16:59.892 tokio-runtime-worker(ThreadId(2)) [1P:data/op-file-transfer/src/lib.rs:561] find_and_complete_pending_uploads: 'WOP2ONKAIJFBJNETIGBQWQL3KY'

1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Browser: Not Provided

FrankyO1P · February 21

Hi @minttamas

Thanks for bringing this to our attention. This is an interesting issue and I would love to investigate into this issue further.

Could you send an email to support+linux@1Password.com?

With your email please include:

A link to this thread: https://1password.community/discussion/144505/1password-desktop-firefox-extension-on-fedora-asahi-m1
Your forum username: minttamas
A diagnostics report: https://support.1password.com/diagnostics/?linux
An extension console log: https://support.1password.com/cs/extension-console-log/
Information about your current environment (Linux distribution, version, desktop environment)

We'll look forward to hearing from you.

Franky

minttamas · February 28

For anyone reaching this post via Google in the future, the root cause was incorrect permissions set on the 1password installation files. This is something the RPM or DEB takes care of, but on arm64 there is (for now) only a tarball. In my case, I had to

sudo chown -R root:root /opt/1password
sudo /opt/1Password/after-install.sh

After that, it started to work.

1password desktop + Firefox extension on Fedora Asahi (M1)

Comments