Bug 127555 - Formatting, regression. Grouped drawing object on a wrong page and overlaps another drawing object
Summary: Formatting, regression. Grouped drawing object on a wrong page and overlaps a...
Status: RESOLVED DUPLICATE of bug 118693
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) release
Hardware: All All
: medium normal
Assignee: Not Assigned
Keywords: bibisected, bisected, regression
Depends on:
Blocks: Regress-elim-SvxShapePolyPolygonBezier
  Show dependency treegraph
Reported: 2019-09-15 11:08 UTC by Juha
Modified: 2021-03-17 23:39 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:

Sample file that has this problem (91.21 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2019-09-15 11:11 UTC, Juha
Comparison image between MS and LO (375.87 KB, image/png)
2019-09-15 11:24 UTC, Juha

Note You need to log in before you can comment on or make changes to this bug.
Description Juha 2019-09-15 11:08:30 UTC
There is severe regression. On LO (x64) the grouped drawing object on the first page is on the correct position. Now it has moved to the second page and it overlaps the drawing object of the second page. This regression noticed on Lo (x64)

Steps to Reproduce:
Just open the sample file and check the locations of drawing objects.

Actual Results:
The grouped drawing object has moved to the second page to overlap another drawing object.

Expected Results:
The grouped drawing object should be on the first page, on it's correct page.

Reproducible: Always

User Profile Reset: Yes

OpenGL enabled: Yes

Additional Info:
Versio: (x64)
Käännöksen ID: b79626edf0065ac373bd1df5c28bd630b4424273
CPU-säikeet: 12; Käyttöjärjestelmä: Windows 10.0; Piirtokomponentti: GL; VCL: win; 
Maa-asetus: fi-FI (fi_FI); Käyttöliittymän kieli: fi-FI
Calc: CL
Comment 1 Juha 2019-09-15 11:11:33 UTC
Created attachment 154170 [details]
Sample file that has this problem
Comment 2 Juha 2019-09-15 11:24:04 UTC
Created attachment 154171 [details]
Comparison image between MS and LO
Comment 3 Juha 2019-09-15 11:25:12 UTC
Oh, I also noticed that both groped drawing objects have shrunk in size.
Comment 4 m_a_riosv 2019-09-15 11:53:11 UTC
Repro with
Version: (x64)
Build ID: f0c832acb53326ccc9a8c1a47401fbc9e1081feb
CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; 
TinderBox: Win-x86_64@62-TDF, Branch:master, Time: 2019-09-11_05:46:53
Locale: en-US (es_ES); UI-Language: en-US Calc: threaded

Looking with the navigator, there is only one group, there also it's no option to select the OLE objects because the have not name and only the first it's selected, no matter in which you click on. 

Shows the two groups but not the OLE names with
Versión: (x64)
Id. de compilación: 5d2cb2a5dd04fe174b336488731eb50bbb5faed3
Subprocs. CPU: 4; SO: Windows 10.0; Repres. IU: GL; 
Configuración regional: es-ES (es_ES); Calc: group threaded
Comment 5 raal 2019-09-16 20:19:40 UTC
This seems to have begun at the below commit.
Adding Cc: to Armin Le Grand ; Could you possibly take a look at this one?
 a35ab2611687602ed7c0b9856f2ced2278e31112 is the first bad commit
commit a35ab2611687602ed7c0b9856f2ced2278e31112
Author: Jenkins Build User <tdf@pollux.tdf>
Date:   Mon Jul 2 18:38:24 2018 +0200

    source 36bade04d3780bc54c51b46bb0b63e69789658a5

author	Armin Le Grand <Armin.Le.Grand@cib.de>	2018-06-28 19:48:59 +0200
committer	Armin Le Grand <Armin.Le.Grand@cib.de>	2018-07-02 18:03:44 +0200
commit 36bade04d3780bc54c51b46bb0b63e69789658a5 (patch)
tree c4465bf33aa2cda65511a2c094688522e9c9b43a
parent 942f1056b51e53358d42ff8da8a1bbdce9ba5303 (diff)
tdf106792 Get rid of SvxShapePolyPolygonBezier
Comment 6 Timur 2020-03-11 12:28:57 UTC
Same reporter and similar documents, duplicate.

*** This bug has been marked as a duplicate of bug 96640 ***
Comment 7 Timur 2020-03-11 12:29:58 UTC
Please search before reporting and confirming, or we loose time to confirm and bibisect.
Comment 8 Aron Budea 2021-03-17 23:39:15 UTC

*** This bug has been marked as a duplicate of bug 118693 ***