Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
Forum Discussion
I can't start wayland-native version of 1Password.
When I try to run 1password with the well-known OzonePlatform, I get the following:
```
INFO 2023-08-07T22:51:44.006 ThreadId(14) [client:typescript] Client starting.
INFO 2023-08-07T22:51:44.114 ThreadId(14) [1P:op-localization/src/lib.rs:227] system locale detected as 'en-US'
INFO 2023-08-07T22:51:44.114 ThreadId(14) [1P:op-localization/src/lib.rs:253] selected translations for EN_US based on detected locale en-US
INFO 2023-08-07T22:51:44.114 ThreadId(14) [status:op-app/src/app.rs:519] App::new(1Password for Linux/81009046 (EN_US), /$USER/.config/1Password/1password.sqlite)
INFO 2023-08-07T22:51:44.117 ThreadId(14) [1P:data/op-db/src/db.rs:446] Table Integrity Check Succeeded
INFO 2023-08-07T22:51:44.118 ThreadId(14) [1P:data/op-db/src/db.rs:462] DB Integrity Check Succeeded
INFO 2023-08-07T22:51:44.118 ThreadId(14) [1P:data/op-db/src/db.rs:137] Starting DB at version: 29
INFO 2023-08-07T22:51:44.187 ThreadId(14) [1P:ssh/op-ssh-config/src/lib.rs:248] agent not configured
INFO 2023-08-07T22:51:44.188 tokio-runtime-worker(ThreadId(9)) [1P:native-messaging/op-native-core-integration/src/lib.rs:281] Mute native core integration is waiting for Shared Lock State to be enabled
INFO 2023-08-07T22:51:44.189 tokio-runtime-worker(ThreadId(9)) [1P:ssh/op-agent-controller/src/desktop.rs:433] Starting filesystem watcher for SSH agent configuration directories...
ERROR 2023-08-07T22:51:44.189 tokio-runtime-worker(ThreadId(9)) [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-07T22:51:44.209 tokio-runtime-worker(ThreadId(1)) [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
3: std::panicking::try
4: tokio::runtime::task::harness::Harness
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
8: tokio::runtime::scheduler::multi_thread::worker::run
9: tokio::loom::std::unsafe_cell::UnsafeCell
10: std::panicking::try
11: tokio::runtime::task::harness::Harness
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<F,A as core::ops::function::FnOnce
at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library/alloc/src/boxed.rs:1973:9
alloc::boxed::Box<F,A as core::ops::function::FnOnce
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-07T22:51:44.209 tokio-runtime-worker(ThreadId(10)) [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
3: std::panicking::try
4: tokio::runtime::task::harness::Harness
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
8: tokio::runtime::scheduler::multi_thread::worker::run
9: tokio::loom::std::unsafe_cell::UnsafeCell
10: std::panicking::try
11: tokio::runtime::task::harness::Harness
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<F,A as core::ops::function::FnOnce
at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library/alloc/src/boxed.rs:1973:9
alloc::boxed::Box<F,A as core::ops::function::FnOnce
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:
INFO 2023-08-07T22:51:44.479 invocation_loop(ThreadId(21)) [1P:op-app/src/app/backend/lock_screen.rs:72] System unlock is enabled: true
INFO 2023-08-07T22:51:44.487 tokio-runtime-worker(ThreadId(10)) [1P:op-app/src/app/backend/lock_screen.rs:88] Sys auth status NotSetup
```
X11 version (via Xwayland) works fine. What should I do to get a wayland-native version running?
1Password Version: 8.10.9
Extension Version: Not Provided
OS Version: Not Provided
Browser: Not Provided
40 Replies
Two years later, we're almost halfway through 2025, Linux platforms are actively dropping X11 support, and 1password still launches as an X11 client even while other Electron applications work fine on modern desktops.
The process of launching the client remains slow and painful:
- Click or press something to launch the client
- Get the far-from-true 1Password quit unexpectedly error window yet again
- Click Report since somewhere there is a pile of reports which represents a fraction of the number of times that our time has been wasted
- Wait for almost 30 seconds on a desktop which can launch Google Chrome with multiple windows and tabs in less than two
- A client window appears
Manually updating the two slightly different `1password.desktop` files installed by 1password to
Exec=env ELECTRON_OZONE_PLATFORM_HINT=auto /opt/1Password/1password %Uevery time the client is updated, while tedious, continues to run it as a Wayland client and the current version, 8.10.78, appears to run fine with the wobbly juddery effect when moving the window which affected some earlier versions no longer present.
For anyone else running into this problem, you are probably running into the chicken-egg situation of "not being able to open the 1Password window to set 'Hardware Acceleration' to 'on'..":
You can go to `~/.config/1Password/settings/` edit `settings.json` and paste `"app.useHardwareAcceleration": true,` as a new line on the third line.
This solution is from this Reddit comment, which I am adding here in the hope backlinking will help search engines make the fix more discoverable.
1P_Mitch
Has there been any progress on this? 1Password could detect if it is using a Wayland Socket and force `Hardware Acceleration` to `on` by default.
I will also chime in that its a bit ridiculous that the clipboard problems are known for more than a year by now, and there is still what seems to be little progress. Linux customers are still paying customers, you can't eternally shove them to the bottom of the priority queue.Thanks boekelele ! I'm on a fresh install so I had no `settings.json` file. I had the feeling that if I could get 1password to start, then I could log in, create the settings file, and at least get some usage out of it, but the hardware acceleration was missing.
For anybody else needing a first-time login on 1password on sway, you can create ~/.config/1Password/settings/settings.json with only this content:
{ "app.useHardwareAcceleration": true }and then start 1Password with `ELECTRON_OZONE_PLATFORM_HINT=auto 1password`.
Same problem here. I installed `swayfx` on Arch. I launched 1password with `ELECTRON_OZONE_PLATFORM_HINT=auto 1password` (otherwise it would complain it cannot find an X server or $DISPLAY). I get a try icon, and I can right-click on it and get the menu. However, no window is ever displayed, even if I click on "settings" or "open 1password". Using the `--toggle` switch on the command line also does not work.
It's still 2025 and 1password still starts as an X11 client.
Setting ELECTRON_OZONE_PLATFORM_HINT=auto still works, at least for me with 1password 8.10.60 in a GNOME on Wayland on an Ubuntu 24.04.1 desktop.
Extra bizzarely, you can the settings window from the tray menu when that broken windowless mode.
@magaretz that behaviour is new, actually. Ozone platform hint used to work fine just a few weeks ago!
So, it is 2025 already. Any updates on the support for 1Password?
Installing from either Flatpak, beta version or mainline for Debian resolves in that I can start the process, like
ELECTRON_OZONE_PLATFORM_HINT=auto 1passwordand I can see the tray icon, but I cannot open the main window.My yearly subscription will renew soon. The reason I pay for a password manager at all is because the most important thing about a pwm is that it must integrate with a lot of different software. Browser, clipboard... 1Password even integrates with SSH and many CLI tools, which is fantastic. That integration takes continuous effort, so the paid subscription model makes sense to me.
That being said, I am completely baffled that Wayland is not supported yet. (And please don't claim a paid pwm supports Wayland while clipboard doesn't work.) Wayland has been the default on all major Linux distributions for years now. A lot of 1Password's features target developers which heavily use Linux (comparable to Windows by most estimates). So by not supporting Wayland, it seems to me 1Password is delivering a sub-standard experience to a large chunk of its core audience. I don't mind janky XWayland apps when they're open source, but paying for one? It doesn't feel right at this point in time.
I'd love to know if I'll be getting my money's worth in the coming year. Maybe someone from 1Password would like to share more details about what's blocking the wayland clipboard support? Remember, a lot of your customers are devs, don't spare the technical details. What's wrong with shelling out to https://github.com/bugaevc/wl-clipboard? It even has a
--paste-onceflag, which seems like its purpose-built for passwords.Got 1password working on wayland with the ELECTRON_OZONE_PLATFORM_HINT environment variable just fine. But another caveat I'd like to add to the list is the "Show in Large Type" feature does not work.
