Bug 89190 - Text doesn't appear when another textbox has animation and hardware acceleration is enabled
Summary: Text doesn't appear when another textbox has animation and hardware accelerat...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
4.4.0.3 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-06 22:42 UTC by Chris King
Modified: 2016-02-22 16:45 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Non-animated does not show on the slide the presentation starts on. (12.91 KB, application/vnd.oasis.opendocument.presentation)
2015-02-06 22:42 UTC, Chris King
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Chris King 2015-02-06 22:42:32 UTC
Created attachment 113191 [details]
Non-animated does not show on the slide the presentation starts on.

If the slide that a presentation starts on has text in a non-animated textbox, and text in another textbox that is animated, the non-animated text does not appear.  (The text does, however, appear in the presenter's screen.  I have two monitors connected to the computer.)

Steps to reproduce:
Create a new slide.  For layout, choose "Title and Content".  Enter text into the title box and the content box.  Animate the text in the content box with the fade-in animation.  Run the presentation.

What is observed:
When the presentation starts, the slide is blank.  Pressing the space bar displays the animated text.  Pressing the space bar again (for this one-slide presentation) ends the slide show.

What is expected:
When the presentation starts, the slide should show the non-animated text.

This only happens for the slide from which a presentation starts.  I've done it with three different animations, so it probably doesn't depend on a particular animation.  
Also, the same problem occurs on switching what is animated (by animating the title, and not animating the content box).  However, in that case (the last slide of the attachment), the non-animated text appears after the animation is done.
Comment 1 Jean-Baptiste Faure 2015-02-07 18:28:59 UTC
Not reproducible for me with LibreOffice 4.4.1.0.0+ built at home under Ubuntu 14.10 x86-64.

Did you try to play with enable or disable hardware acceleration and OpenGL options in menu Tools > Options > LibreOffice > View ?

Set status to NEEDINFO, please set it back to UNCONFIRMED once you have provided requested informations.

Best regards. JBF
Comment 2 Chris King 2015-02-09 15:53:21 UTC
(In reply to Jean-Baptiste Faure from comment #1)

Since my computer has two monitors, I tried setting the monitors to "clone", so that the presenter's screen wouldn't be shown.  The bug still appears with the monitors cloned.

The bug shows up in LibreOfficeDev_4.5.0.0.alpha0_Win_x86.

The original bug report was observed with "Using hardware acceleration" and "Use anti-aliasing" checked.  On unchecking those two options, the bug is not observed, whether or not "Use OpenGL for rendering" and "Force OpenGL, are both checked or not.  The "Use anti-aliasing" option doesn't effect the results, so this bug appears to be caused by using hardware acceleration.  My graphics card adapter type is "Intel HD Graphics 2500" with 1760 MB total available graphics memory.

Not sure that anything can be done for a problem dependent on the display adapter.
Comment 3 Yingtong Li 2015-02-16 06:24:57 UTC
I have also encountered this problem on LibreOffice 4.4.0.3 (build de093506bcdc5fafd9023ee680b8c60e3e0645d7) using an integrated Intel HD Graphics graphics card. Disabling "Using hardware acceleration" solves the issue, while changing the other "View" settings has no effect.
Comment 4 Chris King 2015-02-16 20:00:37 UTC
Because the bug has been reproduced, (comment #3), I've changed the status back to new.
Comment 5 Jean-Baptiste Faure 2015-02-17 06:13:00 UTC
Updated summary.

Best regards. JBF
Comment 6 QA Administrators 2016-02-21 08:35:04 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 on a currently supported version of LibreOffice 
   (5.0.5 or 5.1.0)  https://www.libreoffice.org/download/

   If the bug is present, please leave a comment that includes the version of LibreOffice and 
   your operating system, and any changes you see in the bug behavior
 
   If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave 
   a short comment that includes your version of LibreOffice and Operating System

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)

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: http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for your help!

-- The LibreOffice QA Team This NEW Message was generated on: 2016-02-21
Comment 7 Chris King 2016-02-22 16:45:18 UTC
In LO 5.1.0, I am no longer able to reproduce this bug.