Bug 145737 - Scatter chart with smooth lines skipping values
Summary: Scatter chart with smooth lines skipping values
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
7.2.2.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Chart
  Show dependency treegraph
 
Reported: 2021-11-17 14:17 UTC by Rafael Lima
Modified: 2025-05-21 03:12 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Sample ODS file with examples (40.62 KB, application/vnd.oasis.opendocument.spreadsheet)
2021-11-17 14:17 UTC, Rafael Lima
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Rafael Lima 2021-11-17 14:17:31 UTC
Created attachment 176314 [details]
Sample ODS file with examples

When you create a scatter chart with smooth lines and the two first Y values are equal, then the chart skips the first value.

When the first three Y values are equal, it skips the third, leaving a gap in the line (see attached file with examples).

However, if you switch the chart to straight lines, all is ok (except for the fact that the lines are not smoothed).

Steps to reproduce:
1) Open the attached sample file
2) In tab "Example 1" the chart uses straight lines, so all is ok
3) In tab "Example 2" the chart uses smooth lines and the two first Y values are equal, so the first is skipped
4) In tab "Example 3" the chart uses smooth lines and the three first Y values are equal, so a gap appears

System info:
Version: 7.2.2.2 / LibreOffice Community
Build ID: 20(Build:2)
CPU threads: 16; OS: Linux 5.13; UI render: default; VCL: kf5 (cairo+xcb)
Locale: pt-BR (pt_BR.UTF-8); UI: en-US
Ubuntu package version: 1:7.2.2-0ubuntu0.21.10.1
Calc: threaded
Comment 1 m_a_riosv 2021-11-17 18:14:59 UTC
As you have the max value for Y to 1, seems the line it's out of the chart wall, changing the max value a bit up lets it be showed.

In any case, looks like a bug.

Reproducible
Version: 7.2.3.1 (x64) / LibreOffice Community
Build ID: 1d5dee817bde88d78dbcc0d00f88492568e131d5
CPU threads: 4; OS: Windows 10.0 Build 21390; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: en-US Calc: CL
Version: 7.3.0.0.alpha1+ (x64) / LibreOffice Community
Build ID: 742b8befecbcfc0cfab87cfcd87c83b7d8ef32ab
CPU threads: 4; OS: Windows 10.0 Build 21390; UI render: Skia/Vulkan; VCL: win
Locale: es-ES (es_ES); UI: en-US Calc: CL
Comment 2 QA Administrators 2025-05-21 03:12:05 UTC
Dear Rafael Lima,

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