Bug 112179 - SLIDESHOW: black-out and white-out not working properly in fullscreen presenter mode
Summary: SLIDESHOW: black-out and white-out not working properly in fullscreen present...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: x86-64 (AMD64) macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 135095 (view as bug list)
Depends on:
Blocks: Slide-Show
  Show dependency treegraph
 
Reported: 2017-09-02 15:58 UTC by Piotr Porada
Modified: 2024-03-16 03:14 UTC (History)
3 users (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 Piotr Porada 2017-09-02 15:58:29 UTC
Description:
Black-out and white-out functionalities do not work properly on macOS Sierra.

After entering fullscreen presentation mode with secondary monitor attached primary monitor shows presenter console and secondary monitor shows current slide. Black-out and white-out shortcuts do not work unless I click directly on the slide on the secondary monitor.

Problem occurs only on macOS. Tried the same version on a Windows PC and it worked correctly

Steps to Reproduce:
1. Open a slideshow with two monitors attached
2. Enter slideshow (eg. F5)
3. Press B or W key

Actual Results:  
Nothing happens unless the slide on the actual slideshow is clicked

Expected Results:
Actual slideshow is blacked-out (B key) or whited-out (W key)


Reproducible: Always

User Profile Reset: Yes - started in Safe Mode, problem still occurs

Additional Info:
Computer affected is a Macbook Air 11" (Early 2015) with up-to-date updates installed

The other computer I tried is a Lenovo Y50-70 with Win 8.1 (from factory image) also with up-to-date updates installed.

Problem occurs regardless of which slideshow is opened.


User-Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36
Comment 1 Alex Thurgood 2017-09-04 07:39:00 UTC
Pretty certain this is a duplicate.
Comment 2 Alex Thurgood 2017-09-04 07:51:18 UTC
Can't find the earlier report after quick search. Setting to NEW
Comment 3 m_a_riosv 2017-09-18 00:06:15 UTC
*** Bug 112398 has been marked as a duplicate of this bug. ***
Comment 4 QA Administrators 2018-09-19 02:51:43 UTC Comment hidden (obsolete)
Comment 5 Piotr Porada 2018-09-19 20:26:12 UTC
As per instructions from Comment#4:

This bug is still present in the following version:

Version: 6.1.1.2
Build ID: 5d19a1bfa650b796764388cd8b33a5af1f5baa1b
CPU threads: 4; OS: Mac OS X 10.13.6; UI render: default; 
Locale: pl-PL (pl_PL.UTF-8); Calc: group threaded

The "About..." window also contains the link to the following commit: https://gerrit.libreoffice.org/gitweb?p=core.git&a=log&h=5d19a1bfa650b796764388cd8b33a5af1f5baa1b

I also tested with version 3.3.0.4 - the bug is present there, so I will mark the version, as inherited from OOo. The oldest version from the archive is:

LibreOffice 3.3.0 
OOO330m19 (Build:6)
tag libreoffice-3.3.0.4
Comment 6 Andrew Watson 2020-07-25 11:04:30 UTC
Bug still present in:

Version: 7.0.0.2
Build ID: c01aa64b6c3d89ebe5fe69c28c7adb24eb85249c
CPU threads: 4; OS: Mac OS X 10.11.6; UI render: default; VCL: osx
Locale: en-GB (en_GB.UTF-8); UI: en-GB
Calc: threaded
Comment 7 Andrew Watson 2020-07-25 11:15:18 UTC
*** Bug 135095 has been marked as a duplicate of this bug. ***
Comment 8 Andrew Watson 2022-03-16 12:26:26 UTC
Bug still present in:

Version: 7.3.1.3 / LibreOffice Community
Build ID: a69ca51ded25f3eefd52d7bf9a5fad8c90b87951
CPU threads: 4; OS: Mac OS X 10.14.6; UI render: default; VCL: osx
Locale: en-GB (en_GB.UTF-8); UI: en-GB
Calc: threaded
Comment 9 QA Administrators 2024-03-16 03:14:46 UTC
Dear Piotr Porada,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug