Description: The doc-file with CorelDraw-unit is not displayed correctly (see attachment). Steps to Reproduce: - Create a drawing in the CorelDRAW. - Paste it in MSWord-file. - Open the file in the LibreOfficeWriter. Actual Results: We see distortion. Expected Results: display without distortion. Reproducible: Always User Profile Reset: No Additional Info: In the attachment: - A block diagram of the problem (diagram of bug.odg). - File with problematic data (data.doc). User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.79 Safari/537.36 Edge/14.14393
Created attachment 129760 [details] description of the bug
Created attachment 129761 [details] source-data
Confirming with: Version: 5.4.0.0.alpha0+ Build ID: 53edf60c4ce6ed32f87471e018878c40b788005a CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; TinderBox: Win-x86@42, Branch:master, Time: 2016-12-18_06:57:59 Locale: nl-NL (nl_NL); Calc: CL and with Versie: 4.4.6.3 Build ID: e8938fd3328e95dcf59dd64e7facd2c7d67c704d Locale: nl_NL and with Version: 4.3.0.4 Build ID: 62ad5818884a2fc2e5780dd45466868d41009ec0 and with: Versie: 4.2.0.4 Build ID: 05dceb5d363845f2cf968344d7adab8dcfb2ba71 but not with: Versie: 4.1.0.4 Build ID: 89ea49ddacd9aa532507cbf852f2bb22b1ace28
Regression introduced by: author Jan Holesovsky <kendy@collabora.com> 2013-11-21 15:28:32 (GMT) committer Jan Holesovsky <kendy@collabora.com> 2013-11-25 13:10:46 (GMT) commit 4ba2b2ae62276ab7b40ba5730d631ad4b3fd6ac8 (patch) tree b17713c55073c9acb1f61bbc10bf7bf718d91865 parent 9d3c0aa1e64ae97ddc305df3873f977051f0b317 (diff) fdo#61272: Do the mapping correctly both for WMF and EMF. Turns out that for the WMF, we already had everything set up correctly, we were just overwriting the right settings with default data again :-) - fix that. Adding Cc : to Jan Holesovsky @Kendy: it looks like reverting the commit above fixes the problem and doesn't break fdo#61272. Could you take a look? probably just reverting the commit fixes everything...
Xisco: Too bad I did not create a unit test at the time of the fix, we could be sure now if reverting is OK :-( [because it is possible that something else has changed making the previous fix obsolete] Xisco: would it be possible to isolate what exactly my patch fixed? Unfortunately I don't remember; ideally if you could try in the bibisect repo how the document from bug 61272 looked like before 4ba2b2ae62276ab7b40ba5730d631ad4b3fd6ac8 and after that (ie. what was the exact difference that my patch fixed)? Thank you!
(In reply to Jan Holesovsky from comment #5) > Xisco: Too bad I did not create a unit test at the time of the fix, we could > be sure now if reverting is OK :-( [because it is possible that something > else has changed making the previous fix obsolete] > > Xisco: would it be possible to isolate what exactly my patch fixed? > Unfortunately I don't remember; ideally if you could try in the bibisect > repo how the document from bug 61272 looked like before > 4ba2b2ae62276ab7b40ba5730d631ad4b3fd6ac8 and after that (ie. what was the > exact difference that my patch fixed)? Hi Jan, I've done some bisections here and the files in bug 61272 look the same even with 4ba2b2ae62276ab7b40ba5730d631ad4b3fd6ac8 or without it. However, the real fix for bug 61272 is done by 198b17dc5e182dfb2e5c930458764c7b3e6c914f. So I can't really tell what 4ba2b2ae62276ab7b40ba5730d631ad4b3fd6ac8 fixes using the files in bug 61272. Do you know how to get file n#417818 ?
Putting back to NEW as there's no assignee to this bug
Created attachment 132922 [details] Image extracted from document
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
In LibreOffice: Версия: 6.0.3.2 (x64) ID сборки: 8f48d515416608e3a835360314dac7e47fd0b821 Потоков ЦП: 8; ОС:Windows 10.0; Отрисовка ИП: по умолчанию; Локаль: ru-RU (ru_RU); Calc: group bug is present.
Adding Cc: to Jan Holesovsky
Dear lex, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Created attachment 170994 [details] MS Word vs LibreOffice 7.2 master comparison Unfortunately I cannot reproduce this issue: Version: 7.2.0.0.alpha0+ / LibreOffice Community Build ID: 615ceb107e9faf01b568b0a2440a3f09c8f88ca6 CPU threads: 8; OS: Mac OS X 10.15.7; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
This issue got fixed by https://cgit.freedesktop.org/libreoffice/core/commit/?id=b0b78838e795fcd7f3c53e7f74fb32b2921a5ccb