Bug 1633168 - Colours of Imported SVG into Libreoffice Writer are replaced with black
Summary: Colours of Imported SVG into Libreoffice Writer are replaced with black
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: libreoffice
Version: 28
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-26 10:41 UTC by Aznar
Modified: 2019-05-28 22:35 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-05-28 22:35:34 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Example of an SVG files with the problem (482.21 KB, image/svg+xml)
2018-09-26 10:41 UTC, Aznar
no flags Details
Example of an SVG file created with matplotlib without the issue (34.34 KB, image/svg+xml)
2018-09-26 10:42 UTC, Aznar
no flags Details

Description Aznar 2018-09-26 10:41:40 UTC
Created attachment 1487192 [details]
Example of an SVG files with the problem

Description of problem:

When I import some SVG that I created with matplotlib in Libreoffice Writer, some colours are replaced with black.

Version-Release number of selected component (if applicable):
Libreoffice : Version: 6.0.6.2
Build ID: 6.0.6.2-1.fc28
matplotlib : python3-matplotlib
Version      : 2.2.3
Révision     : 1.fc28


How reproducible:
every time

Steps to Reproduce:
1. create an SVG with matplotlib
2. Import the SVG produced with matplotlib
3.

Actual results:

The colours are not displayed properly but replaced with black.

Expected results:

Having colours in the SVG instead of black

Additional info:
Some SVG imported to Libreoffice do not have this issue, the colours are being  displayed (see next attachment).

Comment 1 Aznar 2018-09-26 10:42:27 UTC
Created attachment 1487193 [details]
Example of an SVG file created with matplotlib without the issue

Comment 2 Ben Cotton 2019-05-02 19:18:33 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Ben Cotton 2019-05-02 20:50:15 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Ben Cotton 2019-05-28 22:35:34 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.