Created attachment 58482 [details] Demonstration of the fade in and out rendering In the attached sample file there are two transparent rectangles in front of other object. The rendering of the fade in and out of those rectangles is incorrect. This was already a bug in some versions of OOo, but it still had worked correctly in LO 3.3.4. For fade in, the rectangle should be invisible at first and then slightly cover the background object until reaching its final state with correct transparency. Instead, the rectangle goes to the opaque state - hiding the background totally - and then suddenly assumes the correct transparency. For fade out, this wrong behavior proceeds in reverse order. Since LO3.5.1rc2 has a general rendering bug while using hardware acceleration, I switched this feature off for this demo. My system is Windows Vista, but I think the same problem will be present in other OS.
Thanks for bugreport reproduced in 3.5.4 on Fedora 64 bit (Windows not tested) reproducible if Tools->Options->LO->View->"Use hardware acceleration" disabled
not reproducible with LO 4.0.2.2 (Win7 Home, 64bit) I would say this issue was resolved in the meantime. Can anybody confirm this? If yes, then I would propose to close this issue.
reproduced in 4.0.2 on Fedora (RFR) 64 bit the same as described in comment 1 (if hardware acceleration enabled, then looks correctly)
@Sasha: confirmed, if I disable the hardware acceleration then this buggy behavior is reproducible, with enabled hardware acceleration it is not reproducible
confirmed with LO 3.6.6.2 (ubuntu 12.04.2 32bit), disabling hardware acceleration will make background blinking/hiding a second
From what I can see this is now fixed, tested in 4.1.2.2 release on Ubuntu 13.04. Closing as WFM If someone can confirm that this is still a problem in 4.1 or 4.2 please set to UNCONFIRMED again until we can get independent confirmation that it's still an issue. Also removing bibisectrequest as it's not needed (if my test is correct and it's indeed fixed). I disabled hardware acceleration, opened presentation and saw the fade in for the rectangle.
in 4.1.2 on Fedora 64 bit Intel video: acceleration disabled: after first click rectangles smoothly becomes yellow and image smoothly disappears. Then appears again. acceleration enabled: after first click rectangles smoothly becomes yellow but without disappearing of images.
The bug still exists in LO 4.1.1.2 (LO 32bit, Windows 7 64bit) as described originally with hardware acceleration disabled. It works with hardware acceleration enabled.
Now I have found time to test also with LO 4.1.2.3 (32 Bit) Build ID: 40b2d7fde7e8d2d7bc5a449dc65df4d08a7dd38 on Win 7, 64 Bit. As described also by Sasha, the bug still exists. There is a fading effect of the rectangle, but it goes wrong: The fade in doesn't stop at the correct opacity of the rectangle, but runs to 100% opaque covering the underlying image totally, then suddenly returns to the right opacity. Fade out behaves reverse. Only with hardware acceleration enabled it works fine.
(In reply to comment #7) > in 4.1.2 on Fedora 64 bit Intel video: > acceleration disabled: after first click rectangles smoothly becomes yellow > and image smoothly disappears. Then appears again. > acceleration enabled: after first click rectangles smoothly becomes yellow > but without disappearing of images. CONFIRMED on Version: 4.2.0.0.beta1 + Ubuntu 12.04.3 Status -> NEW
Not bibisectable
I can reproduce this on OSX in LO 3.3.0.4. While it seems there are some rendering paths which don't show the issue (hardware acceleration on Windows?), the essential bug appears to be inherited from OOo and not a regression -> Removing Keywords: regression -> Setting Version: Inherited from OOo
(In reply to Matthew Francis from comment #12) > I can reproduce this on OSX in LO 3.3.0.4. While it seems there are some > rendering paths which don't show the issue (hardware acceleration on > Windows?) Yes, with hardware acceleration activated it works on Windows (Win 7 64bit for LO4.4.6 and LO5.02).
Bug still exists in Libreoffice 5.3.0 alpha. I think the slide transition and animations have the same problem. i.e. re-showing what's underneath for a split second. I think it's related to these: https://bugs.documentfoundation.org/show_bug.cgi?id=73273 https://bugs.documentfoundation.org/show_bug.cgi?id=95479
Repro (I'm looking at some anim stuff). Arch Linux 64-bit, KDE Plasma 5 Version: 5.5.0.0.alpha0+ Build ID: c855400e9686ddd8bcba5691393f839f6f52c966 CPU threads: 8; OS: Linux 4.11; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on June 2nd 2017
A basic slide show isn't cpu heavy. A basic fade in should work fine even if there is no OpenGL/Hardware acceleration. For me, none of these problems go away if I disable hardware rendering and/or OpenGL rendering. Second, my laptop has an Intel i7-2620m cpu. Using the integrated Intel graphics I see all the glitches regardless of OpenGL/Hardware settings. My laptop also has an NVIDIA QUADRO NVS 4200M. If I switch over to the Nvidia card Libreoffice slide transitions like fade-in look fine. ??? For devs who can't reproduce the problem please test under VirtualBox. I use Lubuntu 16.04.1 with the VirtualBox guest additions (not the ubuntu included guest additions). All the problems show up here with newer versions of LibreOffice.
** 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 MassPing-UntouchedBug
Tested with Version: 6.1.0.0.beta1 Build-ID: 8c76dfe1284e211954c30f219b3a38dcdd82f8a0 CPU-Threads: 4; BS: Windows 6.1; UI-Render: Standard; Gebietsschema: de-DE (de_DE); Calc: CL
Changed Status to Resolved Worksforme
(In reply to bellgardt from comment #19) > Changed Status to Resolved Worksforme Nah, I still repro with HW accel disabled. Arch Linux 64-bit Version: 6.2.0.0.alpha0+ Build ID: 8447d31e529985ef7fc71933f0e55685530f9fc9 CPU threads: 8; OS: Linux 4.16; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group threaded Built on June 14th 2018
*** Bug 119513 has been marked as a duplicate of this bug. ***
Dear bellgardt, 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 MassPing-UntouchedBug
Still reproducible with: Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu3 CPU threads: 12; OS: Linux 5.4; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded on Ubuntu 20.04
This is still a bug on Win10 x64 using the current stable version 7.0.5 and beta version 7.1.1. This means, the fade-in goes to fully opaque state before instantly switching to the specified translucent state. On fade-out, the inverse happens, meaning it instantly switches to fully opaque from the specified translucent state, after which it animates the fade out. Any ideas how to overcome this problem?
Dear bellgardt, 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