Bug 142740 - [EMF+] Path + SetClip + Brush (PathGradient) + FillRects => no shape visible
Summary: [EMF+] Path + SetClip + Brush (PathGradient) + FillRects => no shape visible
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: graphics stack (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: EMF-WMF
  Show dependency treegraph
 
Reported: 2021-06-09 16:09 UTC by Valek Filippov
Modified: 2023-06-15 03:15 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
EMF sample with EMF+ records (680 bytes, image/x-emf)
2021-06-09 16:11 UTC, Valek Filippov
Details
How it should look like (3.02 KB, image/png)
2021-06-09 16:12 UTC, Valek Filippov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Valek Filippov 2021-06-09 16:09:45 UTC
Description:
LO fails to show properly EMF+ with a gradien-filled ellipse.

Steps to Reproduce:
Open attached EMF sample.

Actual Results:
LO shows empty image.

Expected Results:
It should have gradient-filled ellipse.


Reproducible: Always


User Profile Reset: No



Additional Info:
This is an isolated and minified EMF+ part of the EMF file from tdf#34454 (tdf#141049).
While it looks very similar to tdf#142660, the root cause is different.
Comment 1 Valek Filippov 2021-06-09 16:11:26 UTC
Created attachment 172743 [details]
EMF sample with EMF+ records
Comment 2 Valek Filippov 2021-06-09 16:12:22 UTC
Created attachment 172744 [details]
How it should look like
Comment 3 Roman Kuznetsov 2021-06-14 19:26:20 UTC
confirm in

Version: 7.2.0.0.alpha1+ (x64) / LibreOffice Community
Build ID: 31ed81ea71a20ec119805f66a42f99b3f80d2dc5
CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win
Locale: ru-RU (ru_RU); UI: ru-RU
Calc: CL
Comment 4 QA Administrators 2023-06-15 03:15:10 UTC
Dear Valek Filippov,

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