[GH-ISSUE #1015] Screen flashes when switching spaces with keyboard shortcut #612

New issue

Closed

opened 2026-05-05 06:22:15 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 06:22:15 -06:00

Owner

Originally created by @sebastianknell on GitHub (Apr 26, 2022).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1015

Before opening the issue, have you...?

Searched for existing issues
Looked through the wiki
Updated MonitorControl to the latest version (if applicable)

Describe the bug

When switching to another space using a keyboard shortcut (^1, ^2, or a custom one) the screen flashes to the max brightness before going back to the brightness I had. Note that this does not seem to happen (or maybe is not noticeable) when switching to the next/prev space (with ^ + arrow-left, or ^ + arrow-right).

Steps to reproduce

Switch spaces using the default mission control keyboard shortcut (^ + space number).

Expected behavior

The app keeps the same brightness without flashing when one switches spaces using a keyboard shortcut.

Anything else?

I'm running at 75 Hz. Don't know if that could have something to do.

Environment Information (please complete the following information)

- macOS version: 12.2 Monterrey
- Mac model: MacBook Pro (13-inch, 2017, Four Thunderbolt 3 Ports)
- MonitorControl version: v4.0.2
- Monitor(s): LG 27MK600M-B
- Apple Silicon/M1 (yes or no): no

Originally created by @sebastianknell on GitHub (Apr 26, 2022). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1015 ### Before opening the issue, have you...? - [X] Searched for existing issues - [X] Looked through [the wiki](https://github.com/MonitorControl/MonitorControl/wiki) - [X] Updated MonitorControl to the latest version (if applicable) ### Describe the bug When switching to another space using a keyboard shortcut (^1, ^2, or a custom one) the screen flashes to the max brightness before going back to the brightness I had. Note that this does not seem to happen (or maybe is not noticeable) when switching to the next/prev space (with ^ + arrow-left, or ^ + arrow-right). ### Steps to reproduce Switch spaces using the default mission control keyboard shortcut (^ + space number). ### Expected behavior The app keeps the same brightness without flashing when one switches spaces using a keyboard shortcut. ### Anything else? I'm running at 75 Hz. Don't know if that could have something to do. ### Environment Information (please complete the following information) ```markdown - macOS version: 12.2 Monterrey - Mac model: MacBook Pro (13-inch, 2017, Four Thunderbolt 3 Ports) - MonitorControl version: v4.0.2 - Monitor(s): LG 27MK600M-B - Apple Silicon/M1 (yes or no): no ```

gitea-mirror

2026-05-05 06:22:15 -06:00

closed this issue
added the
feedback needed from reporter
label

gitea-mirror commented

2026-05-05 06:22:22 -06:00

Author

Owner

@waydabber commented on GitHub (May 1, 2022):

HI @sebastianknell - This typically happens when overlay (shade) is used instead of gamma dimming. This is normal, overlays do not show during switching spaces.

If this is not the case, please let me know!

@waydabber commented on GitHub (May 1, 2022): HI @sebastianknell - This typically happens when overlay (shade) is used instead of gamma dimming. This is normal, overlays do not show during switching spaces. If this is not the case, please let me know!

gitea-mirror commented

2026-05-05 06:22:25 -06:00

Author

Owner

@sebastianknell commented on GitHub (May 1, 2022):

Ok I disabled the avoid gamma table manipulation setting in the displays section and the issue seems to be gone. Is that what you meant?

@sebastianknell commented on GitHub (May 1, 2022): Ok I disabled the avoid gamma table manipulation setting in the displays section and the issue seems to be gone. Is that what you meant?

gitea-mirror commented

2026-05-05 06:22:27 -06:00

Author

Owner

@the0neyouseek commented on GitHub (May 1, 2022):

Yes, the avoid gamma table manipulation should mostly be used if you have an incompatibility caused by a third party app such as f.lux. I'll close this issue as it seems everything is fixed for you.

@the0neyouseek commented on GitHub (May 1, 2022): Yes, the *avoid gamma table manipulation* should mostly be used if you have an incompatibility caused by a third party app such as [f.lux](https://justgetflux.com/). I'll close this issue as it seems everything is fixed for you.