Created attachment 118759 [details] Calculation of commercial-technical parameters of biogas factorys X-Y-Graphic in Excel File are shown wrong in version 4.4, 4.5, 5.01 Please have a look to the enclosed Excel file with Excel and LibreOffice kind regards Geert Closius
Please attach printscreen from excel, thank you
Created attachment 118764 [details] Screenshot of document in Excel 2007 Tested in Calc Version: 5.0.2.1.0+, Build ID: 00m0(Build:1), Locale: en-GB (en_GB.UTF-8) on openSuSE 13.1 (64-bit). Observations of things going wrong in Calc: -Graphs are squashed vertically to about half the height, exposing a blue background square. - X axis titles are misplaced - Several "enclosed objects" (excel description) with equations have a blue background, and can not be edited in any way. To be fair, in excel 2007 on the Windows test machine the enclosed objects can not be edited as well. The equation editor might not be installed on this machine.
Confirmed in LibreOfficeDev MASTER Version: 5.1.0.0.alpha1+, Build ID: 88b6dd3ea77ca9f6d5fac2965cea6ff0634e6ba5, Locale: en-GB (en_GB.UTF-8) on openSuSE 13.1 An additional observation of an import error in Calc (see also comment 2): - Direct text entries for the Range Name are not imported correctly. I have observed similar import errors with other XLS files in the past. attachment 118759 [details] is an excellent test case for these.
These errors do not occur in OpenOffice.org 3.3.0 (32-bit) on Windows 7: - Graphs are not squashed vertically; - X axis titles are placed correctly; - No blue backgrounds for graphs and "enclosed objects". Therefore marking as a regression, possible bibisect candidate.
Adding keyword 'bibisectRequest'.
Reproduced with v4.0.0.3 / Ubuntu 16.04, except blue background, that is reproduced with v4.1.0.4. Adjusting version.
** 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 on a currently supported version of LibreOffice (5.4.1 or 5.3.6 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170929
Still repro, but only the squashing. Multiple issues in one report would be wrong anyway. Arch Linux 64-bit Version: 6.1.0.0.alpha1+ Build ID: eeaf6dee2d278eaa037d95a756ad0ffab3314bc2 CPU threads: 8; OS: Linux 4.16; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on May 24th 2018
Bibisected with 43all on Linux to range https://cgit.freedesktop.org/libreoffice/core/log/?qt=range&q=ae4e4a11d4300f7448cb6bd170fcb034542caddc...4316e643ef345b0f673b4a03a80a4b7cb3185588 I am unable to locate a suspicious commit.
Did detective work in the range: https://wiki.documentfoundation.org/QA/Bibisect#Doing_detective_work_inside_a_commit_range Maybe it is this mega-commit: https://cgit.freedesktop.org/libreoffice/core/commit/?id=44cfc7cb6533d827fd2d6e586d92c61d7d7f7a70 It has "fix for #118525#: Using primitives for chart sub-geometry visualisation"
Created attachment 151406 [details] comparison MSO 2010 and LibreOffice 6.3 Master
Still reproducible in Version: 6.3.0.0.alpha0+ Build ID: 630db80d17616d635cf2e5f1d5a0852428b794a3 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
Dear Geert Closius, 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 https://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
Dear Geert Closius, 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 https://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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
This is caused by trying to use the chart2 view information in the import filter. I have a fix for this regression but there are still a few small positioning differences between Calc and Excel. This needs another issue at some point with a number of test documents.
Markus Mohrhard committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/0bfca02bf492ec917633388aa01421a1e0dad31a tdf#94259: don't use the non-existed chart view during import It will be available in 26.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Markus Mohrhard committed a patch related to this issue. It has been pushed to "libreoffice-25-8": https://git.libreoffice.org/core/commit/18b40b3964f9fc658abbb6cee1d6401842ffe36c tdf#94259: don't use the non-existed chart view during import It will be available in 25.8.1. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.