Bug 103006 - FILESAVE rotated drawing object (not an pure image) falsely cropped in docx roundtrip when opened in MSWord
Summary: FILESAVE rotated drawing object (not an pure image) falsely cropped in docx ...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.3 all versions
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, filter:docx, regression
Depends on:
Blocks: DOCX-Images Image-Crop
  Show dependency tree / graph
 
Reported: 2016-10-05 10:01 UTC by Milos Sramek
Modified: 2019-02-09 20:31 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
Documents illustrating the problem (66.41 KB, application/x-zip-compressed)
2016-10-05 10:01 UTC, Milos Sramek 		Details
saved in master 63, opened in MsWord (128.38 KB, image/png)
2019-02-09 17:07 UTC, Cor Nouws 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Milos Sramek 2016-10-05 10:01:10 UTC 
Created attachment 127821 [details]
Documents illustrating the problem

Hi,
Rotated image in a docx document is erroneously cropped when saved back in docx and opened in MSWord. It is OK when opened in LO.

See attached files:
rotImage.docx: original saved by MSWord 2010
rotImage-LO43.docx: opened and saved by LO43


regression, bibisected using the lo-linux-dbgutil-daily-till43 repository

git bisect start 'master' 'oldest'
# bad: [91a3610703bc28b3b7bf6200fa320edf1a061a75] 2014-03-03
git bisect bad 91a3610703bc28b3b7bf6200fa320edf1a061a75
# bad: [519adebadb9c1e0c5322fb6d5ccf098b42d69547] 2014-01-16
git bisect bad 519adebadb9c1e0c5322fb6d5ccf098b42d69547
# bad: [50bc7bbcbf59370a6bf943ae1310f254e3677bd2] 2013-12-20
git bisect bad 50bc7bbcbf59370a6bf943ae1310f254e3677bd2
# good: [c60df0d0c7fd84869c8e5a1205acce90624b991d] 2013-12-06
git bisect good c60df0d0c7fd84869c8e5a1205acce90624b991d
# good: [27765beead77d11f986b869e8b1a1fc55afba4ec] 2013-12-13
git bisect good 27765beead77d11f986b869e8b1a1fc55afba4ec
# good: [a3090d781ea896d9d5961c92fc61cd5e5ba07c9d] 2013-12-17
git bisect good a3090d781ea896d9d5961c92fc61cd5e5ba07c9d
# bad: [b35c742ff5fec317e3b5d6c3812c8b76d7905083] 2013-12-19
git bisect bad b35c742ff5fec317e3b5d6c3812c8b76d7905083
# good: [8c8ddac9b845fb958e7616e9b7f885bb7b5c82fd] 2013-12-18
git bisect good 8c8ddac9b845fb958e7616e9b7f885bb7b5c82fd
# first bad commit: [b35c742ff5fec317e3b5d6c3812c8b76d7905083] 2013-12-19
Comment 1 Xisco Faulí 2016-10-05 11:36:30 UTC 
Confirmed in

Version: 5.3.0.0.alpha0+
Build ID: ae3ec79354f7b4967e736c6a4cd7c08fc52e2b7d
CPU Threads: 4; OS Version: Linux 4.2; UI Render: default; 
Locale: ca-ES (ca_ES.UTF-8); Calc: group
Comment 3 Xisco Faulí 2016-10-05 13:52:45 UTC 
Can't be bisected with bibisect-43max :-(
Comment 4 Xisco Faulí 2017-09-09 20:26:04 UTC 
Same range of commits in bug 99810. Maybe they're related...
Comment 5 QA Administrators 2018-09-10 02:37:07 UTC Comment hidden (obsolete)
Comment 6 Cor Nouws 2019-02-09 17:07:43 UTC 
Created attachment 149054 [details]
saved in master 63, opened in MsWord

Is ok in Version: 6.3.0.0.alpha0+
Build ID: b45289e48e0f354b9996e2846dd041db4a9947ce
CPU threads: 4; OS: Linux 4.15; UI render: GL; VCL: gtk3; 
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-02-08_12:51:03
Locale: nl-NL (nl_NL.UTF-8); UI-Language: en-US
Calc: threaded
Comment 7 Cor Nouws 2019-02-09 17:08:03 UTC 
 thus ..