Undo Stroke to Path destroys clones, crash

Bug #700772 reported by Stratadrake
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Inkscape
Triaged
Medium
Unassigned

Bug Description

Encountered in Inkscape 0.48.0 (will attempt in 0.48.1 when available):

1 - Create any convenient object on canvas and then clone it. Move the clone somewhere convenient.

2 - Select the original object and convert its stroke to a path (Object > Stroke to Path).

3 - Select Edit menu > Undo. At this point, all clones of the object have disappeared from view.

4 - Select the master object and clone it again. Nothing happens; statusbar reports "Orphaned Clone in (Layer). Use Shift+D to lookup original" .

5 - Edit menu > Clone > Find Original (Shift+D). Statusbar reports "Cannot find the object to select (orphaned clone, etc.)".

6 - Edit menu > Clone > Unlink Clone. Crash.

So far this only occurs with "Stroke to Path". "Object to Path" does not reproduce this behavior or the crash.

Tags: clones undo
Revision history for this message
su_v (suv-lp) wrote :

> 6 - Edit menu > Clone > Unlink Clone. Crash.

The crash has been fixed in trunk and the branch for 0.48.1, see
Bug #675309 “crash when unlinking an orphaned clone”
<https://bugs.launchpad.net/inkscape/+bug/675309>

tags: added: clones undo
Revision history for this message
su_v (suv-lp) wrote :

Steps 1-5 reproduced with Inkscape 0.48+devel r10000 on OS X 10.5.8:
(step 6 and resulting crash when unlinking orphaned clones has been fixed).

Changed in inkscape:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
su_v (suv-lp) wrote :

The clones are not actually destroyed - if you save the document after step 4 and reopen it, all clones are present and displayed as expected.

Revision history for this message
Beluga (buovjaga) wrote :

Still repro.

Arch Linux 64-bit, KDE Plasma 5
Inkscape 0.92pre1 15054 (GTK3)

jazzynico (jazzynico)
Changed in inkscape:
status: Confirmed → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.