https://bugs.documentfoundation.org/show_bug.cgi?id=161985
Bug ID: 161985
Summary: LibreOffice: Transparent objects in SVG being rendered
in Writer when imported
Product: LibreOffice
Version: 7.6.0.1 rc
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: bibisected, filter:svg, regression
Severity: normal
Priority: medium
Component: LibreOffice
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected], [email protected],
[email protected]
Description:
When importing to a writer document an SVG image with an transparent object
that is marked as visible, the object is rendered.
This did not happened with LibreOffice 7.5.9 and previous versions.
But it is now affects in 7.6.1+ and 24.2 releases.
Steps to Reproduce:
1. Open a new document in Writer (any release from 7.6.2 onward)
2. Select; insert > Image
3. Select the file attached to this bug report. (test-file-01.svg)
4. Open the same test file (test-file-01.svg) in inkscape to compare the
difference
Reproducible: Always
User Profile Reset: No
A bibisect of linux-64-7.6 traces this this commit:
commit 7ddad90c14d9a7422b479547e2eb15e79eef93af
Author: Jenkins Build User <[email protected]>
Date: Mon Oct 30 17:27:18 2023 +0100
source sha:f59804171e2ecb92d9ea554812f847000c17bceb
source sha:f59804171e2ecb92d9ea554812f847000c17bceb
instdir/program/libsvgiolo.so | Bin 534864 -> 534864 bytes
instdir/program/setuprc | 2 +-
instdir/program/versionrc | 2 +-
3 files changed, 2 insertions(+), 2 deletions(-)
Which corresponds to this change:
https://gerrit.libreoffice.org/c/core/+/154274
The commit hash for same patch in the master branch ( 24.2) is
56039daae4a436d7ea1b093a02cf0e8ad3bda4a9
The commit message of: https://gerrit.libreoffice.org/c/core/+/154274
mentions another change:
Partially reverts 3e0e67a152e9631574e28dacb6e06a96f03ebca2
And 3e0e67a152e9631574e28dacb6e06a96f03ebca2 commit message mentions yet
another change: Partially revert d47b37eea9779e3c354e6c19a7211a306965b7ef
Those two commits where checked by Aron Budea, and the bug was not present
before, so this is not a reemerging issue. It's a new issue.
--
You are receiving this mail because:
You are the assignee for the bug.
