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 ...
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
Moderator
ModeratorHello 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.
1P_Dave I'm not sure if it happened automatically or manually, but marking as a solution immediately after the issue reporter unmarked it is nothing short of gross.
- 1P_Dave
I understand your perspective and agree that the "Solution" label isn't the best. The third-party community platform that we're using doesn't currently allow us to change the "Solution" label but it's something that we've requested as a feature with our third-party vendor. Hopefully we get the ability to change the label in the future, I would personally prefer something like "Answer" instead.
For the time being, please avoid unmarking solutions set by the team since it's the only way that we have to pin the current status about an issue to the top of a thread to make sure that everyone sees it when they open the thread.
-Dave
- 1P_Dave
Marking a post as a solution to a thread is a way to highlight the most up-to-date answer to a thread so that folks don't have to look through dozens or hundreds of replies to find the current state of an issue. It doesn't mean that the issue itself is solved or closed.
To clarify: are you no longer seeing a crash when launching 1Password after starting your Linux device? Let me know.
-Dave
Dear 1P_Dave,
We already had this conversation months ago. What edtpg is describing is totally correct.
- Marking this as solved is "incorrect" and "misleading". Yet, you decided not to change this behavior just because you did not want to.
- Multiple users have already reported you that this is incorrect as you can see in this conversation. Yet, you do not want to change it because it is your will to keep it like that
- This is still happening, and it has not been fixed. We are getting close to 1 year with the issue and no solution. Yet, you keep having this as "solved"
