Forum Discussion

edtpg's avatar
edtpg
New Contributor
12 months ago
Solved

Linux desktop client crashes on startup

Since updating to the latest version of the client, the Linux desktop client consistently crashes on first startup, and sometimes crashes again after already running. I have the browser extension ...
linux
  • 1P_Dave's avatar
    1P_Dave
    8 months ago

    Hello folks, 

    I'm sorry that 1Password for Linux is crashing when you first first boot your device. This is a known issue that our development team is investigating and hopes to fix in a future update to 1Password. While I don't have a timeline on when a fix will be released, the fix will be noted in our release notes as soon as it is available. 

    As noted in this thread, the issue should only affect the first launch after boot and subsequent launches of the 1Password app should work normally. If you're seeing different behaviour then please reach out to support@1Password.com so that we can dig deeper.

    -Dave

1P_Dave's avatar
1P_Dave
Icon for Moderator rankModerator
3 days ago

pwhz​ and yjcb2​ 

I’m really sorry for the continued impact this issue is having. I know it’s not ideal, and I truly appreciate your patience while our development team continues to investigate.

When you have a moment, could you please try the following and let me know what happens?

  1. After booting your Linux device, wait about 10–20 seconds before manually launching 1Password for Linux. Does 1Password still crash?
  2. Try turning off “Keep 1Password in the system tray” under 1Password > Settings > General.


Do either of these workarounds make a difference? Your results will help our developers better understand what’s causing the issue and work toward a fix.

-Dave

pwhz's avatar
pwhz
New Member
3 days ago

Neither makes a difference.

I did some more experimenting and I discovered I can make 1Password crash at will, without needing to reboot. It appears to be the same crash as happens at boot.

  1. Get 1Password to start without crashing. (No mean feat, but that's why we're here.)
  2. Let 1Password reach the password screen. This specific screen probably doesn't matter, but it's an indication that the program has started properly.
  3. In a terminal, run either killall -SIGTERM 1password or killall -SIGKILL 1password.
  4. Wait for all of 1Password's processes to exit.
  5. Launch 1Password again.


(*) A slight variation is to let 1Password crash and then start from step (3), which kills the zombie processes.

I found three behaviours in 21 attempts at this:

  • Every (5) after SIGTERM in (3) resulted in a complete crash on startup. This totalled 10 crashes. I think about three of these were (*). Basically, it doesn't matter whether 1Password crashes or not; a SIGTERM used either to kill the whole thing or just the zombie processes after a crash will always be followed by a crash on the next launch.
  • Excluding (*), every (5) after SIGKILL in (3) was a proper startup, with no crash. This totalled 7 normal starts. So if 1Password does not crash and I kill the whole thing with SIGKILL, then it won't crash on the next launch.
  • For (*) with SIGKILL, one (5) was a crash, and on three occasions I got the crash popup followed by a normal start when I dismissed the popup.


It's a bit weird and I don't think I've explained it very well, but maybe it'll be useful in some way. I can clarify if needed.

> uname -a
Linux lnx-p15s 6.12.48-1-MANJARO #1 SMP PREEMPT_DYNAMIC Fri, 19 Sep 2025 16:11:04 +0000 x86_64 GNU/Linux