Steps how to reproduce with Parallel Dev-Installation of "LibreOffice 3.5.0 Beta2- WIN7 Home Premium (64bit) German UI [Build-ID : 8589e48-760cc4d-f39cf3d-1b2857e-60db978]: 1. Open sample document from "Bug 44430 - [Task]: Sample for possible regressions of rendering, using a xls file (cell format, chart location, cale, legend etc..) from 3.3 to 3.4 to 3.5", compare to MS Excel Viewer and GNUMERIC 2. Sheet3 ------ MSEV: Chart X-scale 5000, Y-Scale 250 LibO: Y-Scale 250 wrongly 5000 !!! Gnumeric: Similar to MWEV Same problem in Sheet5 Scale was ok with "LibreOffice Portable 3.3.0 - WIN7 Home Premium (64bit) German UI [OOO330m19 (Build:6) tag libreoffice-3.3.0.4]", so Regression. Confirmed due to Bug 44430
No problem with "LibreOffice 3.4.5 RC1 - WIN7 Home Premium (64bit) German UI [Build ID: OOO340m1 (Build:501)]" in Sheet3 and Sheet5 Scale Sheet3, Sheet5 was ok Server installation of MSVC Master "LibO-dev 3.5.0 – WIN7 Home Premium (64bit) ENGLISH UI [Build ID: a286353-090bcba-3bf3b94]" Win-x86@6 – 2011-12-02_22:36:35) Sheet3 y-axis scale damaged with Server installation of Master "LOdev 3.5.0beta2+ – WIN7 Home Premium (64bit) ENGLISH UI [Build ID: 22905fb-b605e4f-4c1bcb5]" Win-x86@6- - pull time 2011-12-20 20:59:59), Chart Sheet5 ok My Mistake, Sheet5 is ok in 3.5.0Beta2 Y-axis scale problem for chart in Sheet7 (similar to sheet3 problem) starts after Server installation of MSVC Master "LibO-dev 3.5.0 – WIN7 Home Premium (64bit) ENGLISH UI [Build ID: 485138f-e92bf75-4c1bcb5]" Win-x86@6 – 2011-12-06_21:37:02) but with or befire Server installation of Master "LOdev 3.5.0beta2+ – WIN7 Home Premium (64bit) ENGLISH UI [Build ID: 22905fb-b605e4f-4c1bcb5]" Win-x86@6- - pull time 2011-12-20 20:59:59) @Kohei: Please feel free to reassign (or reset Assignee to default) if it’s not your area or if provided information is not sufficient. Please set Status to ASSIGNED if you accept this Bug.
This one might be a DUP of "Bug 44546 - chart y axis scale auto-detection is odd-to-broken", what describes the same problem as a more general problem also for .ods documents
I believe it IS a DUP *** This bug has been marked as a duplicate of bug 44546 ***