Bug 135095 - SLIDESHOW Blank screen not working in Impress presenter console with dual monitors
Summary: SLIDESHOW Blank screen not working in Impress presenter console with dual mon...
Status: RESOLVED DUPLICATE of bug 112179
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
6.4.4.2 release
Hardware: x86-64 (AMD64) macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-07-24 11:22 UTC by Robert
Modified: 2020-07-25 11:15 UTC (History)
0 users

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 Robert 2020-07-24 11:22:07 UTC
Description:
I have a setup with a MacBook connected to an external display. When I start the presentation, the presenter console comes up in one screen and the presentation inherent other. I can navigate the presentation with the keyboard.

One of the features is to black or white the screen with b/. or w/, keys. 

Unfortunately this doesn't work with the presenter console. The application doesn't respond to the keys. 

As soon as I disconnect the external monitor and enter regular presentation mode, I can use all 4 keys to black or white out the screen.

So the bug enters when using and external monitor. 

Steps to Reproduce:
1. Hit F5 key
2. Hit B key
3.

Actual Results:
Screen not black

Expected Results:
Black out screen


Reproducible: Always


User Profile Reset: Yes



Additional Info:
N/a
Comment 1 Robert 2020-07-24 15:12:20 UTC
Version: 6.4.4.2
Build ID: 3d775be2011f3886db32dfd395a6a6d1ca2630ff
CPU threads: 4; OS: Mac OS X 10.15.5; UI render: default; VCL: osx; 
Locale: nl-NL (nl.UTF-8); UI-Language: en-US
Calc: threaded
Comment 2 Andrew Watson 2020-07-25 11:15:18 UTC
Many thanks for flagging this.

This bug has been previously reported as Bug 112179, so setting status of this report to RESOLVED DUPLICATE of that one.

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