Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
Forum Discussion
mrinaldhillon
6 months agoNew Contributor
1Password window blank on gnome 47, wayland , fedora 41
1Password for Linux 8.10.68 (81068014) opens correctly but within a minute the app window goes blank. Behaviour is the same with wayland and x11. The issue is not reproducible on previous version 8.10.60.
ELECTRON_OZONE_PLATFORM_HINT=auto 1password --disable-gpu
ELECTRON_OZONE_PLATFORM_HINT=x11 1password --disable-gpu
Error sending from webFrameMain: Error: Render frame was disposed before WebFrameMain could be accessed
at s.send (node:electron/js2c/browser_init:2:93065)
at _.send (node:electron/js2c/browser_init:2:76113)
at te.send (/opt/1Password/resources/app.asar/main.js:1:105968)
at BrowserWindow.<anonymous> (/opt/1Password/resources/app.asar/main.js:1:105382)
This is an Electron bug affecting 16k page size kernels - https://github.com/electron/electron/issues/45560 . It impacts electron apps on Asahi Linux that were built the buggy electron. Until 1Password is released with an updated Electron version, you can either revert to v8.10.60 or append `--js-flags="--nodecommit_pooled_pages"` to Exec line in 1password.desktop file as a workaround.
3 Replies
- mrinaldhillonNew Contributor
This is an Electron bug affecting 16k page size kernels - https://github.com/electron/electron/issues/45560 . It impacts electron apps on Asahi Linux that were built the buggy electron. Until 1Password is released with an updated Electron version, you can either revert to v8.10.60 or append `--js-flags="--nodecommit_pooled_pages"` to Exec line in 1password.desktop file as a workaround.
- LochnairNew Contributor
Same thing here on Fedora Asahi Remix 41, GPU or not doesn't seem to make a difference
- AJCxZ0Bronze Expert
Not yet tested on Fedora, but native packaged 8.10.68 on Ubuntu 24.04.2 with GNOME 46 on Wayland, `ELECTRON_OZONE_PLATFORM_HINT=auto 1password --disable-gpu` or the same with `x11` produces three errors and fails to produce a window. Interrupting the process produces a warning and an error before exit.
Without `--disable-gpu`, it produces three errors, then the main window opens and appears to behave normally as a Wayland client.
Note that this isn't intended to hijack the thread, but to provide a comparable test on a different platform before I try to reproduce the behaviour on the same platform.
PS. Still waiting for that missing markdown support, but using it in anticipation of future correct rendering.