Description: when you open a save ods file with a diagram of type column after modifying de Y axe font size no column are visible in the diagram. this files also crash openoffice 4.1.6 when you try to open it. Steps to Reproduce: 1. create a diagram of three raw of two line 2. keep first choice for diagram type in french version "colonne" 3. choice data in line and label in first raw 4 after accept modify size of font use in Y axe 5 save ods 6 close libeoffice and re-open the file Actual Results: no column in the diagram windows Expected Results: visible column like before recording Reproducible: Always User Profile Reset: No Additional Info: a workaround that correct this behavior is change temporary the type to XY; column rise and save file work after that
Created attachment 147677 [details] a bogus ods produce by libo6.1.3.2(x64)
I can't reproduce it in Version: 6.3.0.0.alpha0+ Build ID: 6287a4f0d18df7f195d1f14b7c24536317463a23 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 Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Sorry, i dont find this version for windows. I dont know if this behavior exist on linux.
(In reply to MARMONT Fabrice from comment #3) > Sorry, i dont find this version for windows. I dont know if this behavior > exist on linux. Hello, you can download windows dev version here: http://dev-builds.libreoffice.org/daily/master/
Created attachment 150471 [details] capture from reopen file with alpha version bug very few different, not empty but just a line
I cannot reproduce with Version: 6.3.0.0.alpha0+ Build ID: 1ae5ca077119982ae83833871326c86d9930ae11 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; and Version: 6.3.0.0.alpha0+ (x64) Build ID: 3083fe569f96bf0289da1e9d0ef7da15ab22e2f6 CPU threads: 1; OS: Windows 10.0; UI render: default; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2019-04-16_03:05:57
To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and re-test? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present
Dear MARMONT Fabrice, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear MARMONT Fabrice, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp