mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-05-15 14:15:55 -06:00
[GH-ISSUE #1614] Stopped working on adjusting built in monitor brightness after updating to MacOS Sequoia #898
Labels
No labels
Status: Abandoned
arm64
beta
beta
bug
done
duplicate
enhancement
feedback needed from reporter
in progress
invalid
investigating
known Issue
monitor Issue
pull-request
translation
unable to reproduce
unreleased
x86
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/MonitorControl#898
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @pureve on GitHub (Sep 22, 2024).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1614
Before opening the issue, have you...?
Describe the issue
After updating to MacOS Sequoia, the application crashes (the process terminates) whenever I try to adjust the brightness of the built-in monitor on both my MacBook Air M1 and MacBook Pro M1 Pro. However, adjusting the brightness on external displays still works as expected. Prior to the update, the brightness control for the built-in display functioned correctly, but now no brightness changes are applied through the app, and the app crashes when attempting to make adjustments.
Expected behavior
The application should successfully adjust the brightness of both the built-in monitor and the external display.
Anything else?
No response
Environment Information (please complete the following information)
@davidbonnet commented on GitHub (Sep 22, 2024):
Witnessing the exact same behaviour (silently quits as soon as the built-in display of the MacBook becomes active, e.g. by moving the cursor on it and clicking).
@pureve commented on GitHub (Sep 22, 2024):
I found a temporary workaround for this issue. This one isn't an official build but it works as expected 😄
https://github.com/MonitorControl/MonitorControl/issues/1570#issue-2346240609
@waydabber commented on GitHub (Sep 22, 2024):
Right, you need to use that build. :)