mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-05-15 22:01:08 -06:00
[GH-ISSUE #1800] On MacBook native display, macOS Tahoe's brightness meter is always empty #992
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#992
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 @georgeyu26 on GitHub (Sep 16, 2025).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1800
Before opening the issue, have you...?
Describe the bug
On MacBook native display, macOS Tahoe's brightness meter is always empty, even when adjusting brightness. These happens when MonitorControl is either open or quit.
Screen recording: https://imgur.com/a/NrA3VvT
Steps to reproduce
I am still trying to figure out how to reproduce the problem. It has happened a few times already but I have no idea how to reproduce it at the moment. Restarting the computer temporarily fixes the issue.
Expected behavior
On MacBook native display, macOS Tahoe's brightness meter should show the current brightness when adjusting brightness.
Anything else?
No response
Environment Information (please complete the following information)
@georgeyu26 commented on GitHub (Sep 16, 2025):
@waydabber this might be related to https://github.com/MonitorControl/MonitorControl/issues/1798. In the meantime, I'm trying out BetterDisplay and it seems to solve all my Tahoe related issues. Thanks for the suggestion.
@waydabber commented on GitHub (Sep 17, 2025):
Yes, it's the same as 1798 - this might happen if the app is using software brightness control for some reason.