Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to lock on the pidfile #46

Open
ChrissyyyLi opened this issue May 19, 2022 · 2 comments
Open

Unable to lock on the pidfile #46

ChrissyyyLi opened this issue May 19, 2022 · 2 comments

Comments

@ChrissyyyLi
Copy link

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
Copy link
Owner

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
Copy link

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants