Skip to main content
tbjers
tbjers
January 23, 2025
Solved

1Password fails to prompt for approval when using Hyprland

  • January 23, 2025
  • 5 replies
  • 1382 views

I am using Hyprland, a dynamic Wayland compositor.

When I execute git commit -m "chore: initial commit :tada:" I do not see a prompt. The behavior repeats for regular ssh commands as well.

I did some searching but could not find anything specific about this issue anywhere else, so I am posting here. I guess this has something to do with Hyprland being incorrectly identified as Sway somehow.

My debug logs show the following:


DEBUG 2025-01-23T15:43:15.270+00:00 runtime-worker(ThreadId(16)) [1P:ssh/op-ssh-agent/src/lib.rs:261] connection received
DEBUG 2025-01-23T15:43:15.271+00:00 ThreadId(22) [1P:data/op-db/src/core_db/transaction.rs:66] COMMIT(tx#266(get_all_ssh_pubkeys))
DEBUG 2025-01-23T15:43:15.271+00:00 ThreadId(22) [1P:data/op-db/src/core_db/transaction.rs:66] COMMIT(tx#267(get_ssh_pubkey))
DEBUG 2025-01-23T15:43:15.271+00:00 ThreadId(22) [1P:data/op-db/src/core_db/transaction.rs:66] COMMIT(tx#268(save_ssh_pubkey))
DEBUG 2025-01-23T15:43:15.285+00:00 ThreadId(22) [1P:data/op-db/src/core_db/transaction.rs:66] COMMIT(tx#269(get_ssh_pubkey))
DEBUG 2025-01-23T15:43:15.285+00:00 ThreadId(22) [1P:data/op-db/src/core_db/transaction.rs:66] COMMIT(tx#270(save_ssh_pubkey))
DEBUG 2025-01-23T15:43:15.290+00:00 runtime-worker(ThreadId(3)) [1P:ssh/op-ssh-agent/src/lib.rs:541] Handling SSH agent message: RequestIdentities
DEBUG 2025-01-23T15:43:15.291+00:00 ThreadId(22) [1P:data/op-db/src/core_db/transaction.rs:66] COMMIT(tx#271(get_all_ssh_pubkeys))
DEBUG 2025-01-23T15:43:15.291+00:00 ThreadId(22) [1P:data/op-db/src/core_db/transaction.rs:66] COMMIT(tx#272(get_all_ssh_pubkeys))
DEBUG 2025-01-23T15:43:15.291+00:00 ThreadId(22) [1P:data/op-db/src/core_db/transaction.rs:66] COMMIT(tx#273(get_ssh_pubkey))
DEBUG 2025-01-23T15:43:15.291+00:00 ThreadId(22) [1P:data/op-db/src/core_db/transaction.rs:66] COMMIT(tx#274(save_ssh_pubkey))
DEBUG 2025-01-23T15:43:15.296+00:00 ThreadId(22) [1P:data/op-db/src/core_db/transaction.rs:66] COMMIT(tx#275(get_ssh_pubkey))
DEBUG 2025-01-23T15:43:15.296+00:00 ThreadId(22) [1P:data/op-db/src/core_db/transaction.rs:66] COMMIT(tx#276(save_ssh_pubkey))
DEBUG 2025-01-23T15:43:15.301+00:00 runtime-worker(ThreadId(16)) [1P:ssh/op-ssh-agent/src/lib.rs:541] Handling SSH agent message: SignRequest
DEBUG 2025-01-23T15:43:15.302+00:00 runtime-worker(ThreadId(16)) [1P:foundation/op-linux-window/src/linux.rs:40] failed to connect to swaywm
DEBUG 2025-01-23T15:43:15.303+00:00 runtime-worker(ThreadId(16)) [1P:ssh/op-ssh-agent/src/lib.rs:570] process info for client: SessionProcess { pid: 26152, tty_pid: Some(26153), executable_path: /usr/bin/foot, command_line: <Vec < String >>, application_name: <Option < String >>, application_icon: <Option < PathBuf >>, bundle_id: <Option < String >>, freedesktop_file: None }
DEBUG 2025-01-23T15:43:15.303+00:00 ThreadId(22) [1P:data/op-db/src/core_db/transaction.rs:66] COMMIT(tx#277(get_all_ssh_pubkeys))
DEBUG 2025-01-23T15:43:15.426+00:00 runtime-worker(ThreadId(16)) [1P:app/op-app/src/app/backend.rs:360] Invoked: Config
DEBUG 2025-01-23T15:43:15.431+00:00 ThreadId(22) [1P:data/op-db/src/resources_db/transaction.rs:32] COMMIT(tx#114(resource))
INFO 2025-01-23T15:44:15.272+00:00 runtime-worker(ThreadId(10)) [1P:ssh/op-ssh-agent/src/lib.rs:380] ssh authorization prompt timed out
DEBUG 2025-01-23T15:44:15.272+00:00 runtime-worker(ThreadId(10)) [1P:ssh/op-ssh-agent/src/lib.rs:895] Cannot broadcast authorization prompt result; channel closed

1Password gets the request but fails to open the approval window due to the fact that it is trying to connect to swaywm.

FYI: I can connect to the 1Password SSH agent from the terminal, already verified that by looking at a few other community threads.

Is there anything I can do to help further debug or fix this issue? Not sure if this code is open so I can do a PR, but I would be more than happy to do so.

Any help appreciated!

Thank you.

1Password Version: 8.10.54
Extension Version: 8.10.56.28
OS Version: Arch Linux 6.12.10-arch1-1
Browser: Not Provided

    Best answer by

    Hi @bobvanderlinden , 

    Good news, turns out there should be an easy fix for this. 

    • go to Settings > Advanced, enable Hardware Acceleration, quite and restart the app

    Let me know if this works out for you!

    Phil & the 1Password Team!

    5 replies

    floris_1P
    floris_1P
    1Password Employee
    January 24, 2025

    Thanks for providing those logs. Would be good to find out if the culprit lies within the SSH agent or whether it's a general issue with windowing / display management. There are other parts of the app that use a similar window, like Quick Access and the 1Password CLI. Could you try if the window works there?

    P
    paillat
    February 14, 2025

    Not sure if this helps, I am having the exact same issue a the OP, arch linux with hyprland on wayland, and I can confirm that the onepassword cli does not work either. Here is the output of `op vault list`:

    ```

    [ERROR] 2025/02/14 17:54:59 authorization prompt dismissed, please try again
    ```

    H
    HJVT
    February 14, 2025

    It's not that the CLI doesn't work, it's just that it asks the app to unlock, that needs to display the prompt, and the prompt, just like most 1password windows, doesn't show up if it's started in wayland mode. You can use `--ozone-platform-hint=x11` when starting 1password app to force it into x11 mode. You'll need XWayland set up though, and copying from the app might not work.

     

    @floris_1Pgiven the sad state of your app on Wayland, I'm considering my subscription to have been a mistake, and will not be renewing come December, unless I see change. People have been reporting those problems for literal years now, and the only reaction from 1P has been an occasional "we'll pass that on to the team".

      tbjers
      tbjersAuthor
      January 28, 2025

      I will investigate further this week and see if I can track down what is causing this.

      H
      HJVT
      February 11, 2025

      Do you by any chance have any configuration that would force electron-based applications to work in wayland-native mode? In my experience 1Password app is absolutely **bleep**ing broken with `--ozone-platform-hint=wayland`.

      The ways it was broken included running, but not showing any windows except for the Settings window, which sounds fairly similar to what you're experiencing.

      L
      lwndow
      June 10, 2025

      This is 100% what it was for me. Environment variable to encourage Electron apps to use Wayland that it seemingly was respecting (ELECTRON_OZONE_PLATFORM_HINT=auto). As soon as I commented out & logged out, back in, I was able to get the auth prompt like usual. (not the default behavior I want due to wonky font rendering between protocols). I'm sure I had run like this for many moons, so was a surprise to need to do this.

      B
      bobvanderlinden
      July 1, 2025

      I still run into the same problem using `op read`. I created an issue related to NixOS:
      https://github.com/NixOS/nixpkgs/issues/373415

      but this actually seems like a 1password Hyprland compatibility problem.
      8.10.40 was the last working version. Since 8.10.44 (and now 8.10.82) things were failing.

      1password --ozone-platform-hint=x11 indeed is a good workaround for now, but I do get the occasional x11 issues I also get in other applications, like a large cursor, slightly blurry text, excessive blur surrounding popup menus.

      1password works almost flawlessly, it's just those `op read` popups that are totally broken at the moment, making `op` useless.

      For a trace of using `op read` under Hyprland, see: https://github.com/NixOS/nixpkgs/issues/373415#issuecomment-3025200866

        A
        Anonymous
        July 18, 2025

        Hi @bobvanderlinden 

        I'll pass this along to the team and let them know you are still having these troubles.

        Thanks, Phil

        A
        Anonymous
        Answer
        July 18, 2025

        Hi @bobvanderlinden , 

        Good news, turns out there should be an easy fix for this. 

        • go to Settings > Advanced, enable Hardware Acceleration, quite and restart the app

        Let me know if this works out for you!

        Phil & the 1Password Team!

        Terms & ConditionsAccessibility statement

        ©2026 1Password. All rights reserved.
        4711 Yonge St, 10th Floor, Toronto Ontario, M2N 6K8, Canada