[GH-ISSUE #1651] App crash #917

New issue

Closed

opened 2026-05-05 06:53:37 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 06:53:37 -06:00

Owner

Originally created by @iliescumichele on GitHub (Oct 10, 2024).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1651

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

I noticed this behavior after updating macOS to Sequoia.
When I use the keybords standard brightness keys on my external monitor (mouse pointer on external monitor) it works like before, when I use it on my macbook's display it works (probably the native behavior) the app crashes.

I have the following setting enabled in my mac:

Multiple displays: Show separate controls for each display in menu
Application:
- Start at Login
- Automatically check for updates
Brightness control:
- Show brightness slider in menu
- Enable for Apple branded and built-in displays as well
General options:
- Enable smooth brightness transitions
- Combine hardware and software dimming
Upon startup or wake: Assume last saved settings are valid (recommended)
Brightness and contrast: Standard keyboard brightness keys
Do not use alternative briahtness keys
Screen to control: Depends on mouse pointer position
NO advanced setting

Steps to reproduce

When I use the keybords standard brightness keys on my external monitor (mouse pointer on external monitor) it works like before, when I use it on my macbook's display it works (probably the native behavior) the app crashes.

Expected behavior

The app should not crash/close

Anything else?

No response

Environment Information (please complete the following information)

- macOS version: 15.0.1 Sequoia
- Mac model: MacBook Pro (16-inch)
- MonitorControl version: 4.2.0 Build 7048
- Monitor(s): LG 29WN600
- Apple Silicon/M1 (yes or no): yes

Originally created by @iliescumichele on GitHub (Oct 10, 2024). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1651 ### 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 I noticed this behavior after updating macOS to Sequoia. When I use the keybords standard brightness keys on my external monitor (mouse pointer on external monitor) it works like before, when I use it on my macbook's display it works (probably the native behavior) the app crashes. I have the following setting enabled in my mac: - **Multiple displays:** Show separate controls for each display in menu - **Application:** - Start at Login - Automatically check for updates - **Brightness control:** - Show brightness slider in menu - Enable for Apple branded and built-in displays as well - **General options:** - Enable smooth brightness transitions - Combine hardware and software dimming - **Upon startup or wake:** Assume last saved settings are valid (recommended) - **Brightness and contrast:** Standard keyboard brightness keys - **Do not use alternative briahtness keys** - **Screen to control:** Depends on mouse pointer position - NO advanced setting ### Steps to reproduce When I use the keybords standard brightness keys on my external monitor (mouse pointer on external monitor) it works like before, when I use it on my macbook's display it works (probably the native behavior) the app crashes. ### Expected behavior The app should not crash/close ### Anything else? _No response_ ### Environment Information (please complete the following information) ```markdown - macOS version: 15.0.1 Sequoia - Mac model: MacBook Pro (16-inch) - MonitorControl version: 4.2.0 Build 7048 - Monitor(s): LG 29WN600 - Apple Silicon/M1 (yes or no): yes ```

gitea-mirror closed this issue

2026-05-05 06:53:40 -06:00

gitea-mirror commented

2026-05-05 06:53:43 -06:00

Author

Owner

@waydabber commented on GitHub (Oct 10, 2024):

You need to upgrade to the latest version on Sequoia. But I gather you found the download. :)

@waydabber commented on GitHub (Oct 10, 2024): You need to upgrade to the latest version on Sequoia. But I gather you found the download. :)