I can't start wayland-native version of 1Password.

I'm having the same issue

```
/opt/1Password/1password --enable-features=UseOzonePlatform --ozone-platform=wayland

INFO 2023-08-11T20:37:18.692 ThreadId(6) [client:typescript] Client starting.
INFO 2023-08-11T20:37:18.776 ThreadId(6) [1P:op-localization/src/lib.rs:227] system locale detected as 'en-GB'
INFO 2023-08-11T20:37:18.776 ThreadId(6) [1P:op-localization/src/lib.rs:253] selected translations for EN_US based on detected locale en-GB
INFO 2023-08-11T20:37:18.776 ThreadId(6) [status:op-app/src/app.rs:519] App::new(1Password for Linux/81009046 (EN_US), /home/$USER/.config/1Password/1password.sqlite)
INFO 2023-08-11T20:37:18.778 ThreadId(6) [1P:data/op-db/src/db.rs:446] Table Integrity Check Succeeded
INFO 2023-08-11T20:37:18.779 ThreadId(6) [1P:data/op-db/src/db.rs:462] DB Integrity Check Succeeded
INFO 2023-08-11T20:37:18.779 ThreadId(6) [1P:data/op-db/src/db.rs:137] Starting DB at version: 29
INFO 2023-08-11T20:37:18.780 ThreadId(6) [1P:ssh/op-ssh-config/src/lib.rs:246] agent configured
INFO 2023-08-11T20:37:18.780 tokio-runtime-worker(ThreadId(4)) [1P:native-messaging/op-native-core-integration/src/lib.rs:324] Starting IPC listener on 1Password-BrowserSupport
INFO 2023-08-11T20:37:18.781 tokio-runtime-worker(ThreadId(1)) [1P:native-messaging/op-native-core-integration/src/lib.rs:336] Active native core integration is awaiting messages
INFO 2023-08-11T20:37:18.781 invocation_loop(ThreadId(13)) [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 2023-08-11T20:37:18.781 invocation_loop(ThreadId(13)) [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 2023-08-11T20:37:18.781 invocation_loop(ThreadId(13)) [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 2023-08-11T20:37:18.781 invocation_loop(ThreadId(13)) [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 2023-08-11T20:37:18.781 invocation_loop(ThreadId(13)) [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 2023-08-11T20:37:18.782 invocation_loop(ThreadId(13)) [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 2023-08-11T20:37:18.782 invocation_loop(ThreadId(13)) [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 2023-08-11T20:37:18.782 invocation_loop(ThreadId(13)) [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 2023-08-11T20:37:18.782 invocation_loop(ThreadId(13)) [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 2023-08-11T20:37:18.782 invocation_loop(ThreadId(13)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:83] Successfully installed all native messaging manifests.
INFO 2023-08-11T20:37:18.782 tokio-runtime-worker(ThreadId(1)) [1P:ssh/op-agent-controller/src/desktop.rs:614] SSH Agent has started.
INFO 2023-08-11T20:37:18.782 tokio-runtime-worker(ThreadId(1)) [1P:ssh/op-agent-controller/src/desktop.rs:433] Starting filesystem watcher for SSH agent configuration directories...
ERROR 2023-08-11T20:37:18.786 tokio-runtime-worker(ThreadId(1)) [1P:/builds/dev/core/core/ssh/op-agent-controller/src/desktop.rs:434] Io(Os { code: 2, kind: NotFound, message: "No such file or directory" })
ERROR 2023-08-11T20:37:18.805 tokio-runtime-worker(ThreadId(3)) [1P:op-global-shortcuts/src/lib.rs:69] AppError at /builds/dev/core/core/op-global-shortcuts/src/node.rs:62:6
binding shortcut

Caused by:
BindRefused

Stack backtrace:
0: op_global_shortcuts::node::bind::{{closure}}
1: op_executor::spawn_no_span::{{closure}}
2: tokio::loom::std::unsafe_cell::UnsafeCell::with_mut
3: std::panicking::try
4: tokio::runtime::task::harness::Harness::poll
5: tokio::runtime::scheduler::multi_thread::worker::Context::run_task
6: tokio::runtime::scheduler::multi_thread::worker::Context::run
7: tokio::macros::scoped_tls::ScopedKey::set
8: tokio::runtime::scheduler::multi_thread::worker::run
9: tokio::loom::std::unsafe_cell::UnsafeCell::with_mut
10: std::panicking::try
11: tokio::runtime::task::harness::Harness::poll
12: tokio::runtime::blocking::pool::Inner::run
13: std::sys_common::backtrace::__rust_begin_short_backtrace
14: core::ops::function::FnOnce::call_once{{vtable.shim}}
15: alloc::boxed::Box%3CF,A as core::ops::function::FnOnce>::call_once
at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library/alloc/src/boxed.rs:1973:9
alloc::boxed::Box%3CF,A as core::ops::function::FnOnce>::call_once
at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library/alloc/src/boxed.rs:1973:9
std::sys::unix::thread::Thread::new::thread_start
at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library/std/src/sys/unix/thread.rs:108:17
16:
17:

ERROR 2023-08-11T20:37:18.805 tokio-runtime-worker(ThreadId(4)) [1P:op-global-shortcuts/src/lib.rs:69] AppError at /builds/dev/core/core/op-global-shortcuts/src/node.rs:62:6
binding shortcut

Caused by:
BindRefused

Stack backtrace:
0: op_global_shortcuts::node::bind::{{closure}}
1: op_executor::spawn_no_span::{{closure}}
2: tokio::loom::std::unsafe_cell::UnsafeCell::with_mut
3: std::panicking::try
4: tokio::runtime::task::harness::Harness::poll
5: tokio::runtime::scheduler::multi_thread::worker::Context::run_task
6: tokio::runtime::scheduler::multi_thread::worker::Context::run
7: tokio::macros::scoped_tls::ScopedKey::set
8: tokio::runtime::scheduler::multi_thread::worker::run
9: tokio::loom::std::unsafe_cell::UnsafeCell::with_mut
10: std::panicking::try
11: tokio::runtime::task::harness::Harness::poll
12: tokio::runtime::blocking::pool::Inner::run
13: std::sys_common::backtrace::__rust_begin_short_backtrace
14: core::ops::function::FnOnce::call_once{{vtable.shim}}
15: alloc::boxed::Box%3CF,A as core::ops::function::FnOnce>::call_once
at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library/alloc/src/boxed.rs:1973:9
alloc::boxed::Box%3CF,A as core::ops::function::FnOnce>::call_once
at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library/alloc/src/boxed.rs:1973:9
std::sys::unix::thread::Thread::new::thread_start
at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library/std/src/sys/unix/thread.rs:108:17
16:
17:

[4262:0811/213718.839084:ERROR:browser_main_loop.cc(274)] Gtk: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
INFO 2023-08-11T20:37:19.124 invocation_loop(ThreadId(13)) [1P:op-app/src/app/backend/lock_screen.rs:72] System unlock is enabled: true
INFO 2023-08-11T20:37:19.139 tokio-runtime-worker(ThreadId(4)) [1P:op-app/src/app/backend/lock_screen.rs:88] Sys auth status NotSetup
```

