Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
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
58 Replies
Hi,
Any updates on this? It's still happening in Ubuntu 22.04.
I have extension version 8.10.64.7 in Firefox 136.0.2. And the app version is 8.10.68.
It crashes almost every day on startup and I get a prompt asking me to accept, cancel or report. Does reporting do anything?
- 1P_Dave
Moderator
I'm sorry for the disruption to your workflow. The issue is still open in our development team's backlog.
-Dave
Can you please bump this in priority? This is insanely annoying and present for really long time now. It seems to me that it got even worse over time. It's not tied to the first boot and often silently crashes during the day.
I'm on EndeavourOS. I just used KDE Plasma 6.x for some weeks and didn't have this crash on startup.
Thought, it was resolved. But switched to Gnome 47 and updated to Gnome 48 some days ago. Now I get this crash on nearly every start of the OS. I got a popup where I'm able to ignore this error or send a report. On every crash I send a report and I hope they reach the developers ...
I'm using latest 1Password offered via AUR.
Looking forward to a fix.
Hey Dave,
Sorry for the delay. Just wanted to thank you for your reply and wanted to say, that because of that issue I switched from GNOME back to KDE Plasma. The startup issue disappeared. Now I'm back on GNOME 48 and the issue is still there.
Every time I start up my Linux (EndeavourOS) I got the following error message.
Just emailed support team with my Diagnostics Report attached. My support ticket ID is XWK-47424-352.
Hopefully you are able to narrow down the issue and fix it. Thanks!
- 1P_Dave
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 First, sorry for late reply.
That said, the update from the time you answered skips system auth and goes straight to the default account password unlock screen the first time. Unlike other times when the app is locked, there's also no option to trigger system auth manually (the thumbprint button on 1Password's auth popup).
It seems like this works around the issue by skipping the user preference for system auth on app startup. Is that accurate?
Also, to build on what others like AJCxZ0 have said about "solutions": Acknowledging a known issue isn't anything like actually solving it. Marking a solution as "solved" when a solution has yet to have been implemented can only be interpreted as deceptive.
I'm taking that tag off until we can finish discussing the actual fix.
is anything happening to this ticket? When can we expect an update from 1password?
- 1P_Dave
I'm sorry for the delay in replying. The issue is still open in our development team's backlog and I'll update this thread as soon as I have more news to share.
-Dave
The update is that 1Password couldn't care less about their personal users, especially those on Linux. Enterprise is clearly their future money makers and we are just along for the ride.
Glad they were able to secure a many million dollar deal to sponsor a F1 team...
- 1P_Dave
I'm sorry for the disruption and frustration that the issue is causing, I agree that it's something that needs to be fixed as soon as possible. We have developers assigned to the issue and it's currently waiting in our developer's backlog queue to be investigate further and fixed.
1Password for Linux is very important, it's why we've invested in building and releasing for Linux and release frequent updates to the app. I've made a note to update this thread as soon as I have more news to share. For the time being, you can workaround the issue by re-opening 1Password if it crashes when you first start your device.
-Dave
I have the same issue on a fresh install of Ubuntu 24.10.
I installed it through Terminal in order to run it outside the sandbox.It always crashes on startup and I also have another very annoying issue: when I unlock 1Password I got a system prompt to unlock the system keychain.
This is very frustrating, you really need to pay more attention on Linux versions.
Just wanted to report that this is consistently happening to me as well.
2025-02-05T11:21:05.351665+01:00 trond-x1 systemd[4127]: Started app-gnome-1password-90293.scope - Application launched by gnome-shell. 2025-02-05T11:21:05.533488+01:00 trond-x1 1password.desktop[90293]: INFO 2025-02-05T10:21:05.533+00:00 ThreadId(1) [1P:foundation/op-log/src/lib.rs:664] Removed 3 old log files 2025-02-05T11:21:05.535153+01:00 trond-x1 1password.desktop[90293]: INFO 2025-02-05T10:21:05.535+00:00 ThreadId(1) [1P:op-settings/src/store/json_store.rs:73] Settings file created @ 2024-09-13 18:38:50.848754642 UTC and last modified @ 2024-11-10 11:49:38.375714569 UTC 2025-02-05T11:21:05.536074+01:00 trond-x1 1password.desktop[90293]: INFO 2025-02-05T10:21:05.536+00:00 ThreadId(1) [client:typescript] Client starting. 2025-02-05T11:21:09.277899+01:00 trond-x1 1password.desktop[90293]: [90293:0205/112109.277080:ERROR:browser_main_loop.cc(283)] GLib-GObject: ../../../gobject/gsignal.c:2685: instance '0x1e64000f8090' has no handler with id '1358'If I try starting it again, in syslog I can see:
2025-02-05T11:21:11.713750+01:00 trond-x1 systemd[4127]: Started app-gnome-1password-90449.scope - Application launched by gnome-shell. 2025-02-05T11:21:11.891735+01:00 trond-x1 1password.desktop[90449]: INFO 2025-02-05T10:21:11.891+00:00 ThreadId(14) [1P:op-settings/src/store/json_store.rs:73] Settings file created @ 2024-09-13 18:38:50.848754642 UTC and last modified @ 2024-11-10 11:49:38.375714569 UTC 2025-02-05T11:21:11.893193+01:00 trond-x1 1password.desktop[90449]: INFO 2025-02-05T10:21:11.893+00:00 ThreadId(14) [client:typescript] 1Password is already running, closing. 2025-02-05T11:21:11.893522+01:00 trond-x1 1password.desktop[90293]: #033[38;5;196mERROR#033[0m #033[38;5;196m2025-02-05T10:21:11.893+00:00#033[0m runtime-worker(ThreadId(3)) [1P:ffi/op-core-node/src/lib.rs:66] #033[38;5;196mAttempted to notify uninitialized App#033[0mAfter having tried a couple of times (usually 3-4) the app will open. Its terribly annoying.
- 1P_Dave
edtpg and DrewskiMooski
Thank you both for sending in the diagnostics reports! The team will review them and get back to you both as soon as possible via email. Please continue the conversation there.
-Dave
ref: KZI-99494-634
ref: SLI-87415-654 I submitted the diagnostic reports
but did not receive any automated replyand my support ticket ID is SLI-87415-654. I should note that the app will eventually start, but sometimes I have to runkillall 1passworda few times to get it to work.1P_Dave thanks! I submitted the diagnostic reports from the app.
My support ticket is KZI-99494-634.
These last 2 times I tried to make it crash at startup to get the reports, it didn't crash. Instead it temporarily fell back to unlocking with my 1P account password. Does that matter in this case?
- 1P_Dave
Hello edtpg and DrewskiMooski! 👋
I'm sorry that 1Password is crashing on the first attempt on your Linux devices. Our developers are investigating the issue and a work item is open to get this fixed.
If you send in a diagnostics report then the team and I can take a look and confirm that you're running into this known issue:
Sending Diagnostics Reports (Linux
Attach the diagnostics to an email message addressed to
support+forum@1password.com.With your email please include:
- A link to this thread:
https://1password.community/discussion/148868/linux-desktop-client-crashes-on-startup#latest - Your forum username:
username - Do not post the diagnostics report to the forum.
You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks very much!
-Dave
ref: dev/core/core#30639
- A link to this thread:
This also occurs on Manjaro, Arch, Gentoo, and Ubuntu 24.10. Very annoying!
