Redo Duplicate Layer Crashes Inkscape

Reproduced with Inkscape 0.48.2 (official package, local build), 0.48.3, 0.48.4 and current trunk 0.48+devel r12340 on OS X 10.7.5.

> Reproduced with Inkscape 0.48.2 (official package, …) (…)

For the sake of completeness: also reproduced with 0.47, 0.48.0 and 0.48.1 (official Mac OS X packages) -> not related to the fix for bug #802090 released with 0.48.2.

Crash also reproduced on Ubuntu 12.10 (VM, 64bit) with Inkscape 0.48.3.1 and 0.48+devel r12340.

You my friendly bug, are Fixed! See r12395, using defaultLable() instead of getLabel() or getId() allows redo/undo multiple times without crash.

The changes from r12395 merge cleanly into <lp:inkscape/0.48.x>, and fix the crash otherwise easily reproducible with current stable 0.48.4 (tested with 0.48.x r9961 on OS X 10.7.5).

@Martin - any special reason not to backport your fix to the stable branch?

There is no reason not to, we should have a collection of bugs to backport. The adobe files/security bug one should be too.

> There is no reason not to, (…)

The question was with regard to a possible danger of breaking other things - we don't really want to risk introducing regressions in stable. Thx, I'll commit the change to the stable branch lp:inkscape/0.48.x

> (…) we should have a collection of bugs to backport.

Not sure I understand - are you asking whether such a collection already exists?

Here it is:
<https://bugs.launchpad.net/inkscape/+bugs?field.tag=backport-proposed>

Note: watch out for the milestones - the state 'Committed' refers to the milestone branch: several of the backport-proposed items have only been committed to trunk, others already to 0.48.x as well (some of them earlier today).

> The adobe files/security bug one should be too.

I won't touch that one ;) - but it certainly would be great it got backported to stable.

Fix backported to lp:inkscape/0.48.x in revision 9962.