shell
pacman -Q wayland sway 1password
wayland 1.22.0-1
sway 1:1.8.1-1
1password 8.10.9-46


I can confirm it still doesn't work on the new version, 8.10.13.

Hey @ftpd, @georgealton, thanks for reaching out.

I understand you're encountering issues with starting 1Password on native-wayland. At the moment, running 1Password in an xorg-free environment is not recommended.

This is an issue our team is aware of and requires some further investigation. We don't have a timeline to share regarding this issue.

I apologize for any inconvenience this may cause.

Ali

ref: dev/core/core#11478

Thanks for the response Ali, appreciate the feedback.

Im looking forward to a wayland native version.

George

You're most welcome @georgealton. Let me know if there's anything else we can help with.

Ali

Same problem here :( waiting for Wayland support

Hi @afkmario,

Thanks for your feedback. I'll go ahead and pass along this information to the team.

Franky

Thanks @FrankyO1P. Yes, please pass it along. This used to work until 1Password v8.10.8 (which came with Electron 24). It’s a regression and needs to be fixed.

Thanks for the +1 @Claudi 👍

Just another note confirming that this is a regression introduced in v8.10.8.

It is very disconcerting for a password manager to randomly stop working with a routine upgrade of just the patch version.

Furthermore, it seems that one can not easily downgrade from v8.10.8 to v8.10.7 if one managed to get the higher version intermittently working. Presumably the database schema was updated? Again, this seems rather ill-advised for a patch version update where one would assume backwards compatibility.

I ended up having to completely remove all local user data and freshly sign in to all my accounts to get the older version working again.

@FrankyO1P Given that this issues has remained unaddressed for several months, I think it deserves a higher priority.