Bug 115167 - SLIDESHOW Thin gap at bottom and right side of screen in slideshow
Summary: SLIDESHOW Thin gap at bottom and right side of screen in slideshow
Status: RESOLVED DUPLICATE of bug 70976
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-23 10:16 UTC by Flora Canou
Modified: 2018-02-12 18:32 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
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 Flora Canou 2018-01-23 10:16:38 UTC 
Description:
The slideshow does not cover the full screen. There appear gaps of about one-pixel-width at the bottom and the right corner of the screen. Clicking there will result in switching out of the program. 
Happens every time on Windows 10. Never on Ubuntu and Fedora. 
Happens no matter whether OpenGL is enabled or not. 
I started using LibreOffcie since 5.3.6 and then 5.4.3 and 6.0.0.2; the problem always presents. 

Steps to Reproduce:
1. Use Windows. Open Impress and play any slideshow. 

Actual Results:  
There appear gaps of about one-pixel-width at the bottom and the right corner of the screen. Clicking there will result in switching out of the program. 

Expected Results:
The slide show should cover the full screen. 


Reproducible: Always


User Profile Reset: No



Additional Info:


User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0
Comment 1 Xisco Faulí 2018-01-23 10:26:03 UTC 
switching out of the program means it crashes?
Comment 2 Flora Canou 2018-01-23 10:30:52 UTC 
(In reply to Xisco Faulí from comment #1)
> switching out of the program means it crashes?

No. I mean the program is minimalized since the area is not covered by the program.
Comment 3 Buovjaga 2018-02-12 18:32:03 UTC 

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