Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
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 ...
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
Please can we bring this back on topic 🥺: on Linux, 1Password leaves stale files in ~/.config/1Password/crashes/ during a normal shutdown or reboot. On the next start, 1Password misinterprets these as a previous crash, logs a false crash, and delays startup. Clearing that directory (rm -rf ~/.config/1Password/crashes/*) before launching resolves the problem immediately. The discussion should focus on why crash artifacts persist across clean shutdowns and why they’re treated as real crashes on startup.
It shouldn't be crashing at all. The crash logs are produced because 1Password is incapable of handling the SIGTERM that it receives when the system is shutting down. The whole point of SIGTERM (as opposed to, say, SIGKILL) is to tell a process to perform a clean shutdown, but 1Password does something weird while trying to handle it and crashes, so the shutdown is not clean. (Or it at least thinks it crashes, maybe because it doesn't understand that SIGTERM is just a shutdown signal.) It would make sense for the crash logs to persist after that, because normally you might want to know that a program exited improperly the last time it was running. The popup is not because of a misinterpretation – it is actually reporting a real crash.
I have said this before in this discussion, and I will say it again: the solution is for 1Password to handle SIGTERM as though the user had asked it to quit via the GUI. That way, when the user asks the system to shut down and 1Password receives SIGTERM, it will exit gracefully, rather than crashing. No crash means no crash logs, so there's no crash reporting popup when 1Password next starts up. For some reason, nobody at 1PW has bothered to do this. There's a secondary bug, which is the delay that 1Password has for some reason before reporting the crash it found logs for, but that's less important. The most direct fix for the problems discussed here is to just handle the signal properly.
I don't know of any other piece of software (and certainly nothing commercial) that actually manages to crash when it receives SIGTERM.
