Bug 123271 - Impress SLIDESHOW display totally corrupt on UHD monitors
Summary: Impress SLIDESHOW display totally corrupt on UHD monitors
Status: RESOLVED DUPLICATE of bug 40534
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
6.2.2.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: HiDPI Slide-Show
  Show dependency treegraph
 
Reported: 2019-02-08 18:04 UTC by Richard
Modified: 2019-05-01 14:17 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Richard 2019-02-08 18:04:41 UTC
Description:
Main screen is a lot of white blocks when in presentation SLIDESHOW mode.  Seems to be on high-resolution monitors such as 4 k (3840 x 2160).

Steps to Reproduce:
1.Windows 10 PC with UHD/4K monitor
2.Open Impress
3. New Document
4. Press F5

Actual Results:
Main slideshow display massive white blocks, totally useable.
Preview screen fine (if two monitors).

Expected Results:
Slideshow


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
Tried on multiple PCs.  Works fine with std resolution monitors.
Comment 1 Xisco Faulí 2019-04-16 08:39:56 UTC
Does it work if you disable OpenGl ? -> https://wiki.documentfoundation.org/OpenGL

I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the issue is still present
Comment 2 Richard 2019-04-17 22:04:53 UTC
My LibreOffice was already running with OpenGL disabled and showed this problem.  I enabled OpenGL and confirmed it still occurred, which it did.
However, while in the Options--View menu, I noticed the 'Use Hardware Acceleration' checkbox (which was ticked).  When I disabled this, the problem disappears. I confirmed this works with and without OpenGL enabled.

So the problem relates to HW accel rather than OpenGL.
Comment 3 Timur 2019-05-01 14:17:08 UTC
I'll guess mark as a duplicate of (awfully long not-resolved) Bug 40534. 
If you think it's different, feel free to explain and set back to Unconfirmed.

*** This bug has been marked as a duplicate of bug 40534 ***