Bug 127848 - Chart object not visible on Linux
Summary: Chart object not visible on Linux
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.2.0.4 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:docx
Depends on:
Blocks: Chart
  Show dependency treegraph
 
Reported: 2019-09-28 17:02 UTC by raal
Modified: 2022-09-20 03:33 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments
Linux printscreen (51.17 KB, image/png)
2019-09-28 17:03 UTC, raal
Details
windows printscreen (24.04 KB, image/png)
2019-09-28 17:04 UTC, raal
Details

Note You need to log in before you can comment on or make changes to this bug.
Description raal 2019-09-28 17:02:58 UTC
Description:
Chart is not visible in Linux (only rectangle Object3), but is visible in windows. Tested LO 6.3 on windows and LO 6.4 on Linux


Version: 4.2.0.0.alpha1+
Build ID: 24857c46daf06553e8618de46a0f3ece27c32675
chart in not visible at all in 4.1

Steps to Reproduce:
1.open file http://bugs.documentfoundation.org/attachment.cgi?id=154586


Actual Results:
chart is not visible - only rectangle Object3

Expected Results:
chart visible


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 raal 2019-09-28 17:03:43 UTC
Created attachment 154621 [details]
Linux printscreen
Comment 2 raal 2019-09-28 17:04:07 UTC
Created attachment 154622 [details]
windows printscreen
Comment 3 raal 2019-09-28 17:21:48 UTC
(In reply to raal from comment #0)
> Version: 4.2.0.0.alpha1+
> Build ID: 24857c46daf06553e8618de46a0f3ece27c32675
> chart in not visible at all in 4.1
> 

Bisected with bibisect-42max

There are only 'skip'ped commits left to test.
The first bad commit could be any of: 35376f5b116d8ad9a8b529b69ff162278068eff1 7364ed6560fc15ffee4cc4577b032082c8e5d403 29182f1de15b8ec171cb01453de003fc2922275c 77bfa60cd252d799170ef53bd5e9fe12c1bd5f0a b5dab36fec9a113aee74ece465a99f80cceb35b9 fe11b420e510bae06026518c6fe4d84dd55a690a 212681877aece9a0a51f7dfc6eb2290c1470da32 949aaddabacc7b87200b54adcf6db633b5de3e84 36ec00968dd129924662b9440158db226244da6f 5bad49da63d11d71bd5ad65d0c633d8fd784c745 12d76f763ca4be747a0d34bbcc49bf20c2134c55 5b902eab97f6952d3cf5ec7af8dd68f015883814 d14f793f0b1170d3a402f0fac3326a758819e772 efeb41a4ac3572a3d2225187389fa53bdd962382 1d3143df56aeafa1222c6622204ff7297294f139 f434f9bf0a4369f8bf58e141ec05363a64c59b3d 23f97438735467fe59ae3d8d5e5dee7a0bf490f1 a4a6f0716f8253a0917e66a38b5b19c54ddb0fa5 2ed0bef168c87fe43a78a482742132311ff00c36 d3f48434efd17583564389f708c47227ef2b8800 376adc78128491d1c9b9030f60ea3ed9bdd2dd73 d8f6a662c18b4bcf56090340ec73705bad3bd98a 737d3c598ae107781727e8e4d5535a5750a1c494 f729fedbc34c7b2a7bade2568ab9de3a201998e9 3151d154d095074f34b714b5a095ece20d966ec2 d09b67a09b0c89870e1a081dc08542bdae2808a4 97be576368211a784d3c6d14740c4958bda364d2 98adad8cb81677ddd6da1dd0eebce340913714f3 097399947a8097a15c320b6d1555d1037e2ce29b 7d81bf89ebdfebed13a45d5a3a0da6d52ee37c9d a071978f128cbbd6f08c10626225c923cf23b8b9
We cannot bisect more!

This commit looks suspicious. Adding cc to Vinaya Mandke and Miklos Vajna

commit 097399947a8097a15c320b6d1555d1037e2ce29b (tag: source-hash-13e8e9e2fe32bc
77058b5869c39948b683fb81ec, refs/bisect/skip-097399947a8097a15c320b6d1555d1037e2
ce29b)
Author: Matthew Francis <mjay.francis@gmail.com>
Date:   Sat Sep 5 21:17:28 2015 +0800

    source-hash-13e8e9e2fe32bc77058b5869c39948b683fb81ec
    
    commit 13e8e9e2fe32bc77058b5869c39948b683fb81ec
    Author:     Vinaya Mandke <vinaya.mandke@synerzip.com>
    AuthorDate: Tue Sep 17 18:54:21 2013 +0530
    Commit:     Miklos Vajna <vmiklos@collabora.co.uk>
    CommitDate: Fri Sep 20 10:06:05 2013 +0200
    
        fdo#40594 Fix for chart missing issue in Writer (for docx)
    
        1. Enabled parsing of chart in writer module.
        2. While parsing chart is read as ole2shape. Then converted into TextEmb
edded object for chart.
        3. While exporting postponed chart writing after rpr tag.
        4. Generated unique id for each chart.
        5. Corrected content type of chart in export.
        Change-Id: I6a1ca0c34e03e17cc3dd8a183580132ea7af5c48
        Reviewed-on: https://gerrit.libreoffice.org/5976
        Reviewed-by: Miklos Vajna <vmiklos@collabora.co.uk>
Comment 4 Peter Thomson 2019-10-02 03:56:34 UTC Comment hidden (spam)
Comment 5 Durgapriyanka 2019-10-04 17:12:18 UTC
Thank you for reporting the bug. 

I can reproduce the bug in
LibreOffice 3.3.0 
OOO330m19 (Build:6)
tag libreoffice-3.3.0.4 , The chart doesn't appear.


But, I cannot reproduce it in
Version: 6.3.0.0.alpha0+, 
Build ID: b6b28931435e44aca92b8c0e1659f701e3ed1a87
CPU threads: 2; OS: Windows 6.1; UI render: default; VCL: win; 
TinderBox: Win-x86@42, Branch:master, Time: 2019-01-30_06:57:04
Locale: en-US (en_US); UI-Language: en-US
Calc: threaded , the chart does appear.
Comment 6 Timur 2019-10-07 14:02:03 UTC
Repro LO 6.4+ in Linux Mint.
Comment 7 BogdanB 2020-09-19 20:27:19 UTC
Repro in
Version: 7.0.1.2
Build ID: 7cbcfc562f6eb6708b5ff7d7397325de9e764452
CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3
Locale: en-US (ro_RO.UTF-8); UI: en-US
Calc: threaded
Comment 8 QA Administrators 2022-09-20 03:33:32 UTC
Dear raal,

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