Let’s do a manual lock break then.
(To simulate your problem for screen captures, I just started gramps, loaded my “Example52” tree and killed the gramps task. This abnormal exit caused a Lock to be left behind.)
Select your locked file in the Family Trees → Manage Family Trees… dialog and click the Info button:
This will tell you the exact path to the database folder for that Tree. (My database path is very unusual because it is a testing box. The really important part is the final 8 characters because the folder has a “hexadecimal” filename that is hard to remember. In the Example52 tree example, the foldername is
64f6893a) Navigate to that folder in your OS then leave the folder open but quit Gramps.
Delete the lock file (This screen capture is from the Files Manager in Fedora Linux. A macOS file manager will have a somewhat different appearance.)
Restarting Gramps should now allow the Tree to load.
Once your tree loads again:
Make a Backup immediately.
Then use the Tools → Family Tree Repair → Check and Repair Database… tool to fix any damage that might be related to the unexpected power-down.
