The slide is flickering once when after the fade animation ends
Steps to Reproduce:
1. open attachment 148255 [details]
Screen flickering after the animation ends
User Profile Reset: No
Build ID: 61778fd20395794d2de3b52d60dcc65083aecd93
CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win;
Locale: nl-NL (nl_NL); UI-Language: en-US
I have the same problem on 126.96.36.199 release. It is really annoying and renders Impress unusable for me.
I have two displays if this information would help: 1280x1024 and 1680x1050.
I can't reproduce it in
Build ID: 7c7a4675ad5d61add70dd073f680ea37012962ce
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3;
Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US
Id. de compilación: fcd633fb1bf21b0a99c9acb3ad6e526437947b01
Subprocs. CPU: 1; SO: Windows 6.1; Repres. IU: predet.; VCL: win;
Configuración regional: es-ES (es_ES); Idioma de IU: es-ES
Could you please try to reproduce it with a master build from http://dev-builds.libreoffice.org/daily/master/ ?
You can install it alongside the standard version.
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the master build
Confirmed, and bibisected to the same commit as bug 124709 (the cause of the problem is likely somewhere else). Only occurs with OpenGL enabled. Also seems similar to bug 99685 (but I couldn't repro that in Windows).
author Mike Kaganski <firstname.lastname@example.org> 2019-02-17 16:30:55 +0300
committer Mike Kaganski <email@example.com> 2019-02-18 09:28:19 +0100
tdf#98896: GetWidth/GetHeight vs getWidth/getHeight strikes back!
(In reply to Aron Budea from comment #3)
> Only occurs with OpenGL enabled.
seems to contradict with
(from comment #0)
> Additional Info:
> UI render: default
(In reply to Mike Kaganski from comment #4)
> (In reply to Aron Budea from comment #3)
> > Only occurs with OpenGL enabled.
> seems to contradict with
I made two mistakes...
1. It does occur with default rendering (the transitions are drawn using OpenGL regardless).
2. The offending commit is from after the report. :)
Anyway, now the bug is 100% there.
*** Bug 137285 has been marked as a duplicate of this bug. ***