Signing back into the Community for the first time? You'll need to reset your password to access your account. Find out more.
Forum Discussion
1Password fails to prompt for approval when using Hyprland
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
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.
I will investigate further this week and see if I can track down what is causing this.
floris_1P1Password Team
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?
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
```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".
