Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
koom
2 years agoNew Contributor
1password quit unexpectedly
Hello,
For the last month or so I've had the problem that when I try to start 1password I get a message that says "1password quick unexpectedly" immediately after trying to launch the app. If I try to launch the app again, it will sometimes work (and I try to then not close it because I have no idea when it will fail again).
How could I begin to learn what is going or fix this?
I tried launching from the command line and the output is in the image. I do get a GUI popup with the aforementioned message. I'm using Manjaro Linux with a KDE desktop environment.
Glad to upload a log file containing the same content, but this form seems to only alllow me to upload images.
1Password Version: 8.10.24-44
Extension Version: Not Provided
OS Version: 6.1.71-1-MANJARO
Browser: Not Provided
2 Replies
- FrankyO1P
1Password Team
Thanks for bringing this to our attention. There are other users reporting a similar issue and I would love to investigate into this issue further.
If you have not already, could you send an email to
support+linux@1Password.com?With your email please include:
- A link to this thread: https://1password.community/discussion/144180/1password-quit-unexpectedly
- Your forum username:
koomorShamshiel - A diagnostics report: https://support.1password.com/diagnostics/?linux
- Information about your current environment (Linux distribution, version, desktop environment)
We'll look forward to hearing from you.
Franky
- ShamshielNew Contributor
I have the exact same problem. Since one or two weeks ago after I did a system update of my arch based system (EndeavourOS) I get an error pop up when I launch 1Password:
1Password quit unexpectedly
Click Report to send more information to the 1Password team.When I click "Send Later" and wait for 10-30 seconds 1Password will still start.
Running 1Password via the CLI results in the exact same output as in your screenshot with the same error message.
Did you ever figure out what was wrong?