Linux desktop client crashes on startup

This update fixed nothing for me.

Hi, no the problem remains with Version 8.12.2 at least when running on Ubuntu 22 and 24. The pattern hasn't changed, sometimes you can get a run of several days without the problem then it just comes back again.

I can't re-itterate any more strongly that the developers need to resolve this problem rather than users have to work around it.  There is nothing more annoying then getting to a critical transaction requiring a password like on booking.com and then find youself staring at a crash log which when you dismiss takes over 30 seconds for the 1password login to appear.

Because it is such a disruptive bug some users may want to do this.

If you are a standard user and don't care about crash logs at all then you can get around the problem by removing them as the system starts up. Obviously sometimes the crashlogs are important but ones generated during the normal running of 1password won't get deleted unless you log out and log in again.


create a script file as below to do the delete. give it a name such as
/home/yourloginname/deletecrashlogs.sh

(Replace yourloginname with your actual username.)

#!/bin/bash
rm -rf /home/yourloginname/.config/1Password/crashes/*

(Replace yourloginname with your actual username.)

Then schedule the script to run as a user service that runs on startup.

create a user service file called 

/home/yourloginname/.config/systemd/user/cleanup-1password-on-startup.service
(Replace yourloginname with your actual username.)

[Unit]
Description=Cleanup 1Password crash files when graphical session starts
PartOf=graphical-session.target

[Service]
Type=oneshot
ExecStart=/usr/bin/bash /home/yourloginname/deletecrashlogs.sh
RemainAfterExit=no

[Install]
WantedBy=graphical-session.target

(Replace yourloginname with your actual username.)

run 
systemctl --user daemon-reload

then 
run

systemctl --user enable cleanup-1password-on-startup.service

to test
systemctl --user start cleanup-1password-on-startup.service

if you want to disable this at any time from working when you log in then do this.

systemctl --user disable cleanup-1password-on-startup.service

Sounds good. Maybe 1P_Dave​ can give an official statement if the bug should be fixed or not?