It’s Cybersecurity Awareness Month! Join our interactive training session, or learn about security and AI from 1Password experts.
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 and desktop app integration enabled, and I use my system unlock method as the unlock option for the desktop app (local account password popup instead of biometrics).
This crash happens regardless of triggering unlock via the extension, launching the desktop app directly, or triggering the app's global search shortcut (ctrl-alt-space for me).
This happens on both Kubuntu 24.04.1 LTS and Pop!_OS 22.04 LTS.
In both cases, the desktop app is installed via apt.
Quick edit: I originally wrote this for desktop client version 8.10.48. I updated to version 8.10.50 and the issue does still exist.
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
66 Replies
I find it astonishing that this has not yet been fixed. Clearly it is not an issue of reproducibility because apparently it was reproduced internally four months ago. Is it difficult to fix? Is it low priority because Linux users are expected to be able to deal with unpolished software? Or because Linux users are (presumably) a small proportion of 1Password's (paying!) customer base, and therefore not worth the time?
Please excuse the tone; I bear no ill will towards anyone at 1Password, especially not Dave and the rest of the community team who have the unfortunate job of updating people on this when there are no updates to give. But it's extraordinary that a bug like this has survived several production releases of a commercial piece of software after having been reported a year ago.
- 1P_Dave
Moderator
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?
- After booting your Linux device, wait about 10–20 seconds before manually launching 1Password for Linux. Does 1Password still crash?
- 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
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.
- Get 1Password to start without crashing. (No mean feat, but that's why we're here.)
- Let 1Password reach the password screen. This specific screen probably doesn't matter, but it's an indication that the program has started properly.
- In a terminal, run either killall -SIGTERM 1password or killall -SIGKILL 1password.
- Wait for all of 1Password's processes to exit.
- 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
Your message is the voice for what I am feeling. Thanks a lot for this!
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.
- 1P_Dave
Thank you for sharing your workaround and I'm sorry for the continued disruption.
-Dave
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!"- 1P_Dave
The internal item is still open with the team, and I’ve asked our developers for an update. I’ll keep you posted as soon as there’s news. We appreciate your patience and I completely understand how this is a frustrating issue to encounter whenever you restart your Linux device.
Some folks have reported some workarounds that have helped them avoid the issue although the behaviour doesn't seem entirely consistent when applied to different devices:
- Turning off crash reports for 1Password.
- Turning off "Keep 1Password in the system tray".
I know that these aren't solutions but I wanted to share them in case they help with the current impact to your workflow.-Dave
As a workaround, you could think about switching to KDE Plasma. I did and no such issues anymore.
I know that this isn't a solution, but for me it's working as long there is no fix.
I'm on KDE Plasma (kubuntu latest stable at time of writing), and I experience all the same issues reported in this thread on every startup.
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?
- 1P_Dave
An internal work item is open with the team and I've pinged the development team for an update. I'll update this thread as soon as there's news to share. Thank you for your continued patience.
-Dave
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-reports1Password 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...
- 1P_Dave
I'm sorry that you're also running into the issue, the issue remains open with our development team.
Sometimes though, seemingly especially after 1Password being updated, it refuses to start entirely until I run `sudo pkill 1password` and open it again.
This might be a different issue that I'd like to investigate further. The next time that this happens after an update, I'd like to ask you to create and share a 1Password diagnostics report from your Linux device after you re-open 1Password:
Send a diagnostics report (Linux)
Attach the diagnostics to an email message addressed to support@1password.com
With your email please include:- A link to this thread: https://www.1password.community/discussions/1password/linux-desktop-client-crashes-on-startup/110161/replies/160446
- Your forum username: efstajas
You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks very much!-Dave
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?
- 1P_Dave
I'm sorry for the continued disruption, I've added your report to the internal work item for the issue.
-Dave
#30639
Any news here regarding that topic? :(
- 1P_Blake
Community Manager
While we don't have anything new to share regarding this, there has been some movement on this internally as we've been able to reproduce this with our team.
We'll be sure update everyone here as soon as we have more to share.
- 1P_Dave
Former Member
Thank you for sharing what ended up resolving the issue for you, I've passed your comment along to our development team.
-Dave
#30639
- 1P_Dave
Welcome to the community! Marking a post as a solution to a thread doesn't mean that the issue itself is solved or closed. It's a way to highlight the most up-to-date answer to a thread (letting them know that this is a known issue that our team is investigating) for anyone who stumbles onto the thread in the future.
-Dave
Dear 1P_Dave ,
please note that what you are saying vs what is happening is completely opposite, and it is also decisive:
1. Once you add "Market as solution" the system will show the thread as "solved" refer to the attached image. Even though you are saying it is not solved, the specific word "solved" is added to the thread.2. The color changes to a green. So, having the word solved + the color green with a message saying "marked as solution" makes a new person coming to the thread (like me) think it is fixed, which is not the case.
