<!-- See our full bug reporting guidelines at https://inkscape.org/contribute/report-bugs/ Writing a good bug report will ensure we'll be able to help efficiently. 🙂 --> #### Summary: As the title implies, Inkscape encounters an internal error, and the program terminates. #### Steps to reproduce: <!-- Describe what you did (step-by-step) so we can reproduce: --> - open Inkscape. - create an inverse clip of an object (a triangle with flat faces drawn with "Bezier and straight line" tool, in my case) and a path (from a cutted square outline, which is the same programmatically, because it gets converted I presume). - save it as an SVG. - re-open Inkscape, and load the svg file. - release the clipped object. #### What happened? I have no idea what the errors are, it just straight up prompt me internal error, and then you just press the button to terminate the program. #### What should have happened? - the clip should have been released into the original paths, and an object (a triangle, in my case). Sample attachments: <!-- Attach the sample file(s) highlighting the issue, if appropriate. --> #### Version info Version: Inkscape 1.1.1 (3bf5ae0d25, 2021-09-20) on Parrot Home Edition (LTS) GNU/Linux. <!-- Open 'Help > About' and click on the little bug icon in the bottom right corner that copies the debug information to your clipboard. For command line users, run 'inkscape --debug-info'. For Inkscape 1.0.2 and older, please manually add the Inkscape Version and Operating System Version. The Inkscape version is listed in the About dialog. For command line users, run 'inkscape -V' Paste the information in the empty space between the apostrophes below: --> ``` ``` <!-- ❤️ Thank you for filling in a new bug report, we appreciate the help! ❤️ Please be patient while we try to find the time to look into your issue. Remember that Inkscape is developed by volunteers in their spare time, we'll try our best to respond to all reports. --> <!-- Please be careful when/after writing # for example in logs, code, or versions of linux - use inline code span - single backticks (`) before and after it, like this - `#1618` - use multi-line code block - triple backticks (```) to fence/enclose console logs - attach long logs as a text file. -->