Skip to content

Run 1Password with software GL where there is no render GPU - #14717

Draft
maralcbr wants to merge 1 commit into
omabot/pr-13362from
1password-software-gl
Draft

maralcbr wants to merge 1 commit into
omabot/pr-13362from
1password-software-gl

Conversation

@maralcbr

@maralcbr maralcbr commented Oct 9, 2026

Copy link
Copy Markdown
Member

Electron draws a blank window when the machine has no DRM render node: a VM, a headless or passthrough GPU, or a GPU whose driver isn't up yet, such as Apple M3 and later on Linux today. This was part of #14431 and is moved out here because only those machines need it.

omarchy-hw-render-gpu tells whether a renderD node exists, and omarchy-cmd-electron-gl-args prints --ozone-platform=wayland --disable-gpu only when it doesn't. omarchy-cmd-electron-gl-wrap installs a marked PATH wrapper in /usr/local/bin that execs the real binary with those flags, so it follows the machine rather than the moment it was installed. It refuses to replace a launcher it didn't write or to wrap a binary over itself, and stages the write so a failure leaves the old launcher in place. omarchy-cmd-desktop-exec-repair points the user's desktop entry at the wrapper by replacing only the executable token, with a backup.

The 1Password installer uses them only when the machine has no render node. With one, which is every x86 machine with a working GPU, nothing changes.

Stacked on #14431.

Electron draws a blank window when the machine has no DRM render node: a VM,
a headless or passthrough GPU, or a GPU whose driver isn't up yet (Apple M3
and later on Linux today). omarchy-hw-render-gpu tells whether a renderD node
exists, and omarchy-cmd-electron-gl-args prints --ozone-platform=wayland
--disable-gpu only when it doesn't.

omarchy-cmd-electron-gl-wrap installs a marked PATH wrapper in /usr/local/bin
that execs the real binary with those flags, so it follows the machine rather
than the moment it was installed. It refuses to replace a launcher it didn't
write, or to wrap a binary over itself, and stages the write so a failure
leaves the old launcher in place. omarchy-cmd-desktop-exec-repair points the
user's desktop entry at the wrapper by replacing only the executable token,
keeping arguments, other actions and customizations, with a backup.

The 1Password installer uses them when the machine has no render node. With
one, which is every x86 machine with a working GPU, nothing changes.

Co-authored-by: Scott Jones <444693+scottjones@users.noreply.github.com>
@jandrusk

Copy link
Copy Markdown

Heads-up: the base branch here is omabot/pr-13362, and #13362 has been closed. The description says this is stacked on #14431, so it probably needs retargeting, either onto #14431's branch or onto quattro once that lands. Otherwise the diff GitHub shows won't match what would actually merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants