Bug 126023 - Breaking an SVG image destroys objects
Summary: Breaking an SVG image destroys objects
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
Version:
(earliest affected)
4.1.6.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:svg
Depends on:
Blocks: Draw-Images
  Show dependency treegraph
 
Reported: 2019-06-20 13:28 UTC by etienne.jussiau
Modified: 2025-11-03 03:12 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Draw document with SVG image inside (85.27 KB, application/vnd.oasis.opendocument.graphics)
2019-06-25 08:42 UTC, etienne.jussiau
Details
Sample document after breaking the image (18.65 KB, application/vnd.oasis.opendocument.graphics)
2019-06-25 08:42 UTC, etienne.jussiau
Details
Some variations of a small svg file to study expected and broken behaviour of "break" feature (43.14 KB, application/vnd.oasis.opendocument.graphics)
2020-01-29 21:08 UTC, Christina Rossmanith
Details

Note You need to log in before you can comment on or make changes to this bug.
Description etienne.jussiau 2019-06-20 13:28:21 UTC
Description:
I am using LibreOffice Draw to customize SVG images, usually scientific plots. I was using the "Break" command to separate the different elements of the image which could then be modified individually. It used to work like a charm with LibreOffice 5 but I recently updated to version 6.2.4 and this feature is now quite buggy. When using "Break" on an SVG image, some parts of the image are deleted.

I have tested this for different versions of LibreOffice and this problem seems to come with version 6. I have also tested this issue with several computers (MacOS and Linux) but this does not solve the problem.

Steps to Reproduce:
1.Open an SVG file with LibreOffice
2.Choose "Shape-Break"
3.

Actual Results:
Some parts of the image have been deleted

Expected Results:
"Break" should only have separated the different elements of the file from one another


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 Alex Thurgood 2019-06-25 07:05:21 UTC
@Etienne : would you have a sample Draw document with an SVG image in it that we could try and reproduce this behaviour with ?

Does the problem occur with all SVGs, or only some (particular) images ?
Comment 2 etienne.jussiau 2019-06-25 08:41:29 UTC
(In reply to Alex Thurgood from comment #1)
> @Etienne : would you have a sample Draw document with an SVG image in it
> that we could try and reproduce this behaviour with ?
> 
> Does the problem occur with all SVGs, or only some (particular) images ?

Hi Alex, thank you for your answer. I added an example as an attachment. In this example, you have an SVG image of a plot. When I break the image on my computer (see other attachment), the frame of the plot partly dissapears.

This problem has occurred with all SVGs that I have tried so far. It seems however that it is mostly thin lines which are erased.
Comment 3 etienne.jussiau 2019-06-25 08:42:19 UTC
Created attachment 152379 [details]
Draw document with SVG image inside
Comment 4 etienne.jussiau 2019-06-25 08:42:47 UTC
Created attachment 152380 [details]
Sample document after breaking the image
Comment 5 Alex Thurgood 2019-06-25 09:18:23 UTC
Thanks Etienne.


Confirming with

Version: 6.4.0.0.alpha0+
Build ID: eda0568ec550a10b962c2427edfe05ea3197f107
CPU threads: 4; OS: Mac OS X 10.14.5; UI render: default; VCL: osx; 
Locale: fr-FR (fr_FR.UTF-8); UI-Language: en-US
Calc: threaded
Comment 6 Alex Thurgood 2019-06-25 09:32:30 UTC
I can confirm that this is broken at least all the way back to LO4.1.x, don't currently have anything older with which to test.
Comment 7 eisa01 2019-08-31 12:46:21 UTC
Setting OS to all, as reported happening on Linux too, and replicated on Windows as well
Comment 8 Christina Rossmanith 2020-01-29 21:07:20 UTC
I've created a draw document with variations of a small svg file. Some of them break as expected some of them don't.

The svg file contains a blue line without and a red line with a clip path. 

- red line without clip path first -> expected behaviour
- clip path intersects blue line -> expected behaviour
- cropping the inserted image works like a work around -> expected behaviour

- clip path && bounding box of red line touch blue line -> buggy
Comment 9 Christina Rossmanith 2020-01-29 21:08:13 UTC
Created attachment 157512 [details]
Some variations of a small svg file to study expected and broken behaviour of "break" feature
Comment 10 QA Administrators 2022-01-29 03:54:27 UTC Comment hidden (obsolete)
Comment 11 eisa01 2022-02-05 13:09:22 UTC
Still present

Version: 7.4.0.0.alpha0+ / LibreOffice Community
Build ID: 583185235389b55d6cfffac3067c0e1ccb2852b1
CPU threads: 10; OS: Mac OS X 10.16; UI render: Skia/Raster; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded
Comment 12 BogdanB 2023-11-03 15:05:12 UTC
Also in Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 2f2803a77af3bfdab979bd44ce61866e6985d172
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 13 QA Administrators 2025-11-03 03:12:13 UTC
Dear etienne.jussiau,

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