Forum Discussion

edtpg's avatar
edtpg
New Contributor
12 months ago
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 ...
linux
  • 1P_Dave's avatar
    1P_Dave
    8 months ago

    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

Addero's avatar
Addero
New Contributor
19 days ago

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's avatar
1P_Dave
Icon for Moderator rankModerator
7 days ago

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: 


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