Linux desktop client crashes on startup

I can also say that this problem appears to have been fixed in the last few days, after the upgrade from 1password 8.12.0 to 8.12.2.

I am running on Arch Linux with 1password installed from the AUR.

I was experiencing this crash report on startup reliably - probably 90% of the time. However, in my reboots over the last few days it is no longer occurring.

I believe this is likely the upgrade that fixed it:

https://aur.archlinux.org/cgit/aur.git/commit/?h=1password&id=4e812cfd70e28eb66e65c070ec76d9df9fd2df09

Thanks to the 1password devs for whatever they did to fix it... although it doesn't seem to be mentioned at all in the release notes here:

https://releases.1password.com/linux/stable/

1password 8.12.8 on Ubuntu 24.04.4, which was where the reproducible crashes recently stopped.

To give it credit, this time was unexpected.

I just updated to 8.12.10, so will test initial launch soon.

I think I've found the mechanism behind this on my machine, plus a workaround that stops the crash itself rather than hiding the popup.

I'm on 1Password 8.12.42, Kubuntu, Plasma 6 on Wayland. At logout the journal shows systemd stopping the 1Password autostart unit, 1Password starting its own orderly shutdown, and then:

GPU process launch failed: error_code=1002
FATAL:gpu_data_manager_impl_private.cc:418] GPU process isn't usable. Goodbye.

That's followed by a SIGTRAP in coredumpctl, which is the crash the popup reports on the next start. The autostart unit runs with systemd's default KillMode=control-group, so SIGTERM reaches every process in the cgroup at once. The GPU and zygote children die while the main process is still shutting down, it tries to relaunch the GPU process, fails, and aborts. I tried --disable-gpu first and it made no difference, since Chromium still launches a GPU process.

The workaround is to have systemd signal only the main process, so 1Password can close its own children:

mkdir -p ~/.config/systemd/user/app-com.onepassword.OnePassword@autostart.service.d
printf '[Service]\nKillMode=mixed\n' > ~/.config/systemd/user/app-com.onepassword.OnePassword@autostart.service.d/killmode.conf
systemctl --user daemon-reload

This only covers the copy started by "Start at login", on desktops that run autostart entries as systemd units (Plasma 6 does). A copy you start from the app menu runs outside that unit and still crashes. Since I made the change, 1Password has exited cleanly at logout with no new coredump.

For the 1Password team, the proper fix is presumably to handle SIGTERM by quitting before the children are gone, or to stop counting child deaths during session teardown as a GPU failure. Electron recently backported Chromium's fix for the Windows version of this same crash (electron/electron#52843).