[Bug]: 1password extension isn't seeing 1password installed on Linux

[rudidev08]

Operating system

Linux (Fedora 43, Kionite, UBlue Aurora)

Version

Version 0.7.10.1 (Official Build, Chromium 143.0.7499.192) appimage (64-bit)

Have you tested that this is not an upstream issue or an issue with your configuration?

• I have tried reproducing this issue in Chrome and it could not be reproduced there
• I have tried reproducing this issue in ungoogled-chromium and it could not be reproduced there
• I have tried reproducing this issue in Helium with a new and empty profile using --user-data-dir command line argument and it could not be reproduced there

Description

1password extension installed via chrome web extension store doesn't see 1password on OS

How to Reproduce?

1. Install 1password on linux OS
2. (for immutable fedora such as kionite, use layering. flatpak and snap 1password is sandboxed)
3. (for immutable fedora like aurora, there's ublue brew tap that has 1password install script)
4. (for regular fedoras, use dnf install steps from 1password website)
5. (for all those installs, confirm in 1password that app has access to SSH agent and such - this is a sign that it's not sandboxed)
6. Install 1password extension in Helium from Chrome Web Extension store

Actual behavior

In initial extension setup, extension won't see OS 1password, and therefore won't login user automatically

Expected behavior

In initial extension setup, 1password on OS should be detected, and user should be logged in automatically.

Additional context

Confirmed on Fedora 43 with KDE, Kionite, and Aurora.

[thaiiko]

have you tried https://support.1password.com/additional-browsers/. this guide should help

…

On Wed, Jan 14, 2026 at 12:09 AM Rudi ***@***.***> wrote: *rudidev08* created an issue (imputnet/helium-linux#168) <#168> Operating system Linux Version Version 0.7.10.1 (Official Build, Chromium 143.0.7499.192) appimage (64-bit) Have you tested that this is not an upstream issue or an issue with your configuration? - I have tried reproducing this issue in Chrome and it could not be reproduced there - I have tried reproducing this issue in ungoogled-chromium and it could not be reproduced there - I have tried reproducing this issue in Helium with a new and empty profile using --user-data-dir command line argument and it could not be reproduced there Description 1password extension installed via chrome web extension store doesn't see 1password on OS How to Reproduce? 1. Install 1password on linux OS 2. (for immutable fedora such as kionite, use layering. flatpak and snap 1password is sandboxed) 3. (for immutable fedora like aurora, there's ublue brew tap that has 1password install script) 4. (for regular fedoras, use dnf install steps from 1password website) 5. (for all those installs, confirm in 1password that app has access to SSH agent and such - this is a sign that it's not sandboxed) 6. Install 1password extension in Helium from Chrome Web Extension store Actual behavior In initial extension setup, extension won't see OS 1password, and therefore won't login user automatically Expected behavior In initial extension setup, 1password on OS should be detected, and user should be logged in automatically. Additional context Confirmed on Fedora 43 with KDE, Kionite, and Aurora. — Reply to this email directly, view it on GitHub <#168>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BJ57U32OUPCMNVUA4UIBFNT4GXMRBAVCNFSM6AAAAACRUERQLCVHI2DSMVQWIX3LMV43ASLTON2WKOZTHAYTCNZTGI3TMMY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[NGPixel]

I have the same issue and the guide above didn't help. This is most likely related to Helium being only available as an AppImage on Linux?

I'm using Fedora 43 Workstation.

[rudidev08]

have you tried
https://support.1password.com/additional-browsers/. this guide should help
…

I tried with these steps: https://support.1password.com/additional-browsers/?linux

with no luck. I had binary name as helium-browser and helium

So it seems that might be on 1password to fix, maybe.

Agree with NGPixel that could be AppImage related

[meatcar]

I'm also experiencing this issue. On my system (NixOS 25.11) I'm seeing the following 1Password log after running the Helium AppImage:

$ cat $(find ~/.config/1Password/logs/BrowserSupport/ | tail -n 1)
INFO  2026-01-21T23:26:47.884+00:00 main(ThreadId(1)) [1P:native-messaging/op-browser-support/src/main.rs:392] Starting 1Password-BrowserSupport 8.11.22 production build no. 81122027.
ERROR 2026-01-21T23:26:47.884+00:00 main(ThreadId(1)) [1P:foundation/op-binary-support/src/linux.rs:99] process detected it was running without libc's security, aborting

This feels like an AppImage sandbox issue. There's a solution for flatpak, but I'm not sure how to apply it to AppImages.