Solved

Linux desktop client crashes on startup

Forum|Forum|1 year ago
November 1, 2024
32 replies
5249 views

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.

Linux

Best answer by 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

Show previous replies

B

borgille

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.

Y

yjcb2

@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.

1P_Dave

1Password Employee

@yjcb2

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

AJCxZ0

I suspect that marking thread replies as a Solution continues to irk even folks who recognise how you are using it. A "simple" fix [i.e. one done by others] would be to change Solution to Answer.

Other technical forums use this terminology in similar circumstances [citation not needed].

A

Anonymous

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

1Password Employee

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

A

Anonymous

Today I had the error again. Sorry, I was wrong :-)

DenalB

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.

P

peterdk

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

1Password Employee

I'm sorry for the continued disruption, I've added your report to the internal work item for the issue.

-Dave

#30639

E

efstajas

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

1Password Employee

@efstajas

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

C

callo90

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.

A

Anonymous

This helped me too, thank you so much!

F

fabianerni

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

1Password Employee

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

A

Addero

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!"

DenalB

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.

E

efstajas

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.

P

peterdk

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

1Password Employee

Thank you for sharing your workaround and I'm sorry for the continued disruption.

-Dave

Show more replies

Sign up

1Password employees: Sign in with SSO

Login to the community

1Password employees: Sign in with SSO

Scanning file for viruses.

This file cannot be downloaded