[GH-ISSUE #340] Brightness buttons occasionally not responding #273

Closed
opened 2026-05-05 05:39:48 -06:00 by gitea-mirror · 7 comments
Owner

Originally created by @AlfHou on GitHub (Dec 2, 2020).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/340

Checklist

  • I have searched for existing issues
  • I have looked through the wiki
  • I have updated MonitorControl to the latest version

Describe the bug
Occasionally the brightness buttons on my MacBook 15" (mid 2012) just ceases to respond. No overlay, no change in brightness. The only fix I've found is quitting MonitorControl. Note, this happens when there is no display connected.

To Reproduce
Steps to reproduce the behavior:

  1. Either launch MonitorControl or have it auto start on boot
  2. Use computer as normal for an unspecified time
  3. See error

Expected behavior
Being able to use by brightness buttons as normal while MonitorControl is running in the background

Additional context
This happens very spordically, and only occurs maybe twice a month or something. Is there anywhere I can read the logs to better troubleshoot/provide better debugging info?

Super appreciative of your work! I think MonitorControl is a fantastic tool 😄

Environment Information (please complete the following information):

  • macOS version: MacOS Mojave, 10.14.6
  • MonitorControl version: 2.1.0 (Build 721)
  • Monitor(s): Non connected
Originally created by @AlfHou on GitHub (Dec 2, 2020). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/340 **Checklist** - [x] I have searched for existing issues - [x] I have looked through [the wiki](https://github.com/MonitorControl/MonitorControl/wiki) - [x] I have updated MonitorControl to the latest version **Describe the bug** Occasionally the brightness buttons on my MacBook 15" (mid 2012) just ceases to respond. No overlay, no change in brightness. The only fix I've found is quitting MonitorControl. Note, this happens when there is no display connected. **To Reproduce** Steps to reproduce the behavior: 1. Either launch MonitorControl or have it auto start on boot 2. Use computer as normal for an unspecified time 3. See error **Expected behavior** Being able to use by brightness buttons as normal while MonitorControl is running in the background **Additional context** This happens very spordically, and only occurs maybe twice a month or something. Is there anywhere I can read the logs to better troubleshoot/provide better debugging info? Super appreciative of your work! I think MonitorControl is a fantastic tool 😄 **Environment Information (please complete the following information):** - macOS version: MacOS Mojave, 10.14.6 - MonitorControl version: 2.1.0 (Build 721) - Monitor(s): Non connected
gitea-mirror 2026-05-05 05:39:48 -06:00
Author
Owner

@ibash commented on GitHub (Dec 28, 2020):

This is not #282 is it?

<!-- gh-comment-id:751583770 --> @ibash commented on GitHub (Dec 28, 2020): This is not #282 is it?
Author
Owner

@AlfHou commented on GitHub (Dec 28, 2020):

Hmm, it doesn't seem so. I tried with both Secure Keyboard Entry toggled on and off. I was still able to change brightness. To be clear, this bug only happens occasionally. I can use the brightness keys fine for days with the MonitorControl running in the background, then suddenly they stop working and I have to quit the program.

I didn't see it described anywhere, but are there any logs I could look into?

<!-- gh-comment-id:751639999 --> @AlfHou commented on GitHub (Dec 28, 2020): Hmm, it doesn't seem so. I tried with both `Secure Keyboard Entry` toggled on and off. I was still able to change brightness. To be clear, this bug only happens occasionally. I can use the brightness keys fine for days with the MonitorControl running in the background, then suddenly they stop working and I have to quit the program. I didn't see it described anywhere, but are there any logs I could look into?
Author
Owner

@JoniVR commented on GitHub (Dec 28, 2020):

Do you happen to disconnect the Monitor in between when this happens? I have noticed that when you disconnect the monitor, you'll need to restart MonitorControl before it'll actually work again with the internal display, but I'm not sure if this is a related issue.

<!-- gh-comment-id:751714154 --> @JoniVR commented on GitHub (Dec 28, 2020): Do you happen to disconnect the Monitor in between when this happens? I have noticed that when you disconnect the monitor, you'll need to restart MonitorControl before it'll actually work again with the internal display, but I'm not sure if this is a related issue.
Author
Owner

@achembarpu commented on GitHub (Mar 4, 2021):

I have the same issue. Exact same cause, disconnecting all external monitors and leaving only the internal display. The brightness keys stop working, and need to quit MonitorControl to fix.

<!-- gh-comment-id:790789576 --> @achembarpu commented on GitHub (Mar 4, 2021): I have the same issue. Exact same cause, disconnecting all external monitors and leaving only the internal display. The brightness keys stop working, and need to quit MonitorControl to fix.
Author
Owner

@jellybeaner101 commented on GitHub (Mar 6, 2021):

I now have the same issue. MontorControl has worked perfectly for years but now the brightness keys stop working intermittently.

I recently updated to the latest security patch for 10.14.6 (2021-002). Not sure if its related but I didn't have the problem before the update.

<!-- gh-comment-id:791902779 --> @jellybeaner101 commented on GitHub (Mar 6, 2021): I now have the same issue. MontorControl has worked perfectly for years but now the brightness keys stop working intermittently. I recently updated to the latest security patch for 10.14.6 (2021-002). Not sure if its related but I didn't have the problem before the update.
Author
Owner

@waydabber commented on GitHub (Aug 21, 2021):

Hi all, can you please try the latest 3.0.0 release and see if this is still a problem? Thank you!

<!-- gh-comment-id:903128965 --> @waydabber commented on GitHub (Aug 21, 2021): Hi all, can you please try the latest 3.0.0 release and see if this is still a problem? Thank you!
Author
Owner

@waydabber commented on GitHub (Aug 25, 2021):

I'll close this issue for now but please feel free to comment if there is anything we can do. If the issue persists, we can reopen this issue! Thank you!

<!-- gh-comment-id:905690195 --> @waydabber commented on GitHub (Aug 25, 2021): I'll close this issue for now but please feel free to comment if there is anything we can do. If the issue persists, we can reopen this issue! Thank you!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/MonitorControl#273
No description provided.