Bug 123223

Summary: Gradient fill not correct when .pptx file
Product: LibreOffice Reporter: Christopher POTTER <cpotter>
Component: ImpressAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: libreoffice, xiscofauli
Priority: medium Keywords: filter:pptx
Version: 4.1 all versions   
Hardware: All   
OS: All   
See Also: https://bugs.documentfoundation.org/show_bug.cgi?id=72567
https://bugs.documentfoundation.org/show_bug.cgi?id=49920
https://bugs.documentfoundation.org/show_bug.cgi?id=154858
Whiteboard:
Crash report or crash signature: Regression By:
Bug Depends on:    
Bug Blocks: 108226, 114005    
Attachments: Fill circle form incorrect when importing Powerpoint file

Description Christopher POTTER 2019-02-07 10:38:02 UTC
Description:
When you visualise a form (circle, ...) with a "gradient fill" from a document create on Powerpoint (.pptx) the form does not have the correct gradient (see included file)

Steps to Reproduce:
1. Create a circle form with 2 colors gradient on Powerpoint
2. Open it with LibreOffice
3. The gradient is not the same 

Actual Results:
Wrong gradient (See attached file)

Expected Results:
Correct gradient (See attached file)


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 Christopher POTTER 2019-02-07 10:39:04 UTC
Created attachment 148976 [details]
Fill circle form incorrect when importing Powerpoint file
Comment 2 Xisco FaulĂ­ 2019-02-07 17:09:08 UTC
Reproduced in

Version: 6.3.0.0.alpha0+
Build ID: 6287a4f0d18df7f195d1f14b7c24536317463a23
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US
Calc: threaded

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

Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)
Comment 3 NISZ LibreOffice Team 2021-01-18 15:51:05 UTC
This has multi step gradient which is not supported currently.
Comment 4 NISZ LibreOffice Team 2021-01-25 11:26:27 UTC

*** This bug has been marked as a duplicate of bug 76682 ***