Closed juhp closed 4 years ago
Workaround is just to create ~/.hawk/
manually.
Hmm, hawk
is supposed to create that folder for you if it doesn't exist. I am guessing that the locking mechanism is now being activated too early, before we got a chance to create the folder.
Indeed, that was a regression introduced by #172, which switched the locking mechanism from a socket-based to a file-based approach. We've always been activating the lock before creating the folder, but that used not to be a problem.
Thanks, looks good now :+1:
I am not sure what it is going on but when I try to use hawk in a new system after a long break I got:
Just for transparency this is running in a Fedora Toolbox user container, but I don't think that should matter.