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

Thank you for 1Password for linux! But on this year all new distribution want to move from X11 to wayland and drop X11. I don't have problem with Google Chrome, Slack, Discord, Vscode and even IDEA 2024.1 now fully supports wayland and fractional scaling. When do you plan to add full wayland support?

Bumping due the lack of response to the important, urgent, clear and reasonable comments above by Shediv3aiMapiTh9 solarizde and blau after the somewhat disappointing response from FrankyO1P.

I have nothing new to add, except that 1Password is one of, if not the, only client on my several Linux platform desktops which requires Xwayland, i.e. to work in compatibility mode with a protocol which has reached the end of its very long life.

I look forward to 1Password running by default as a client of modern Linux desktop platforms, i.e. using Wayland, with X11 support being a bonus feature for backwards compatibility.

That being said, currently 1Password for Linux does not support Wayland.

that surely is very disappointing especially keeping in mind that Linux is moving more and more towards Wayland. Considering this is a regression bug, makes it even worse. I would also appreciated a more straight forward communication as I see no need for whitewashing. To me it very much seems like you guys broke the functionality and don't care enough about a few users to fix it.

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?

Thank you everyone for your feedback.

I know that support for Wayland is something that some folks find necessary and I've let the team know that you're still eager to see support be introduced in a future version of 1Password for Linux.

That being said, currently 1Password for Linux does not support Wayland. While older versions might have run in some capacity using Wayland, I don't recommend using those older versions since they're missing several important bug fixes and security updates. We always recommend using the latest version of 1Password: https://releases.1password.com/linux/

If you're unable to run the latest version of the 1Password for Linux on your device, then as a workaround, I would recommend sticking with 1Password in the browser (extension) in stand alone mode for now rather than running an older version of the desktop app:

Get to know 1Password in your browser

Franky

FrankyO1P When re-assessing priority, please keep in mind that leaving us stuck at v8.10.7 (or v8.10.8) means we’re also left affected by the webp vulnerability.

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.

Thanks for the +1 Claudi 👍

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.

Hi @afkmario,

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

Franky