Forum Discussion

ftpd's avatar
ftpd
Occasional Contributor
3 years ago

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:4...
linux
boekelele's avatar
boekelele
New Contributor
5 months ago

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.

spak's avatar
spak
New Contributor
5 months ago

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`.