Created attachment 1432829 [details] test.svg Description of problem: Inkscape crashes in Inkscape::UI::Tools::perform_bitmap_scanline_check when filling area from bucket. There is something special about this test file. It was created by importing some pdf file. Version-Release number of selected component (if applicable): inkscape-0.92.3-1.fc28 How reproducible: 100% Steps to Reproduce: 1. open attached file test.svg 2. chose the bucket tool 3. click fill on the red are of the test.svg Actual results: crash Expected results: should fill the area Additional info:
Created attachment 1432830 [details] core_backtrace
I can reproduce this with a file I created on my own. I can share the file privately if necessary, but would like to avoid posting it publicly. inkscape-0.92.3-2.fc28.x86_64
I'm seeing the same bug when trying to fill any area from bucket. How can I help? Inkscape 0.92.3-2.fc28
Observed consistently on Fedora 29 as well. inkscape-0.92.3-5.fc29.x86_64
The linked upstream bug report indicates that this problem is a packaging issue: the Fedora package exhibits the bug, but a hand compiled version does not.
The issue is continuing with 0.92.4 version.
I've asked in inkscape-devel IRC channel room, and Mc has responded to this: (that's because fedora packagers use -D_FORTIFY_SOURCE=2; these kind of bugs that were only reproducible on fedora before we knew why will slowly be fixed in the future now that I know how to cause them)
Does it still happen with 0.92.4-4?
Yes, the problem is carrying on with 0.92.4-4, and the problem is with RPM file and flatpak as well. A way to produce the issue: Draw a circle and a square and select them, then go to Path >> Division you will end up with a crash which closes the app
Ok, thanks. I can reproduce that, and I've offered to help upstream.
*** Bug 1679489 has been marked as a duplicate of this bug. ***
Is there any possibility of rebuilding the package *without* -D_FORTIFY_SOURCE=2? Right now, inkscape is totally unusable.
Yes. I was hoping to see movement on the upstream bug, but we can do this for the interim. Updates forthcoming.
inkscape-0.92.4-5.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2019-67616f15b6
inkscape-0.92.4-5.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-4411c81065
inkscape-0.92.4-5.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-66255a2c48
The issue has been solved in inkscape-0.92.4-5, thank you Gwyn Ciesla.
inkscape-0.92.4-5.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-66255a2c48
inkscape-0.92.4-5.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-67616f15b6
inkscape-0.92.4-5.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-4411c81065
inkscape-0.92.4-5.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.
inkscape-0.92.4-5.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.
inkscape-0.92.4-5.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.