1Password refuses to start if there are existing zombie processes

nyuszika7hnyuszika7h
Community Member

If there are existing unkillable zombie processes of 1Password running, it will refuse to start as "already running". This is usually only fixable by a reboot, as zombie processes cannot be killed the normal way, and the parent will be usually init/systemd.

❯ 1password
INFO  2022-09-12T10:29:55.325 ThreadId(10) [client:typescript] 1Password is already running, closing.
❯ pkill -9 1password
❯ 1password
INFO  2022-09-12T10:30:00.194 ThreadId(10) [client:typescript] 1Password is already running, closing.
❯ ps uax | grep '[1]password'
nyuszik+   18333  0.0  0.0      0     0 ?        Zl   Sep02   1:40 [1password] <defunct>
nyuszik+   18336  0.0  0.0      0     0 ?        Z    Sep02   0:00 [1password] <defunct>
nyuszik+   18337  0.0  0.0      0     0 ?        Z    Sep02   0:00 [1password] <defunct>
nyuszik+   18376  0.0  0.0      0     0 ?        Z    Sep02   0:20 [1password] <defunct>

1Password Version: 8.8.0
Extension Version: Not Provided
OS Version: Ubuntu 22.04.1
Browser:_ Not Provided

Comments

  • snova32snova32
    Community Member

    I have also encountered this. In particular, I use a Wayland tiling WM (Hyprland) and have run into this issue with Quick Access. If the Quick Access window loses focus, it disappears, and cannot be opened again; attempting it from terminal results in this same "1Password is already running" message. I'd be really interested in a solution since this issue makes Quick Access completely useless to me.

    For what it's worth I have been able to reset 1Password without a reboot via killall -9 1password instead of pkill, maybe that's useful to you OP.

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Image
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file