[GH-ISSUE #1791] macOS Tahoe 26 Compatibility - MonitorControl crashes and exits #990

New issue

Closed

opened 2026-05-05 07:00:23 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 07:00:23 -06:00

Owner

Originally created by @nguyentrongduy on GitHub (Sep 2, 2025).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1791

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

Actual Behavior:
MonitorControl crashes and exits immediately when I try to adjust the brightness slider for the built-in Color LCD display. The app works fine when adjusting the external Samsung monitor brightness, but consistently crashes when touching the built-in display controls.

Additional Context:
External monitor brightness control works perfectly
The crash happens every time I interact with the built-in display brightness slider
No error message is displayed; the app just vanishes
Need to manually restart the app after each crash
This makes the app unusable for controlling the built-in display brightness

Frequency:
Reproducible 100% of the time when adjusting the built-in display brightness.

Steps to reproduce

Open MonitorControl from the menu bar
Click on the brightness slider for "Color LCD" (built-in display)
Try to adjust the brightness level
App crashes and disappears from the menu bar

Expected behavior

The app should allow me to adjust brightness for both external monitor (S27B80P) and built-in display (Color LCD) without crashing.

Anything else?

No response

Environment Information (please complete the following information)

System Information:
- macOS version: Version 26.0 Beta (25A5349a)
- Mac model: MacBook Pro M1 13' 2020
- MacOS version: Version 26.0 Beta (25A5349a)
- MonitorControl version: Version 4.2.0 Build 7048
- Hardware: MacBook with built-in Color LCD display
- External monitor: Samsung S27B80P connected
- Apple Silicon/M1: yes

Originally created by @nguyentrongduy on GitHub (Sep 2, 2025). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1791 ### 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 Actual Behavior: MonitorControl crashes and exits immediately when I try to adjust the brightness slider for the built-in Color LCD display. The app works fine when adjusting the external Samsung monitor brightness, but consistently crashes when touching the built-in display controls. Additional Context: External monitor brightness control works perfectly The crash happens every time I interact with the built-in display brightness slider No error message is displayed; the app just vanishes Need to manually restart the app after each crash This makes the app unusable for controlling the built-in display brightness Frequency: Reproducible 100% of the time when adjusting the built-in display brightness. ### Steps to reproduce 1. Open MonitorControl from the menu bar 2. Click on the brightness slider for "Color LCD" (built-in display) 3. Try to adjust the brightness level 4. App crashes and disappears from the menu bar ### Expected behavior The app should allow me to adjust brightness for both external monitor (S27B80P) and built-in display (Color LCD) without crashing. ### Anything else? _No response_ ### Environment Information (please complete the following information) ```markdown System Information: - macOS version: Version 26.0 Beta (25A5349a) - Mac model: MacBook Pro M1 13' 2020 - MacOS version: Version 26.0 Beta (25A5349a) - MonitorControl version: Version 4.2.0 Build 7048 - Hardware: MacBook with built-in Color LCD display - External monitor: Samsung S27B80P connected - Apple Silicon/M1: yes ```

gitea-mirror closed this issue

2026-05-05 07:00:26 -06:00

gitea-mirror commented

2026-05-05 07:00:30 -06:00

Author

Owner

@waydabber commented on GitHub (Sep 2, 2025):

Use v4.3.3. The v4.2.0 will not auto update. https://github.com/MonitorControl/MonitorControl/issues/1663

@waydabber commented on GitHub (Sep 2, 2025): Use v4.3.3. The v4.2.0 will not auto update. https://github.com/MonitorControl/MonitorControl/issues/1663