Steps to reproduce:
1. Open attachment 153993 [details] from bug 127412
2. Select shape 3
3. Move it somewhere else
-> Shape 1 and 3 are moved to the same position. Only shape 3 should be moved back to the original position.
Build ID: 498c2d3944b666c2f016b65903001920db2cb2a4
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3;
Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US
Regression introduced by:
author Vasily Melenchuk <email@example.com> 2019-08-15 12:08:06 +0300
committer Thorsten Behrens <Thorsten.Behrens@CIB.de> 2019-08-21 00:24:58 +0200
commit db257d6605143813e0b75ffa878a18810c8b3412 (patch)
parent ff3cfee4ebfcb412f54f17ffccc95512fdc15c8e (diff)
sw undo/redo: avoid usage of pointers as a style references
Bisected with: bibisect-linux64-6.3
Adding Cc: to Vasily Melenchuk
While this task has different scenario, reason of this problem is the same as tdf#128782.
*** This bug has been marked as a duplicate of bug 128782 ***
*** Bug 133069 has been marked as a duplicate of this bug. ***
This is still valid for 7.0.0 alpha1. However, it is fixed in master by https://git.libreoffice.org/core/+/0b0de876bad66c84a8dd0d8d19944109e59cf21a%5E!/
sw: set unique name for shape format even if shape name is empty
Vasily: can you backport that to 6.4 and 7.0?
Changing status to fixed as this was not covered by the fix for bug 128782.
@Buovjaga backport for 6.4 is in gerrit https://gerrit.libreoffice.org/c/core/+/94373
For 7.0 i see no branch yet: is it already forked?
(In reply to Vasily Melenchuk (CIB) from comment #5)
> @Buovjaga backport for 6.4 is in gerrit
> For 7.0 i see no branch yet: is it already forked?
Ok, sorry about that: I got confused. Branching is only in 2 weeks, so the fix will be included in Beta1 anyway. Thanks for the backport!
Vasily Melenchuk committed a patch related to this issue.
It has been pushed to "libreoffice-6-4":
tdf#128665: sw: set unique name for shape format
It will be available in 6.4.5.
The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
Affected users are encouraged to test the fix and report feedback.