search

gillescastel / inkscape-figures

Inkscape figure manager
MIT License
557 stars 119 forks source link

Unable to lock on the pidfile #46

Open ChrissyyyLi opened 2 years ago

ChrissyyyLi commented 2 years ago

Everything ran fine on my old MacOS 11.3, but somehow I decided to update to 12.3.1 Monterey... What a terrible mistake. Now when running Inkscape-figures watch for the first time as part of my ~/.zprofile, an error occurs: "Unable to lock on the pidfile." Subsequently cmd+s in Inkscape will no longer save properly.

However, when running with the Inkscape-figures watch --no-daemon option, there is no such error.

A temporary solution to this issue appears to be: in a separate terminal, run Inkscape-figures watch --no-daemon every time you need it to work.

Is there a better fix?

gillescastel commented 2 years ago

Unable to lock pid file probably means that it is already running. Can you check that? Or kill the program with killall inkscape-figures or whatever the equivalent is on MacOS.

BLACKSWORD0 commented 1 year ago

I have the similar problem. But in my case, if I just input "inkscape-figures watch" in my terminal , it works well. When I want to stop the process, if I input "killall inkscape-figures", it will say "No matching processes belonging to you were found". If I input "killall fswatch"(since my system version is macos 12.6, main.py uses fswatch. ) , it will stop smoothly. However, after that if I input "inkscape-figures watch" again, it will say "Unable to lock on the pidfile."

I don't know why it can't work in this situation. Is there any help?