Bug 133549 - Another incorrect rendering of an SVG image - parts of image are not shown
Summary: Another incorrect rendering of an SVG image - parts of image are not shown
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: filters and storage (show other bugs)
Version:
(earliest affected)
4.4 all versions
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:svg
Depends on:
Blocks: SVG-Import
  Show dependency treegraph
 
Reported: 2020-05-31 10:17 UTC by Callegar
Modified: 2025-10-30 03:13 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Test svg image (5.29 KB, image/svg+xml-compressed)
2020-05-31 10:18 UTC, Callegar
Details
Comparison Inkscape and LibreOffice 7.1 master (627.37 KB, image/png)
2020-07-02 09:31 UTC, Xisco Faulí
Details
minimal sample (344 bytes, image/svg+xml)
2022-09-21 09:54 UTC, Xisco Faulí
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Callegar 2020-05-31 10:17:52 UTC
Description:
Some parts of an SVG image are not shown.

Steps to Reproduce:
1. Try to insert attached image in a draw document


Actual Results:
See that numbers from 10 to 31 surrounding the image are shown, but numbers from 0 to 9 are not.

Expected Results:
All numbers from 0 to 31 should be shown


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 6.4.4.2
Build ID: 3d775be2011f3886db32dfd395a6a6d1ca2630ff
CPU threads: 8; OS: Linux 5.4; UI render: GL; VCL: kf5; 
Locale: it-IT (en_US.UTF-8); UI-Language: en-US
Calc: threaded
Comment 1 Callegar 2020-05-31 10:18:39 UTC
Created attachment 161454 [details]
Test svg image
Comment 2 ian 2020-05-31 16:19:52 UTC
Thanks for reporting the bug.

This bug sounds similar to 133020.

I can reproduce it in:

Version: 6.4.4.2 (x64)
Build ID: 3d775be2011f3886db32dfd395a6a6d1ca2630ff
CPU threads: 2; OS: Windows 10.0 Build 17763; UI render: default; VCL: win; 
Locale: en-US (en_US); UI-Language: en-US
Calc: CL

And I also can reproduce it in:

Version: 7.1.0.0.alpha0+ (x64)
Build ID: 83c4f86f22dc37269ac6a038fe7de053c42aad6e
CPU threads: 2; OS: Windows 10.0 Build 17763; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded
Comment 3 Xisco Faulí 2020-07-02 09:31:21 UTC
Created attachment 162587 [details]
Comparison Inkscape and LibreOffice 7.1 master
Comment 4 Xisco Faulí 2020-07-02 09:35:41 UTC
Reproduced in

Version: 7.1.0.0.alpha0+
Build ID: 7df1884118a0d995ec57679ef83e586c95063858
CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

Version: 5.2.0.0.alpha0+
Build ID: 3ca42d8d51174010d5e8a32b96e9b4c0b3730a53
Threads 4; Ver: 4.19; Render: default; 

and

Version: 4.3.0.0.alpha1+
Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e
Comment 5 QA Administrators 2022-07-03 03:30:40 UTC Comment hidden (obsolete)
Comment 6 Callegar 2022-07-03 11:09:03 UTC
Bug still present as of 7.3.4.2
Comment 7 Xisco Faulí 2022-09-05 20:04:37 UTC
In LibreOffice 7.5 master, the svgz file can't be open due to bug 150808
Comment 8 Xisco Faulí 2022-09-21 08:10:37 UTC
Still reproducible in

Version: 7.5.0.0.alpha0+ / LibreOffice Community
Build ID: 90861cc6f815b3f34edb88d47afed0d1099e72e7
CPU threads: 8; OS: Linux 5.10; UI render: default; VCL: gtk3
Locale: es-ES (es_ES.UTF-8); UI: en-US
Calc: threaded
Comment 9 Xisco Faulí 2022-09-21 08:15:34 UTC
this is interesting, if one of the non visible numbers ( e.g. 9 ) is changed to 99, then it's visible...
Comment 10 Xisco Faulí 2022-09-21 09:54:27 UTC
Created attachment 182593 [details]
minimal sample
Comment 11 BogdanB 2023-10-30 15:59:38 UTC
X (from demo file from comment 10) is duplicated, and numbers from 1-9 are not visible (with the file from comment 1).
Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: b7d2a9c824aca1a4dfd1b857a3620e73ade6bc0d
CPU threads: 16; OS: Linux 6.2; UI render: default; VCL: gtk3
Locale: ro-RO (ro_RO.UTF-8); UI: en-US
Calc: threaded
Comment 12 QA Administrators 2025-10-30 03:13:00 UTC
Dear Callegar,

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