Forum Discussion
Suddenly unable to use op run
I've use op run heavily for a couple of years now. All of a sudden, in the past few hours, it's stopped working. I get
error initializing client: authorization prompt dismissedYes, my main 1password desktop is open & unlocked. Yes, I've checked my network. All other activity is working fine (including my posting this from the same device).
In general, there seems to be a wave of 1password flakiness and bugginess I've noticed in the past 24 hours. I've also just since last night had the same problem with it's asking for my main password over and over again, as reported in this thread:
Password queried multiple times per day | 1Password Community
That I can live with, however. Losing op run is a much bigger deal.
I'm on Mac M1. Sequoia 15.4.1 . 1Password for Mac 8.10.75 (81075001).
2 Replies
I also can't use the git commit signing that has always worked to date
> git commit -m abc error: 1Password: failed to fill whole buffer fatal: failed to write commit objectI could use the -c commit.gpgsign=false flag to work around this, but our repo requires signed commits.
Bit the bullet and rebooted this morning. That fixed it. Probably my UNIX heritage, but I HATE being compelled to reboot for an app-level bug.
