MathbookPro:Downloads tanellebedev$ sqlite3 kopsik.db
SQLite version 3.7.13 2012-07-17 17:46:21
Enter ".help" for instructions
Enter SQL statements terminated with a ";"
sqlite> .schema
Error: database disk image is malformed
Computer was powered down while Desktop was running.
I got same problem, and Toggl cannot continue to any other screen than login. Can you help me what to do?
'The database disk image is malformed: The database disk image is malformed'
Before this fix goes live the way to fix this situation is by deleting the local database.
/Users/<username>/Library/Application\ Support/KopsikThis is still an issue, why has this been closed?
what version are you experiencing it with?
we've added the journaling mode that could have fixed the issue (see above commit 4852ae1)
i'm using 7.3.87. When switching network locations from proxied (company) to non-proxied (home) environment i also have this issue. Removing the Kopsik folder is a workaround but requires login each time.
I have just experienced this problem and submitted a bug report through the app...
After much frustration searching the net for a solution, the advice from IndrekV above helped me out. On my MacBook Air, I just went to Finder, selected "Go" --> "Go to Folder...". Entered this, exactly: ~/Library/Application Support/Kopsik. Deleted all. Restarted. Thanks Indrek!
Just had this happen with v7.3.254. Mac froze / kernel panic, hard reset, then database was corrupted.
Just happened with v 7.3.309 Mac OS X 10.11.3.
Toggl timer was running along with many other apps… spinning beachball, lost control of apps. Activity Monitor was showing an empty list of Processes (!) Switched off iMac. After restart got "the database disk image is malformed" message on top of timer window that was apparently still running (but did not). I could not stop (or start) timer.
Removing the Kopsik folder worked fine. Login was required.
Thanks @IndrekV for the tip.
Customer has reported this message via Toggl support. Mac OS X, same 'Error: database disk image is malformed' message. Instructed them as to removing the Kopsik folder.
Same thing happened on Version 7.3.319.
Manually removing Kopsik/production from Application Support resolved issue.
I had the same issue today, removing the Kopsik folder from Application Support fixed it.
I encountered this issue as well, after doing a time machine migration to a new machine.
I encountered this as well after doing a time machine restore, just as @brennan-nc. Clearing cache doesn't work, it keeps getting corrupted.
Most helpful comment
Before this fix goes live the way to fix this situation is by deleting the local database.
/Users/<username>/Library/Application\ Support/Kopsik