github-starred/MonitorControl

Fork 0

mirror of https://github.com/MonitorControl/MonitorControl.git synced 2026-05-15 14:15:55 -06:00

[GH-ISSUE #991] Default brightness keyboard keys not working after waking from sleep #599

New issue

Closed

opened 2026-05-05 06:20:25 -06:00 by gitea-mirror · 6 comments

gitea-mirror commented

2026-05-05 06:20:25 -06:00

Owner

Originally created by @stefbontinckx on GitHub (Apr 6, 2022).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/991

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

MonitorControl works fine most of the time, but after a while (After sleep) the brightness keys won't respond anymore, and thus MonitorControl does not change the brightness levels of my displays anymore.

The software control still works, it's only the keyboard keys that stop working.

Steps to reproduce

Wake computer from sleep
Change brightness with keyboard keys (the brightness change is in sync for both displays)
Keys don't do anything. Screen brightness does not change, and the Mac OS brightness overlays are not shown.

Expected behavior

Keys change the brightness levels of my displays, as they were doing before waking from sleep.

Anything else?

Environment Information (please complete the following information)

- macOS version: 12.3.1 (Monterey)
- Mac model: Mac Studio with Apple Magic Keyboard (Touch ID)
- MonitorControl version: 
- Monitor(s): 2x Dell U2723QE
- Apple Silicon/M1 (yes or no): yes

Originally created by @stefbontinckx on GitHub (Apr 6, 2022). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/991 ### 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 MonitorControl works fine most of the time, but after a while (After sleep) the brightness keys won't respond anymore, and thus MonitorControl does not change the brightness levels of my displays anymore. The software control still works, it's only the keyboard keys that stop working. ### Steps to reproduce 1. Wake computer from sleep 2. Change brightness with keyboard keys (the brightness change is in sync for both displays) 3. Keys don't do anything. Screen brightness does not change, and the Mac OS brightness overlays are not shown. ### Expected behavior Keys change the brightness levels of my displays, as they were doing before waking from sleep. ### Anything else? <img width="725" alt="Schermafbeelding 2022-04-06 om 22 46 42" src="https://user-images.githubusercontent.com/54323570/162067889-f75321e0-4841-44cc-bac9-b506971e8da4.png"> <img width="723" alt="Schermafbeelding 2022-04-06 om 22 47 21" src="https://user-images.githubusercontent.com/54323570/162067970-f6013114-9e3a-4124-b8e0-e08e57110d51.png"> <img width="726" alt="Schermafbeelding 2022-04-06 om 22 47 00" src="https://user-images.githubusercontent.com/54323570/162067990-49ed7fab-dca9-4b6e-9b71-4fa0f408b9c3.png"> ### Environment Information (please complete the following information) ```markdown - macOS version: 12.3.1 (Monterey) - Mac model: Mac Studio with Apple Magic Keyboard (Touch ID) - MonitorControl version: - Monitor(s): 2x Dell U2723QE - Apple Silicon/M1 (yes or no): yes ```

gitea-mirror

2026-05-05 06:20:25 -06:00

closed this issue
added the
feedback needed from reporter
label

gitea-mirror commented

2026-05-05 06:20:31 -06:00

Author

Owner

@stefbontinckx commented on GitHub (Apr 7, 2022):

Checked again this morning after waking Mac from sleep, and the keys were working again.
Maybe the times before I just 'locked' my Mac, so the displays only are put to sleep, not the Mac itself.

It's very inconsistent to reproduce I'm afraid.

@stefbontinckx commented on GitHub (Apr 7, 2022): Checked again this morning after waking Mac from sleep, and the keys were working again. Maybe the times before I just 'locked' my Mac, so the displays only are put to sleep, not the Mac itself. It's very inconsistent to reproduce I'm afraid.

gitea-mirror commented

2026-05-05 06:20:32 -06:00

Author

Owner

@waydabber commented on GitHub (Apr 7, 2022):

Well, if DDC control is working but keys are not registered then it might be that some other app (like Karabiner etc) is interfering and somehow grabs these events before MonitorControl does. You might want to check if the issue happens with a clean user profile without any other app running. I don't see any other way how could MonitorControl be selective about this. Also, you can check whether custom keyboard shortcuts work as that uses an entirely different mechanism to capture events than the media keys. If the latter works but the former one doesn't (or vice-versa) that might also give us a hint where to look.

@waydabber commented on GitHub (Apr 7, 2022): Well, if DDC control is working but keys are not registered then it might be that some other app (like Karabiner etc) is interfering and somehow grabs these events before MonitorControl does. You might want to check if the issue happens with a clean user profile without any other app running. I don't see any other way how could MonitorControl be selective about this. Also, you can check whether custom keyboard shortcuts work as that uses an entirely different mechanism to capture events than the media keys. If the latter works but the former one doesn't (or vice-versa) that might also give us a hint where to look.

gitea-mirror commented

2026-05-05 06:20:35 -06:00

Author

Owner

@stefbontinckx commented on GitHub (Apr 8, 2022):

Thanks! That's a great suggestion indeed.
I was using Karabiner before, but deleted it after migrating to my new Mac.
It definitely did not have the privacy permission any more to register keyboard input, probably some old files are still affecting some things, so I removed Karabiner completely via Terminal now.

I'll see if this improves the issue I saw, so far I haven't noticed it again.

@stefbontinckx commented on GitHub (Apr 8, 2022): Thanks! That's a great suggestion indeed. I was using Karabiner before, but deleted it after migrating to my new Mac. It definitely did not have the privacy permission any more to register keyboard input, probably some old files are still affecting some things, so I removed Karabiner completely via Terminal now. I'll see if this improves the issue I saw, so far I haven't noticed it again.

gitea-mirror commented

2026-05-05 06:20:37 -06:00

Author

Owner

@devnoname120 commented on GitHub (May 10, 2022):

@stefbontinckx Can you confirm that the issue didn't happen in the previous month after uninstalling Karabiner?

@devnoname120 commented on GitHub (May 10, 2022): @stefbontinckx Can you confirm that the issue didn't happen in the previous month after uninstalling Karabiner?

gitea-mirror commented

2026-05-05 06:20:39 -06:00

Author

Owner

@stefbontinckx commented on GitHub (May 10, 2022):

@devnoname120 It’s still happening sometimes. Only happens after waking my Mac Studio. A quick lock and unlock with my TouchID keyboard fixes the problem, and brightness keys respond again.

Again, it’s very inconsistent to reproduce. I’ve removed karabiner completely.

@stefbontinckx commented on GitHub (May 10, 2022): @devnoname120 It’s still happening sometimes. Only happens after waking my Mac Studio. A quick lock and unlock with my TouchID keyboard fixes the problem, and brightness keys respond again. Again, it’s very inconsistent to reproduce. I’ve removed karabiner completely.

gitea-mirror commented

2026-05-05 06:20:41 -06:00

Author

Owner

@devnoname120 commented on GitHub (May 11, 2022):

@stefbontinckx Thank you for the confirmation.

This issue is the reason why I stopped using MonitorControl :(

@devnoname120 commented on GitHub (May 11, 2022): @stefbontinckx Thank you for the confirmation. This issue is the reason why I stopped using MonitorControl :(