Description: Every time I open a document containing a chart, I have to manually reselect the chart type to correct the format. I've only observed this with the Column–Normal chart. It's been happening through many revisions of LibreOffice. If I don't reformat, it will also print wrong. Steps to Reproduce: 1. Create a Column chart, type of Normal with at least 3 data points. (number untested) Observe layout of the chart looking specifically at the beginning and end data points. 2. Save and close the document. 3. Reopen the document and examine the first and last data points now "bleed" beyond the edge of the chart. This is more severely apparent when multiple data sets are used. Actual Results: The first and last data points now appear slightly beyond the edge of the chart. When using multiple data sets, it's possible that some of those data points will not be visible at the beginning or end of the chart. Expected Results: The first and last data points should display wholly within the chart, as it does when first created. Reproducible: Always User Profile Reset: Yes Additional Info: This has been happening since at least version 6, and I've also tried using the versions through 7.1.4. The only fix I know of is reselecting the chart and rechoose the chart type to force a reformat. This "fix" does not hold; once the document is closed and reopened, the chart will be misformatted again. Version: 7.0.6.2 (x64) Build ID: 144abb84a525d8e30c9dbbefa69cbbf2d8d4ae3b CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL
Please attach a sample file.
Created attachment 173355 [details] test data and chart as requested Although two charts are present, the chart of concern is the uppermost column type chart.
The column chart seems fine upon opening. I also recreated it and after reloading it looks the same. I do get this when trying to update links: The following external file could not be loaded. Data linked from this file did not get updated. file:///MEGA/2021 Blue Petunia Store Sales Reports.xls Maybe you could attach a screenshot about the problem. Can you still reproduce with a fresh version? Arch Linux 64-bit Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: e5fb120a32d04e241b35a7e63894c744196f576b CPU threads: 8; OS: Linux 5.17; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Jumbo Built on 10 May 2022
A similar-sounding bug was fixed some time ago: bug 136111
Dear Todd, 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 Todd, 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