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

I've done further testing on an Intel laptop and are having the same issues so doubt it hardware related.

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

1. It's possible that is related to the GPU as I have the same one as ftpd.
2. I have it installed it via the official apt repository.

I start qtile with dbus-run-session already, but I've tried also explicitly add it to my flatpak 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?

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.

1P_Mitch, what do you have set as XDG_CURRENT_DESKTOP? Maybe here the problem lies, as I'm setting it manually in my qtile config.

1. glibc, it is x86_64.
2. 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.
3. I've tried, still the same result.
4. 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 by dbus). 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.

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 and dbus services and export the output of dbus-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:

1. Are you using the glibc or musl version of Void? I assume this is x86_64.
2. What GPU? Could you try launching with --disable-gpu?
3. 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.)
4. 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.

Well, it doesn't work for me:

```
~ ❯ env | grep -i electron
ELECTRON_OZONE_PLATFORM_HINT=auto
~ ❯ flatpak run com.onepassword.OnePassword
INFO 2024-04-30T23:38:20.659 ThreadId(15) [client:typescript] Client starting.
INFO 2024-04-30T23:38:20.660 ThreadId(15) [1P:ffi/op-core-node/src/lib.rs:982] detected an external seccomp filter
WARN 2024-04-30T23:38:21.596 ThreadId(15) [1P:op-crash-reporting/src/killswitch.rs:58] Failed to check Sentry enabled status, Sentry is disabled. Reason: IoError(IoError(error sending request for url (): operation timed out))
INFO 2024-04-30T23:38:21.597 ThreadId(15) [1P:op-localization/src/lib.rs:232] system locale detected as 'en-US'
INFO 2024-04-30T23:38:21.597 ThreadId(15) [1P:op-localization/src/lib.rs:258] selected translations for EN_US based on detected locale en-US
INFO 2024-04-30T23:38:21.597 ThreadId(15) [status:app/op-app/src/app.rs:568] App::new(1Password for Linux/81030032 (EN_US), /$USER/.var/app/com.onepassword.OnePassword/config/1Password)
INFO 2024-04-30T23:38:21.606 ThreadId(15) [1P:data/op-db/src/common/mod.rs:120] Core DB Table Integrity Check Succeeded
INFO 2024-04-30T23:38:21.608 ThreadId(15) [1P:data/op-db/src/common/mod.rs:134] Core DB Integrity Check Succeeded
INFO 2024-04-30T23:38:21.608 ThreadId(15) [1P:data/op-db/src/core_db/db.rs:164] Starting Core DB at version: 31
INFO 2024-04-30T23:38:21.610 ThreadId(15) [1P:data/op-db/src/common/mod.rs:120] Resources DB Table Integrity Check Succeeded
INFO 2024-04-30T23:38:21.610 ThreadId(15) [1P:data/op-db/src/common/mod.rs:134] Resources DB Integrity Check Succeeded
INFO 2024-04-30T23:38:21.611 ThreadId(15) [1P:data/op-db/src/resources_db/db.rs:133] Starting Resources DB at version: 1
INFO 2024-04-30T23:38:21.705 ThreadId(15) [1P:ssh/op-ssh-config/src/lib.rs:325] agent not configured
ERROR 2024-04-30T23:38:21.709 ThreadId(15) [1P:app/op-app/src/app/backend/native_messaging/mod.rs:73] BrowserSupport manifest installer failed: InvalidAppPath
WARN 2024-04-30T23:38:21.721 ThreadId(15) [1P:native-messaging/op-native-core-integration/src/lib.rs:167] detected 1Password was in an incompatible sandbox, disabling native messaging.
INFO 2024-04-30T23:38:21.723 tokio-runtime-worker(ThreadId(5)) [1P:ssh/op-agent-controller/src/lib.rs:502] Starting filesystem watcher for SSH agent configuration directories...
ERROR 2024-04-30T23:38:21.723 tokio-runtime-worker(ThreadId(5)) [1P:/builds/dev/core/core/ssh/op-agent-controller/src/lib.rs:503] Io(Os { code: 2, kind: NotFound, message: "No such file or directory" })
ERROR 2024-04-30T23:38:21.768 tokio-runtime-worker(ThreadId(5)) [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

ERROR 2024-04-30T23:38:21.768 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

INFO 2024-04-30T23:38:22.200 tokio-runtime-worker(ThreadId(10)) [1P:app/op-app/src/app/backend/lock_screen.rs:89] System unlock is enabled: false
INFO 2024-04-30T23:38:22.200 tokio-runtime-worker(ThreadId(10)) [1P:app/op-app/src/app/backend/lock_screen.rs:117] Sys auth status Disabled
```

And nothing happens - 1Password window doesn't appear.

Version:


1Password for Linux 8.10.30
81030032, on PRODUCTION channel


installed via Flatpak, from the official 1Password repository. Void Linux with kernel 6.8.8, qtile 0.25. All other Electron apps work great natively on Wayland.

Hey all. It's been several months since we last revisited this topic. As things are rapidly changing in the Linux world, I wanted to check in and provide some notes and guidance about running 1Password in native Wayland mode.

Running 1Password on Wayland

I did a fresh install with:

• Ubuntu 24.04 LTS
• GNOME on Wayland (default in Ubuntu 24.04)
• The latest stable version of 1Password (8.10.30, installed via the official apt repository)

I was then able to launch 1Password in native Wayland mode using ELECTRON_OZONE_PLATFORM_HINT=auto 1password.

I confirmed that 1Password was indeed running in Wayland mode by launching xeyes and running my cursor over the app — the eyes did not follow. 👀

Caveats and things to keep in mind

The ELECTRON_OZONE_PLATFORM_HINT env variable is a newer and better way of configuring the app than the Ozone command-line flags which you may have seen or tried before. If you set it globally, it will affect all apps using recent versions of Electron, including when launched from the GUI (e.g. by adding export ELECTRON_OZONE_PLATFORM_HINT=auto to ~/.bashrc).

Typical 1Password functionality including sign-in, the tray icon, browser integration, SSH agent, and item browsing and editing worked well for me in Wayland mode.

There are still some gotchas:

• 1Password currently depends on XWayland for secure clipboard access, even in Wayland mode. You do not need to log in to an X11 session, simply have it installed. We would like to migrate to a fully-native clipboard implementation for Wayland but we will need to build one that meets our security requirements for putting passwords on the clipboard.
• Global keyboard shortcuts do not work out of the box. (You will see an error about keyboard shortcuts on launch but this can be ignored.) You can however create your own keyboard shortcut launchers in GNOME/KDE/your WM of choice to simulate the built-in ones, e.g. 1password --quick-access to open Quick Access and 1password --lock to lock.
• The QR code scanner does not work in native Wayland mode.
• The Snap package will not launch in native Wayland mode.

Now every distribution/WM/configuration is different, and Wayland support is still in flux, so my experience may not be the same as yours. Please make sure to update your OS/GPU drivers and 1Password, and share in the thread if you run into difficulties. I'll do my best to help out and/or flag issues to the team.

-Mitch

FrankyO1P I'm still stuck with the vulnerable version v8.10.8, just like I was when this thread was created. I don't understand why you would think that this is an acceptable situation, or why you would seriously suggest that I migrate my entire system to X11, a dated and insecure environment, instead of having your developers fix the regression that they introduced nine months ago.

I think that we, your paying customers, have demonstrated a lot of patience, given the severity. But now nine months have passed without a fix on the horizon. I respectfully request that you please ask the development team for an approximate timeline for when they plan to fix that regression, and then get back to us with a response. Would you be willing to do that for us please?