Hi, I tried both Chrome and Firefox. Neither worked with browser integration.
Followed the discussion in: https://1password.community/discussion/119692/browser-integration-not-working (installation/reinstallation of extensions didn't solve the problem)
1Password startup log shows:
INFO 2021-03-21T16:59:09.712 op_executor:invocation_loop [status:op-app/src/app.rs:149] App::new(1Password for Linux/80028004 (EN_US), /home/username/.config/1Password/1password.sqlite) INFO 2021-03-21T16:59:09.714 op_executor:invocation_loop [1P:native-messaging/op-nm-installer/src/nix_utils.rs:51] Created NMH manifest at /home/username/.config/google-chrome/NativeMessagingHosts/com.1password.1password.json INFO 2021-03-21T16:59:09.714 op_executor:invocation_loop [1P:native-messaging/op-nm-installer/src/nix_utils.rs:65] - Unable to install Native Messaging Host manifest at "/home/username/.config/google-chrome-beta/NativeMessagingHosts/com.1password.1password.json" due to: Io(Os { code: 2, kind: NotFound, message: "No such file or directory" }) INFO 2021-03-21T16:59:09.714 op_executor:invocation_loop [1P:native-messaging/op-nm-installer/src/nix_utils.rs:65] - Unable to install Native Messaging Host manifest at "/home/username/.config/chromium/NativeMessagingHosts/com.1password.1password.json" due to: Io(Os { code: 2, kind: NotFound, message: "No such file or directory" }) INFO 2021-03-21T16:59:09.714 op_executor:invocation_loop [1P:native-messaging/op-nm-installer/src/nix_utils.rs:65] - Unable to install Native Messaging Host manifest at "/home/username/.config/microsoft-edge-dev/NativeMessagingHosts/com.1password.1password.json" due to: Io(Os { code: 2, kind: NotFound, message: "No such file or directory" }) INFO 2021-03-21T16:59:09.714 op_executor:invocation_loop [1P:native-messaging/op-nm-installer/src/nix_utils.rs:65] - Unable to install Native Messaging Host manifest at "/home/username/.config/BraveSoftware/Brave-Browser/NativeMessagingHosts/com.1password.1password.json" due to: Io(Os { code: 2, kind: NotFound, message: "No such file or directory" }) INFO 2021-03-21T16:59:09.714 op_executor:invocation_loop [1P:native-messaging/op-nm-installer/src/nix_utils.rs:76] Installed 1 Native Messaging Host manifests for Chromium INFO 2021-03-21T16:59:09.714 op_executor:invocation_loop [1P:native-messaging/op-nm-installer/src/nix_utils.rs:51] Created NMH manifest at /home/username/.mozilla/native-messaging-hosts/com.1password.1password.json INFO 2021-03-21T16:59:09.714 op_executor:invocation_loop [1P:native-messaging/op-nm-installer/src/nix_utils.rs:76] Installed 1 Native Messaging Host manifests for Firefox ERROR 2021-03-21T16:59:09.922 main [1P:foundation/op-linux/src/bin/keyring_helper.rs:145] keyring helper detected it was not running as root. This could lead to credentials being compromised, aborting! WARN 2021-03-21T16:59:09.922 op_executor:invocation_loop [1P:op-app/src/app/backend/lock_screen.rs:130] Failed to get system unlock availability Enclave(EnclaveInitalization(Io(Custom { kind: UnexpectedEof, error: "failed to fill whole buffer" }))). Defaulting to false! ERROR 2021-03-21T16:59:22.669 main [1P:foundation/op-linux/src/bin/keyring_helper.rs:145] keyring helper detected it was not running as root. This could lead to credentials being compromised, aborting! WARN 2021-03-21T16:59:22.669 op_executor:invocation_loop [1P:op-app/src/app/backend/lock_screen.rs:130] Failed to get system unlock availability Enclave(EnclaveInitalization(Io(Custom { kind: UnexpectedEof, error: "failed to fill whole buffer" }))). Defaulting to false! INFO 2021-03-21T16:59:22.716 tokio-runtime-worker [1P:op-data-layer/src/load.rs:160] loaded 114 items in 4 vaults for account: <redacted> INFO 2021-03-21T16:59:22.722 op_executor:invocation_loop [1P:op-app/src/app/backend/unlock.rs:136] Lock state changed: Unlocked ERROR 2021-03-21T16:59:22.724 main [1P:foundation/op-linux/src/bin/keyring_helper.rs:145] keyring helper detected it was not running as root. This could lead to credentials being compromised, aborting! ERROR 2021-03-21T16:59:22.733 main [1P:foundation/op-linux/src/bin/keyring_helper.rs:145] keyring helper detected it was not running as root. This could lead to credentials being compromised, aborting! WARN 2021-03-21T16:59:22.733 op_executor:invocation_loop [1P:op-app/src/app/backend/lock_screen.rs:130] Failed to get system unlock availability Enclave(EnclaveInitalization(Io(Custom { kind: UnexpectedEof, error: "failed to fill whole buffer" }))). Defaulting to false! INFO 2021-03-21T16:59:26.654 tokio-runtime-worker [1P:op-syncer/src/sync_job.rs:264] synced account <redacted> (0.801765167s)
/home/username/.config/1Password/logs/BrowserSupport/1Password_rCURRENT.log
INFO 2021-03-21T16:54:57.574 main [1P:native-messaging/op-browser-support/src/main.rs:104] Starting 1Password-BrowserSupport INFO 2021-03-21T16:54:57.714 main [1P:native-messaging/op-browser-support/src/main.rs:128] Connection name: 1Password-BrowserSupport INFO 2021-03-21T16:54:57.715 main [1P:native-messaging/op-browser-support/src/main.rs:143] 1Password app connected ERROR 2021-03-21T16:54:57.719 main [1P:native-messaging/op-browser-support/src/main.rs:110] CodecError(Linux(Io(Io { kind: UnexpectedEof, inner: "<redacted>" })))
/home/username/.config/1Password/logs/BrowserSupport/KeyringHelper/1Password_rCURRENT.log
ERROR 2021-03-21T16:54:57.718 main [1P:foundation/op-linux/src/bin/keyring_helper.rs:145] keyring helper detected it was not running as root. This could lead to credentials being compromised, aborting!
1Password Version: 8.0.28
Extension Version: 1.24.5
OS Version: RHEL 8.3
Sync Type: Not Provided
Comments
Team Member
Hey there @ahmadsalah, welcome to the 1Password Support Community! 🎉
Thanks so much for writing in with this - looking at the logs, are you perhaps running Nix as your package manager? If so, this may be the cause of the issue, as Nix runs into issues with setting file permissions properly. If you'd like to try and set those permissions manually,
1Password-KeyringHelper
must be owned by root, with the grouponepassword
. It must also have thesetuid
flag enabled.Hopefully that information is helpful!
Thanks @Dayton_ag for the reply
My package manager is DNF (I was using Yum before upgrading to RHEL 8.3).
The permissions are set as:
And I don't have the group
onepassword
in my system.Team Member
Hi @ahmadsalah,
Did you use the installation steps on our website for CentOS, Fedora, or Red Hat Enterprise Linux (via RPM/DNF), or did you install from an AppImage?
Team Member
I can actually see that the permissions aren't set correctly.
/opt/1Password/1Password-KeyringHelper
needs to have suid enabled, and needs to be part of theonepassword
group. The installation scripts are supposed to handle that.I'll set up an RHEL machine to test it there. I'm guessing that there may be a significant difference between RHEL and Fedora Core.
Thanks @Dayton_ag and @Savanni for the guidance. I don't recall following https://support.1password.com/getting-started-linux/#centos-fedora-or-red-hat-enterprise-linux. But I had the repo configured with
baseurl=https://onepassword.s3.amazonaws.com/linux/rpm
instead ofbaseurl=https://downloads.1password.com/linux/rpm
(probably I used an old version of instructions back then).I did the following:
Unfortunately, this didn't solve my issue. I noticed the following during reinstallation:
My root account was having something incorrect, and I had to reset its password in order to complete the installation successfully.
After resetting root's password (don't know if it was good to reset root's password), I managed to have 1Password running with browser integration working in both Chrome and Firefox.
Thanks again for the support.
Team Member
@ahmadsalah:
Ahh that's great, I'm glad it's sorted out now! Not a problem, we're glad to help. smile: Let us know if there's anything else we can do to assist.
@Dayton_ag one last question, why the
scriptlet: 1password-8.0.30-53266.x86_64
needs to be run assudo
ifdnf install 1password
is already executed byroot
?In my bash (with root user), I was still being asked by the script to enter the
Current password:
Team Member
@ahmadsalah, it doesn't. This will be fixed in the next update, it was meant for other setups but we found that it isn't required there either, so we'll be removing the sudo entirely from the post-install script.
Hi,
I came here to provide the following feedback and wasn't sure if related to this issue or not. Happy to be broken out into it's own thread if it's not related, where I'll provide some additional context
Team Member
Hi @k4n30,
We're looking into it. Can you tell us what distro you're using? This should be mostly fixed already for next's Monday release.