Description: Graphics is partially lost if converted from metafile to curve or polygon or contour. In this example a 1 survives the conversion, but the 0 does not. Steps to Reproduce: Open 10-meta.odg (attached) Ctrl-A Modify > Convert > To curve Save as > 10-curve.odg Modify > Convert > To metafile Save as > 10-meta1.odg Modify > Convert > To polygon Save as > 10-polygon.odg Modify > Convert > To metafile Save as > 10-meta2.odg Modify > Convert > To contour Save as > 10-contour.odg Re-open all saved files. Actual Results: The 1 is in all files. The 0 is missing in 10-curve.odg, 10-polygon.odg, 10-contour.odg Expected Results: The 1 is in all files. The 0 is in all files. Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: da Module: DrawingDocument [Information guessed from browser] OS: Windows (All) OS is 64bit: no User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.90 Safari/537.36
Created attachment 137303 [details] 10-meta.odg
Possibly related to Bug 113039.
The Graphics is partially lost if converted from metafile to curve or polygon or contour.
Workaround: Convert to metafile before saving. Convert back to curve/poly/contour for editing. Then back to metafile. Then Save.
Issue is reproduced on both following environments : • Operating system : Windows 8.1 Pro 64-bits. • LibreOffice : Version: 5.4.2.2 Build ID: 22b09f6418e8c2d508a9eaf86b2399209b0990f4 CPU threads: 4; OS: Windows 6.2; UI render: default; Locale: en-US (en_US); Calc: group And also on : • Operating system : Ubuntu 16.04.3 64-bits. • LibreOffice :Version: 5.4.2.2 Build ID: 22b09f6418e8c2d508a9eaf86b2399209b0990f4 CPU threads: 8; OS: Linux 4.4; UI render: default; VCL: gtk2; Locale: ja-JP (ja_JP.UTF-8); Calc: group
** 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
Bug is still present in: Version: 6.1.2.1 (x64) Build ID: 65905a128db06ba48db947242809d14d3f9a93fe CPU tråde: 4; Styresystem: Windows 10.0; Gengiver af brugergrænseflade: Standard; Lokalisering: da-DK (da_DK); Calc: CL
Dear Ole Tange, 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
Version: 6.3.2.2 (x86) Build ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c