Bug 128384 - FILEOPEN: XLSX: gridlines are missing in a 3d line chart
Summary: FILEOPEN: XLSX: gridlines are missing in a 3d line chart
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Chart (show other bugs)
Version:
(earliest affected)
4.4 all versions
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:xlsx
Depends on:
Blocks: OOXML-Chart xlsx-aggressive-competitors
  Show dependency treegraph
 
Reported: 2019-10-25 09:32 UTC by Xisco Faulí
Modified: 2024-11-11 03:12 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
sample file (13.06 KB, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet)
2019-10-25 09:32 UTC, Xisco Faulí
Details
comparison MSO 2010 and LibreOffice 6.4 Master (101.56 KB, image/png)
2019-10-25 09:32 UTC, Xisco Faulí
Details
Example file with changed background color (132.99 KB, image/png)
2019-11-04 10:16 UTC, NISZ LibreOffice Team
Details
The document in current master with Anti-Aliasing turned off (126.83 KB, image/png)
2020-02-03 08:10 UTC, NISZ LibreOffice Team
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Xisco Faulí 2019-10-25 09:32:01 UTC
Created attachment 155297 [details]
sample file

Steps to reproduce:
1. Open attached document

-> Chart's gridlines are missing. See comparison

Reproduced in

Version: 6.4.0.0.alpha1+
Build ID: 6c6b00300c5430466804619394b84beea01b3187
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

and

Version: 4.3.0.0.alpha1+
Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e

Previously the chart wasn't even imported correctly...
Comment 1 Xisco Faulí 2019-10-25 09:32:25 UTC
Created attachment 155298 [details]
comparison MSO 2010 and LibreOffice 6.4 Master
Comment 2 Julien Nabet 2019-10-26 21:06:56 UTC
On pc Debian x86-64 with master sources updated today, I could reproduce this.

I noticed these on console:
warn:oox:26115:26115:oox/source/docprop/docprophandler.cxx:322: OOXMLDocPropHandler::startFastElement: unknown element 5620
warn:oox:26115:26115:oox/source/docprop/docprophandler.cxx:322: OOXMLDocPropHandler::startFastElement: unknown element 3197
warn:oox:26115:26115:oox/source/docprop/docprophandler.cxx:322: OOXMLDocPropHandler::startFastElement: unknown element 5620
warn:oox:26115:26115:oox/source/docprop/docprophandler.cxx:322: OOXMLDocPropHandler::startFastElement: unknown element 2748
warn:oox:26115:26115:oox/source/docprop/docprophandler.cxx:322: OOXMLDocPropHandler::startFastElement: unknown element 3197
warn:oox:26115:26115:oox/source/docprop/docprophandler.cxx:322: OOXMLDocPropHandler::startFastElement: unknown element 3197
warn:oox:26115:26115:oox/source/docprop/docprophandler.cxx:322: OOXMLDocPropHandler::startFastElement: unknown element 3197
warn:legacy.osl:26115:26115:oox/source/helper/graphichelper.cxx:120: GraphicHelper::GraphicHelper - cannot get target frame
warn:oox:26115:26150:oox/source/helper/progressbar.cxx:67: ProgressBar::setPosition - invalid position
warn:oox:26115:26150:oox/source/helper/progressbar.cxx:67: ProgressBar::setPosition - invalid position
warn:oox:26115:26150:oox/source/helper/progressbar.cxx:67: ProgressBar::setPosition - invalid position
warn:oox:26115:26115:oox/source/drawingml/shapecontext.cxx:130: ShapeContext::onCreateContext: unhandled element: 3639
warn:oox:26115:26115:oox/source/drawingml/shapecontext.cxx:130: ShapeContext::onCreateContext: unhandled element: 1030
warn:oox:26115:26115:oox/source/drawingml/shapecontext.cxx:130: ShapeContext::onCreateContext: unhandled element: 2493
warn:svx.uno:26115:26115:svx/source/unodraw/unoshape.cxx:1625: Unknown Property: GraphicColorMode
warn:chart2:26115:26115:chart2/source/view/main/ChartView.cxx:493:  com.sun.star.lang.IndexOutOfBoundsException
warn:chart2.tools:26115:26115:chart2/source/tools/WrappedPropertySet.cxx:137: found no inner property set to map to
warn:sfx.view:26115:26115:sfx2/source/view/viewfrm.cxx:3192: SID_SIDEBAR state requested, but no task pane child window exists for this ID!
warn:sfx.view:26115:26115:sfx2/source/view/viewfrm.cxx:3192: SID_SIDEBAR state requested, but no task pane child window exists for this ID!
warn:sfx.control:26115:26115:sfx2/source/control/dispatch.cxx:1309: Childwindow slot missing: 25917
warn:sfx.control:26115:26115:sfx2/source/control/dispatch.cxx:1309: Childwindow slot missing: 25917
warn:sfx.control:26115:26115:sfx2/source/control/dispatch.cxx:1309: Childwindow slot missing: 25917
warn:sfx.control:26115:26115:sfx2/source/control/dispatch.cxx:1309: Childwindow slot missing: 25917
warn:sfx.control:26115:26115:sfx2/source/control/dispatch.cxx:1309: Childwindow slot missing: 25917
Comment 3 NISZ LibreOffice Team 2019-11-04 10:16:33 UTC
Created attachment 155498 [details]
Example file with changed background color

Looks like its there, but the line is very thin and the background color is very dark. 
If we change the background color to a lighter one the line becomes more visible.

Excel describes the line as 0.75 pt wide while Calc reports 0.7 pt.
Comment 4 NISZ LibreOffice Team 2020-02-03 08:10:05 UTC
Created attachment 157607 [details]
The document in current master with Anti-Aliasing turned off

Looks like this problem is visible when Anti-aliasing is turned on.
Turning off AA in Options - View makes the lines appear (with or without GL).

So this looks more like a drawinglayer problem than OOXML import.
Comment 5 Michael Meeks 2020-11-09 15:10:43 UTC
Dennis; would be good to have this one on your radar / back-burner =) not urgent of course.
Comment 6 QA Administrators 2022-11-10 04:02:34 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2024-11-11 03:12:57 UTC
Dear Xisco Faulí,

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