Description: Hi, when exporting a slide as a PNG (Export... menu then choose png) the shadows of texts with the shadow property get rendered as transparent, not as black. No matter whether keep transparency is selected or not. Steps to Reproduce: 1. Create some slide with a huge headline 2. Turn the text shadows on for that text 3. Export as png 4. watch the png file with a file viewer capable of displaying transparency (as checkerboard pattern), e.g. eog Actual Results: Text shadows transparent Expected Results: Text shadows black (as on the presentation) Reproducible: Always User Profile Reset: No Additional Info:
Seems to be fixed in 6.1.0.1 Unfortunately I've seen the announcement of the alpha release available for testing just on the bug page _after_ submitting the bug. I would have tested it otherwise before submitting the bug.
No, not really fixed in 6.1.0.1. When not selecting "Save Transparency" in the PNG dialog, slides look good, but when selecting (whatever this is good for), shadows still become transparent.
I did many tests and first it looked like I could repro, but finally I could not. Please attach an example file, so the testing will be consistent. Arch Linux 64-bit Version: 6.2.0.0.alpha0+ Build ID: d30e76eb7854e9a4f170677719ad0ac3f92ef297 CPU threads: 8; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5; Locale: fi-FI (fi_FI.UTF-8); Calc: threaded Built on August 23rd 2018 (also tested on Win 10)
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20190321
Dear Hadmut Danisch, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp