Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
Forum Discussion
ftpd
3 years agoOccasional Contributor
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
- tobylitNew Contributor
Just as a heads up to everyone, you can run 1Password in Wayland by enabling "Use Hardware Acceleration" in Settings>Advanced with the
ELECTRON_OZONE_PLATFORM_HINT=auto
set but copying passing from the app does not currently work. - FrankyO1P
1Password Team
Thanks for bringing this to our attention. With a few users reporting a similar issue, I would love to investigate into this issue further.
Could you send an email to
support+linux@1Password.com
?With your email please include:
- A link to this thread: https://1password.community/discussion/141663/i-cant-start-wayland-native-version-of-1password
- Your forum username:
ftpd
ortobylit
- A diagnostics report: https://support.1password.com/diagnostics/?linux
- Information about your current environment (Linux distribution, version, desktop environment)
We'll look forward to hearing from you.
Franky
- nerumoNew Contributor
I'm using 1password on ubuntu 24.04 KDE, installed as deb package, and I'm able to start 1password with wayland. BUT: the copy paste isn't working. This implementation probably needs changing from X11 to wayland
- tobylitNew Contributor
I've done further testing on an Intel laptop and are having the same issues so doubt it hardware related.
- tobylitNew Contributor
1P_Mitch I'm glad to see that there is some work on getting 1Password to work on Wayland. I'm currently trying to run 1Password in Wayland on COSMIC, System76's new Rust based DE but I'm having the same issues as ftpd where the window doesn't show up when running in Wayland with
ELECTRON_OZONE_PLATFORM_HINT=auto
- It's possible that is related to the GPU as I have the same one as ftpd.
- I have it installed it via the official apt repository.
- ftpdOccasional Contributor
I start qtile with
dbus-run-session
already, but I've tried also explicitly add it to myflatpak run
- still nothing. I've created a fresh user, run qtile as this user on the default configuration, installed 1Password (from flatpak too) and also the same problem.My
XDG_*
values are the same as yours. Maybe I'm missing some not-obvious dependency? - 1P_Mitch
Moderator
ftpd: I do not have that variable set.
env | grep XDG
XDG_SEAT=seat0
XDG_SESSION_TYPE=wayland
XDG_SESSION_CLASS=user
XDG_VTNR=1
XDG_SESSION_ID=1
XDG_RUNTIME_DIR=/run/user/1000
XDG_DATA_DIRS=/home/mitch/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share
Could you also try running the app (either Flatpak or tar) with
dbus-run-session?
Failing that I'd try with a fresh user account and home directory. - ftpdOccasional Contributor
- glibc, it is x86_64.
- some generic gpu on my AMD Ryzen 5 4650U, all I can identify is
AMD ATI 06:00.0 Renoir
. Using--disable-gpu
changes nothing. - I've tried, still the same result.
- This is when it starts to get interesting. While using the portable version, I see an icon in system tray. I still can't open the main window - it doesn't show automatically and does not show when I click the systray icon. The weird thing is: I can select 'Settings' from the icon's menu and they work just fine.
Note: I normally don't have
elogind
, but for testing purposes I've installed it and even enabled the service (even if it should be automatically started bydbus
). This changed nothing.
I've also installed all Vulkan-related stuff (as the documentation instructs), but it didn't help either.So, the problem has to be somewhere on my side, since it works for you in Gnome and qtile.
- 1P_Mitch
Moderator
Well you intrigued me ftpd. I had never used Void Linux before. (Interesting distro… no systemd! Thanks for introducing me to it.)
I set up a fresh install of Void in a qemu VM (x86_64, glibc version), and installed qtile plus some dependencies (elogind, flatpak, and polkit) and was able to launch 1Password in Wayland mode. I did have to enable the
elogind
anddbus
services and export the output ofdbus-launch
to get the flatpak to launch.I also got the same console output as you, but those errors did not prevent the window from appearing:
This is on a system without Xorg or even Xwayland installed, so I can confirm that it is possible to run 1Password in Wayland in qtile on Void Linux.
Some more questions to help you troubleshoot:
- Are you using the glibc or musl version of Void? I assume this is x86_64.
- What GPU? Could you try launching with
--disable-gpu
? - Could you try deleting the 1Password app user data in
~/.var/app
? (Make sure you have your Emergency Kit saved so you can sign back in to your account.) - In case there's a problem specific to the flatpak, could you try running 1Password from the portable .tar.gz? https://support.1password.com/install-linux/#other-distributions-or-arm-targz
Let's see if we can get this working as well for you as it did in my VM.