Bug 98229 - F5 Full screen not Displaying slides in UHD screen (3840x2160)
Summary: F5 Full screen not Displaying slides in UHD screen (3840x2160)
Status: RESOLVED DUPLICATE of bug 40534
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
5.0.5.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-27 14:23 UTC by Michka1111
Modified: 2016-03-09 08:21 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
What is shown after F5 press (644.77 KB, image/png)
2016-02-27 14:23 UTC, Michka1111 		Details
Impress Window with W10 Display's resolution in the bottom (4.09 MB, image/png)
2016-02-27 14:25 UTC, Michka1111 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michka1111 2016-02-27 14:23:08 UTC 
Created attachment 123037 [details]
What is shown after F5 press

When I press F5 to display the presentation in full screen,
the slide is not displayed, but in each corner of the screen,
tne bottom of the slide is being seen.
The presentation is made with LibreOffice 5.0.4 Impress and nox displayed with 5.0.5.
The presentation is correctly seeing on another computer 1900x1200.

Screen display is ACER K242HQK.
Windows 10 64b displaying at 3840x2160 @60Hz / Display Port
CPU Intel Core i5-5675C with IGP Intel Iris Pro Graphics 6200
Screen driver up to date v20.19.15.4331
15.799MB RAM
Please see the sceenshots

PS I found a turnaround by exporting to pdf and display in full screen read mode with Acrobat DC ;-)
Comment 1 Michka1111 2016-02-27 14:25:36 UTC 
Created attachment 123038 [details]
Impress Window with W10 Display's resolution in the bottom
Comment 2 Buovjaga 2016-03-09 08:21:45 UTC 
Seems the same as bug 40534. Comments there say that dual screen is not a requirement for the bug - a large screen is enough.

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