Description: After saving the document in ODS format its layout is destroyed. Steps to Reproduce: 1.open the attached xls file 2.check the layout of Page 4 3.save the file as ods 4.close LO 5.open the created ods file 6.compare the layout with the original Actual Results: The embedded arrows change in size, position and even orientation. Expected Results: I want this shit to look like it was when i saved it. Reproducible: Always User Profile Reset: No Additional Info: User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:54.0) Gecko/20100101 Firefox/54.0
Created attachment 135222 [details] xls for the test case
Additional Info: This also happens if I edit the created ODS file and move or resize the arrows. The result when loading the file later after saving it will always be different from what I created.
Perhaps it would be smart to give a try to a recent LO version? 4.3 branch is EOL (like all 4.X branches, 5.1 and 5.2) so you can give a try to 5.3.4.
I confirm with Version: 6.0.0.0.alpha0+ Build ID: e371ec501db0c473bea7ef7325d9a9049f913b5e CPU threads: 8; OS: Linux 4.9; UI render: default; VCL: kde4; Locale: nl-BE (en_US.UTF-8); Calc: group and Version: 5.3.4.2 Build ID: SlackBuild for 5.3.4 by Eric Hameleers CPU Threads: 8; OS Version: Linux 4.9; UI Render: default; VCL: kde4; Layout Engine: new; Locale: nl-BE (en_US.UTF-8); Calc: group
Corrected version.
farmboy: Version field must correspond to the oldest version when the bug is encountered.
I changed the version to the one for which I reported the error. The original version i gave was an error. I didnt ever use LO4.
farmerboy: ok then. Anyway, since Xavier confirmed the bug with LO 5.3.4.2 in comment 4, let's put the version accordingly.
** 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
Still happening with LO 6.0.6.
Dear farmboy0+libreoffice, 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
The bug is to some extend still present. Info from About page: Version: 6.2.8.2 Build ID: Gentoo official package CPU threads: 16; OS: Linux 5.3; UI render: default; VCL: kde5; Locale: de-DE (de_DE.utf8); UI-Language: en-US Calc: threaded To reproduce follow these steps: 1. open the attached xls file 2. note the arrow locations and directions on page 4 3. save the file as ods 4. close calc 5. open the newly saved ods 6. compare with 2.
Still reproducible in Version: 6.5.0.0.alpha0+ Build ID: 4a8d3b80283cec4a93dd697eab70afcb82f04f4f CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US Calc: threaded
it seems the rotation problem was introduced somewhere in LibreOffice 5.1. Arrows in page 4 are correctly rotated in Version: 5.0.0.0.alpha1+ Build ID: 0db96caf0fcce09b87621c11b584a6d81cc7df86 Locale: ca-ES (ca_ES.UTF-8) and they are wrong in Version: 5.2.0.0.alpha0+ Build ID: 3ca42d8d51174010d5e8a32b96e9b4c0b3730a53 Threads 4; Ver: 4.15; Render: default; thus, it needs to be bisect with bisect 5.1
(In reply to Xisco Faulí from comment #14) > it seems the rotation problem was introduced somewhere in LibreOffice 5.1. > Arrows in page 4 are correctly rotated in This seems to have begun at the below commit. Adding Cc: to Henry Castro; Could you possibly take a look at this one? Thanks 0c9da5d5b253b1322b5cf8ecc109c4b00c13b4aa is the first bad commit commit 0c9da5d5b253b1322b5cf8ecc109c4b00c13b4aa Author: Norbert Thiebaud <nthiebaud@gmail.com> Date: Sat Jul 11 12:56:01 2015 -0700 source 487880b6882ec01c1b4679eae60bec484272a86b author Henry Castro <hcastro@collabora.com> 2015-04-24 16:55:01 -0400 committer Andras Timar <andras.timar@collabora.com> 2015-05-28 04:59:27 +0000 commit 487880b6882ec01c1b4679eae60bec484272a86b (patch) tree 7d0c2c7c333ad7f2b86c8f8572ad89652141a790 parent be01d68420086fc36ecf26b5f597ba7c6b29b369 (diff) Resolves tdf#67712 form controls and draw objects
It is a file open error with vertical flipped custom shapes. Proposed patch is in https://gerrit.libreoffice.org/c/core/+/104643. Waiting for review.
Should be fixed with https://cgit.freedesktop.org/libreoffice/core/commit/?id=1f0b3c7a40edfa81bbc7a58d123a6a2dfd83e4ca (The patch covers several bug reports, therefore no automatic notification.) I set this to fixed. In case you still see problems, please write a new bug report and attach a _small_ file, which shows the error.
Verified in Version: 7.1.0.0.alpha1+ Build ID: 9c8ed8c8526b9b696d0bf592eb7d963950f3cef4 CPU threads: 4; OS: Linux 5.7; UI render: default; VCL: x11 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded @Regina, thanks for fixing this issue!!