Loop when cloning a path with a marker: "set marker color"
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Inkscape |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
Using:
Inkscape 0.92.2 2405546, 2018-03-11
Archlinux updated
The bug is very easy to trigger, and I tested in two different computers (although both with the information said above). Restarting user settings does not help.
Steps to reproduce:
1. Create a straight line.
2. Open fill and stroke.
3. Set a marker at the end.
4. Clone it.
5. Move the clone away.
6. Optional: Open the undo history window, so you can see what is happening.
7. Select the original path. At this point, Inkscape will become unresponsive for some tasks: you will not be able to open any menu (for example, Edit menu).
8. Deselect the path by clicking anywhere else.
Actual program behaviour:
By looking at the undo history, you will notice that between steps 7 and 8 Inkscape was continuously setting the mark colour (you can see that it did it scores of times, even hundreds if you wait a few seconds before step 8).
Expected program behaviour:
One expects to be able to manipulate the original path when done a clone, as it is possible with any other kind of object. This bug implies that you cannot manipulate some parts of it anymore, for example, you cannot change its colour.
Workaround:
If you substitute step 8 for "make a group" (with Ctrl+G, as you cannot open Object menu > Group), the bug will stop for that time (you will notice in undo history that was triggered until that moment) and forever (unless you try to select inside the group holding Ctrl), but that still makes impossible to change path colour.
One more workaround:
Use Path menu > Stroke to Path before cloning the object. You will still be able to change its colour, but you will lose easy node editing.
Extra:
- If you, instead of cloning, just make a duplicate, you will get that "set the mark colour" in the undo history, but only once, when you actually did not do that.
- If you substitute 8 for a secondary click and then a normal click, the mouse menu will remain there forever, unless you close Inkscape or go back in history until you undo all problematic steps. I guess this is caused by some internal crash caused by being in an infinite loop.
Maybe this bug is related with (and sorry if it is a duplicate, I am not sure):
- https:/
- https:/
- https:/
- https:/
| Alvin Penner (apenner) wrote | #1 |
| Changed in inkscape: | |
| status: | New → Confirmed |
confirmed on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)
in step 7, after selecting the original path, the CPU usage rose to about 30%, and returns back to zero only after deselecting the path. While the path was selected, it was not possible to edit the stroke paint or fill in the Fill&Stroke dialog.