inkstitch
inkstitch copied to clipboard
inkstitch
ResourceWarning in Select (tartan linux pre-release)
Playing around with tartans (neat, btw!) and decided to try out the new Select stuff. It couldn't find my py3 (~/.pyenv/shims/python3 if we're taking notes on possible locations) so I entered it, and got this:
subprocess.py:946: ResourceWarning: subprocess 229312 is still running
ResourceWarning: Enable tracemalloc to get the object allocation traceback
Closed and reopened Inkscape in hopes it would terminate the subprocess but nope. (Also didn't realize "Apply" was going to attempt the Select rather than applying the directory choice, though that might be an Inkscape UI quirk.)
Not sure if that's just a pre-release thing or just my janky python situation, but there it is.
Thank you for trying the dev builds. Actually I wanted to tell you just now that now the build versions should work much better than a few days ago and that you could start trying to break them :) This issue though should be fixed in main by now. I should rebase the tartan branch to fix it.
Ooh nifty.
Doesn't get the ResourceWarning with that one, though it doesn't do any selecting (or deselecting, if I start with an active selection).
I did manage to segfault(!) Inkscape somehow once, but I can't reproduce that. Launching it from the command line doesn't show any useful error messages (just the usual unknown-type warnings; someday I should find where to shut that off).
And the two-rung detection works in Troubleshooting, at least, so I am off to fix fonts, woo hoo!
Okay, DinoMouse is fixed, since that didn't take long maybe I'll just fix Emiliohhhhh no.
On second thought, maybe I'll just contemplate what it would take to write a third-rung-adding Perl script.
That's ... chaos :D Claudine said she is brave enough to face it, so no worries about Emilio, it will be fixed.
Doesn't get the ResourceWarning with that one, though it doesn't do any selecting (or deselecting, if I start with an active selection).
So this is working if you do not have any previous selection?
No, it just doesn't give an error. (It doesn't appear to do anything.)
If you give me a known-good file that successfully selects I can see if it's just my weird files.
The select elements extension should work now ok-ish. Button will need to be pushed twice sometimes though. At least no ResourceWarning is to be expected ... I think.