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

FrankyO1P Thank you for your response, though it is a disappointing one.

How exactly is one supposed to learn that 1Password does not support Wayland?

Before we signed up for our paid business account, we checked the requirements documentation on https://support.1password.com/system-requirements/#system-requirements-for-the-1password-apps. There is no mention of either Wayland or X.org / X11 / X on that page.

We created a trial account and downloaded the app. It worked perfectly fine under Wayland.

We later read through further documentation and found https://support.1password.com/keyboard-shortcuts/ in your official knowledge base which specifically mentions Wayland: “If you’re using Linux with the X11 or Wayland protocols, you can customize global keyboard shortcuts for 1Password.”

If it quacks like a duck, and it walks like a duck …

Then a patch version update completely breaks the app, and suddenly we are informed that Wayland is not supported. Are we supposed to conclude that it never was supported? That it only ever worked by accident? That any mention of Wayland in the knowledge base is a typo? And that by pure accident no one ever deemed it necessary to document the fact that one can not use 1Password under Wayland?

Without a specific notice that Wayland was not supported, I certainly wouldn't have anticipated this being the case. Wayland has been the default on Ubuntu since 21.04 (released 2½ years ago!), on Debian since 10 Buster (released 4 years ago!!), Fedora since 34 (released 2½ years ago!), and openSUSE since Leap 15.0 (released more than 5 years ago!!!). Respectfully, what does Linux support even mean, if it lags that much behind and if the app doesn't run on any of the current major distros without workarounds (such as Xwayland—if that even fully works)?

Besides, this is a security product after all. Thinking about its overall mission, 1Password should actively discourage customers from using X and point them towards Wayland instead. The former's architectural flaws are well known, the many high severity CVEs are but a quick search away, and its ever slowing release cadence / its increasingly anaemic release notes speak for themselves.

I realize that this is a rather harsh message. I am glad that you are participating in this discussion, FrankyO1P, and I certainly do not blame you personally for any of this. From an engineering perspective, I simply cannot understand the decision to disregard Wayland. I can understand still wanting to support X for backwards compatibility, but why on earth would one do so at the cost of supporting Wayland. And from a business perspective, I find it, frankly, rather fraudulent-ish to cloak the issue of Wayland incompatibility in silence in seemingly all public-facing materials, produce an application that initially works, and then silently take that “feature” away in a future patch-version update.

To your point about using the browser extension in standalone mode: My understanding is that this will support neither the CLI nor running an SSH agent. It is thus not a replacement.

What are we left to do? Migrate to a different vendor? Will we get refunds for any prepaid time on 1Password? What about other users in our family accounts who are running a different OS and are thus not affected? Can they transition to free 1Password accounts to continue using it?