https://bugs.documentfoundation.org/show_bug.cgi?id=160680

Aron Budea <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]
                   |                            |om, [email protected]
           Keywords|                            |bibisected, bisected
           See Also|                            |https://bugs.documentfounda
                   |                            |tion.org/show_bug.cgi?id=99
                   |                            |508
            Version|24.8.0.0 alpha0+ Master     |5.2.4.2 release

--- Comment #2 from Aron Budea <[email protected]> ---
This is somewhat of a regression, because before the following commit in 5.4
(and its backports to 5.3/5.2), the GIF is shown fine, though only a quarter of
the LO window is shown (again, this is with 4K and 200% scaling).

https://cgit.freedesktop.org/libreoffice/core/commit/?id=d9a6e0023c9a192850b9db00f8120fbcc4256ec9
author          Caolán McNamara <[email protected]>    2016-11-22 15:35:16
+0000
committer       Tomaž Vajngerl <[email protected]>       2016-11-23 22:40:58
+0000

"Resolves: tdf#99508 ensure sufficient size for hidpi backing surface"


In addition, the GIF looks fine when LibreOffice is run with gen VCL plugin,
but LO crashes out after the slideshow, with the following on the console:

========

X-Error: BadDrawable (invalid Pixmap or Window parameter)
        Major opcode: 62 (X_CopyArea)
        Resource ID:  0x88006b6
        Serial No:    28385 (28385)
Unspecified Application Error

========

It's probably unrelated to the reported issue, and started between the
following commits on 5.3 (between those LO fails to start with gen VCL plugin):
https://cgit.freedesktop.org/libreoffice/core/log/?qt=range&q=5bb5463efefc4d65e3434b37618cb74a1fe2a598..36888dc9607b6ce1f98a0a7fcd1069ded091aec1

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to