Linux desktop client crashes on startup

For me to make it a bit workable, I disconnected the (Firefox) 1Password plugin from the desktop app in the plugin settings. Now it doesn't crash when using it in the browser (my (almost) only usecase ). But yeah, not a real solution ofcourse. 

Created an account to reply to this - Marking this as resolved is HIGHLY misleading as this has been a year in the works and is NOT resolved. I have tried all of the different versions of Linux, tried Snap, .deb, and any other package types I could find, tried settings changes, and there has been and is STILL NO FIX. 

I have been very happy with 1Password, but over the last year a LOT of my devices and my computers have moved to linux and the amount of time this issue wastes is ridiculous. It can take anywhere from 1-5 minutes after launching to actually have the 1Password program launch and function after a reboot. I work in IT, I understand that's not all that much time for a one time thing. But EVERY TIME I reboot? That can easily take a "quick fix" to a well I guess I will do this later" if I am in a hurry. 

WHEN is a fix coming?? Is there any news other than "oh we're working on it!" 

You wrote in February, we should watch the release log for a fix. But nothing happend since then.

1Password is still crashing every morning on Ubuntu 25 with version 8.10.78

Any plans of solving this problem?

Here’s what fixed the “crash/slow first launch, then fine after” issue for me on Ubuntu Asahi (ARM64). Maybe it helps others hitting the same thing.

First launch after a reboot hangs ~30s or “crashes,” then later launches are instant.

Logs show lines like:

GLib-GObject … has no handler with id …
sending crash reports (then a long pause)

After it finally starts, DB integrity checks succeed and the app is snappy until next reboot.

The crash reporter was blocking startup on the first run after boot. Disabling it removed the delay.

Quick test (no install changes)

Run 1Password once like this:

/opt/1Password/1password --disable-crash-reports

1Password doesn’t provide a Flatpak build for ARM64, and I haven’t seen this issue on my other machine running AMD64.

Usually wouldn't pile on a thread with plenty of information just to +1, but considering this has been an issue for so long, thinking it might help raise the pressure a bit 🙂

On Kubuntu 25.04 this happens after every restart - first a crash, then it opens. Sometimes though, seemingly especially after 1Password being updated, it refuses to start entirely until I run `sudo pkill 1password` and open it again.

It's really annoying and after experiencing this for over a year now personally I'm seriously close to looking for alternatives... which is a real shame considering how happy I am with 1PW otherwise...

Come on guys! Why is this not fixed!! I have this every day, every time I start my Ubuntu 25.04 and use Firefox and 1Password or 1Password directly. 

Every time I report this, and more then a year(?!) this is not fixed. Am I paying for something or not?

Any news here regarding that topic? :(

Could this be related to also using the 1Password extension with Chromium/Firefox in snap/flathub?

I uninstalled my snap versions and installed the normal Chrome .deb from the website. I don't have the error now, but it could be a coincidence.

1P_Dave 

Why did you solve this issue?

You are saying it is not fixed and it is in backlog. This is still happening on our business account and it is quite annoying. uggg. 

Please keep it open until it is fixed. Marking it as solved gives the false pretense that it was fixed but it is not. 

I had this same issue on Kubuntu 24.04.2 LTS.  Sometimes it wouldn't start.  Many times it would crash whenever I clicked on the edit button for an entry.  I would usually find many instances of 1password processes running in the background without a GUI.  In those situations, attempting to start the app from the launcher would result in another process but no GUI.  Even killing all of the running processes wouldn't necessarily help.  HOWEVER, I did notice that any time I started the app from a terminal (e.g. /usr/bin/1password) the result was a 1Password window that opened immediately.  I didn't experience any issues until I backgrounded the app (using 'bg' and 'disown' commands after CTRL-z) and closed the terminal.  From what I was experiencing, I think closing the terminal was the issue.  The last thing I tried was changing the launcher command to redirect STDIN and STDOUT to /dev/null.  This seems to have the same effect as running from a terminal command line in stabilizing the app.  To do this, I change the launch command to this:

/bin/bash -c '/opt/1Password/1password > /dev/null < /dev/null'

For the launcher, you have to split this into the command (bash) and its options:

Anyway, maybe it will help.  I've only been testing this for a few hours, but I haven't had any crashes since.

Btw, I'm using Wayland for my desktop with NVidia drivers.  1Password was installed using apt with 1password's package repo.