Now Clio demanded a fresh login. But she couldn’t log in, because the app wouldn’t stay open long enough to type her credentials.
The next morning, she wrote to Clio support with steps to reproduce: “Lockfile persistence + corrupted saved state = silent failure on launch.” They thanked her. A junior engineer later confirmed it was a race condition in the Electron shell’s ready-to-show event, triggered only when a previous crash left a zombie lockfile.
Priya’s heart rate climbed. The PDF was sitting on her desktop. The report was perfect. But without Clio, she couldn’t invoice. Without an invoice, the client’s payment portal wouldn’t open. Without payment, she couldn’t pay her own software subscriptions due tomorrow. clio desktop app not opening
Then she clicked the Clio icon.
She deleted the lockfile. Then she went to ~/Library/Saved Application State/ and deleted com.clio.desktop.savedState . Corrupted state data from a crash two weeks ago had been poisoning every launch attempt. Now Clio demanded a fresh login
She restarted her MacBook. Waited. Logged in. Clicked the icon. The column bounced three times this time—optimistic, almost—then froze again. No splash screen. No login window. Just a grayed-out icon in Activity Monitor, consuming 0% CPU but refusing to die.
Instead of brute force, she switched to forensic calm. She opened Terminal. Navigated to ~/Library/Application Support/Clio/ . She saw a file: Lockfile . That shouldn’t be there. A lockfile means the app thinks it’s already running—even after a reboot. A junior engineer later confirmed it was a
Priya Sharma, a 34-year-old freelance graphic designer and historian. She had been using Clio for six months to manage her client invoices, track her research time, and log her ancestry projects. For her, Clio wasn’t just an app—it was the spine of her chaotic solo practice.