Bug 101341 - FILESAVE: Slide transparency from PPTX not exported to <style:drawing-page-properties>
Summary: FILESAVE: Slide transparency from PPTX not exported to <style:drawing-page-pr...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
Keywords: filter:odp
Depends on:
Blocks: ODF-import
  Show dependency treegraph
Reported: 2016-08-05 19:06 UTC by Yousuf Philips (jay) (retired)
Modified: 2018-05-03 02:42 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

sample (30.96 KB, application/wps-office.pptx)
2016-08-05 19:06 UTC, Yousuf Philips (jay) (retired)

Note You need to log in before you can comment on or make changes to this bug.
Description Yousuf Philips (jay) (retired) 2016-08-05 19:06:39 UTC
Created attachment 126620 [details]

1) Open sample doc
2) Notice that background is grey though the background color is set to black
3) Save as an odp and reopen file
4) Background is now black

Build ID: 8da4ba9be2d2deb8990f40fa0cc5d6b16d525c72
CPU Threads: 2; OS Version: Linux 3.19; UI Render: default; 
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2016-08-03_23:43:46
Locale: en-US (en_US.UTF-8); Calc: group
Comment 1 Cor Nouws 2016-08-05 19:36:09 UTC
can confirm this
Comment 2 Yousuf Philips (jay) (retired) 2017-05-02 14:32:40 UTC
@Xisco: The file wasnt created with WPS, the stupid upload mime-type checker must have put that instead of the correct ms word docx mime-type.
Comment 3 QA Administrators 2018-05-03 02:42:10 UTC
** Please read this message in its entirety before responding **

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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team