github-starred/MonitorControl

Fork 0

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

[GH-ISSUE #1211] ⚠️ What to do if Ventura update messes up keyboard control? #703

New issue

Closed

opened 2026-05-05 06:32:14 -06:00 by gitea-mirror · 14 comments

gitea-mirror commented

2026-05-05 06:32:14 -06:00

Owner

Originally created by @mike126126 on GitHub (Oct 26, 2022).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1211

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

更新了macOS13.0之后，键盘上的快捷键失效了。电脑型号Mac mini M1。

After updating macOS 13.0, the shortcut keys on the keyboard are invalid. Computer model Mac mini M1

Steps to reproduce

更新了macOS13.0之后，键盘上的快捷键失效了。电脑型号Mac mini M1。

After updating macOS 13.0, the shortcut keys on the keyboard are invalid. Computer model Mac mini M1

Expected behavior

暂无

Anything else?

No response

Environment Information (please complete the following information)

- macOS version:13.0
- Mac model:Mac mini M1
- MonitorControl version:4.1.0
- Monitor(s):LG
- Apple Silicon/M1 (yes or no): yes

Originally created by @mike126126 on GitHub (Oct 26, 2022). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1211 ### 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 更新了macOS13.0之后，键盘上的快捷键失效了。电脑型号Mac mini M1。 -- After updating macOS 13.0, the shortcut keys on the keyboard are invalid. Computer model Mac mini M1 ### Steps to reproduce 更新了macOS13.0之后，键盘上的快捷键失效了。电脑型号Mac mini M1。 -- After updating macOS 13.0, the shortcut keys on the keyboard are invalid. Computer model Mac mini M1 ### Expected behavior 暂无 ### Anything else? _No response_ ### Environment Information (please complete the following information) ```markdown - macOS version:13.0 - Mac model:Mac mini M1 - MonitorControl version:4.1.0 - Monitor(s):LG - Apple Silicon/M1 (yes or no): yes ```

gitea-mirror closed this issue

2026-05-05 06:32:15 -06:00

gitea-mirror commented

2026-05-05 06:32:19 -06:00

Author

Owner

@joehquak commented on GitHub (Oct 27, 2022):

It would be helpful if you share with the team which shortcuts you are referring to (sound or brightness or both)

Also to confirm if you have MonitorControl displaying correctly in your taskbar and share a screenshot of all of your settings

@joehquak commented on GitHub (Oct 27, 2022): It would be helpful if you share with the team which shortcuts you are referring to (sound or brightness or both) Also to confirm if you have MonitorControl displaying correctly in your taskbar and share a screenshot of all of your settings

gitea-mirror commented

2026-05-05 06:32:22 -06:00

Author

Owner

@mike126126 commented on GitHub (Oct 27, 2022):

thank you. I solved the problem by "uninstalling the app and reinstalling it"

@mike126126 commented on GitHub (Oct 27, 2022): thank you. I solved the problem by "uninstalling the app and reinstalling it"

gitea-mirror commented

2026-05-05 06:32:23 -06:00

Author

Owner

@Fire5Lion commented on GitHub (Nov 1, 2022):

Hi, I have a similar problem.
After the update, standard keyboard brightness key don't working. Custom keyboard shortcuts work. Reinstall does not help
P.S Volume standard key work

macOS version:13.0
Mac model:Mac mini M1
MonitorControl version:4.1.0
Monitor(s):LG
Apple Silicon/M1 (yes or no): yes

@Fire5Lion commented on GitHub (Nov 1, 2022): Hi, I have a similar problem. After the update, standard keyboard brightness key don't working. Custom keyboard shortcuts work. Reinstall does not help P.S Volume standard key work - macOS version:13.0 - Mac model:Mac mini M1 - MonitorControl version:4.1.0 - Monitor(s):LG - Apple Silicon/M1 (yes or no): yes

gitea-mirror commented

2026-05-05 06:32:25 -06:00

Author

Owner

@nvlashi commented on GitHub (Nov 4, 2022):

I'm encountering the same issue since upgrading to Ventura on my Intel silicon Macbook Pro.

@nvlashi commented on GitHub (Nov 4, 2022): I'm encountering the same issue since upgrading to Ventura on my Intel silicon Macbook Pro.

gitea-mirror commented

2026-05-05 06:32:28 -06:00

Author

Owner

@sxflynn commented on GitHub (Nov 11, 2022):

Same problem. It literally just started happening. I had MacOS 13 already installed and it was okay, this monitor brightness was working correctly. I have a Dell P2027 and an M1 Mac Mini.

@sxflynn commented on GitHub (Nov 11, 2022): Same problem. It literally just started happening. I had MacOS 13 already installed and it was okay, this monitor brightness was working correctly. I have a Dell P2027 and an M1 Mac Mini.

gitea-mirror commented

2026-05-05 06:32:31 -06:00

Author

Owner

@waydabber commented on GitHub (Nov 14, 2022):

Hi guys, it should be working fine, but you might have to re-add the application under Privacy&Security / Accessibility. If all things fail, you can reset the entire accessibility list and then re-add the application.

@waydabber commented on GitHub (Nov 14, 2022): Hi guys, it should be working fine, but you might have to re-add the application under Privacy&Security / Accessibility. If all things fail, you can reset the entire accessibility list and then re-add the application.

gitea-mirror commented

2026-05-05 06:32:33 -06:00

Author

Owner

@waydabber commented on GitHub (Nov 14, 2022):

Let me know if this issue is still valid or we can close it! Thank you!

@waydabber commented on GitHub (Nov 14, 2022): Let me know if this issue is still valid or we can close it! Thank you!

gitea-mirror commented

2026-05-05 06:32:34 -06:00

Author

Owner

@Fire5Lion commented on GitHub (Nov 15, 2022):

Hi guys, it should be working fine, but you might have to re-add the application under Privacy&Security / Accessibility. If all things fail, you can reset the entire accessibility list and then re-add the application.

it works thanks

@Fire5Lion commented on GitHub (Nov 15, 2022): > Hi guys, it should be working fine, but you might have to re-add the application under Privacy&Security / Accessibility. If all things fail, you can reset the entire accessibility list and then re-add the application. it works thanks

gitea-mirror commented

2026-05-05 06:32:36 -06:00

Author

Owner

@Fire5Lion commented on GitHub (Nov 15, 2022):

Hi guys, it should be working fine, but you might have to re-add the application under Privacy&Security / Accessibility. If all things fail, you can reset the entire accessibility list and then re-add the application.

it works thanks

no, sorry, it works for 1 minute after reboot. Then only the volume buttons work.
I don't have any other brightness control apps. Maybe there is an opportunity to take the application logs and send it?

P.S. Volume buttons work even without setting in the Privacy&Security / Accessibility

@Fire5Lion commented on GitHub (Nov 15, 2022): > > Hi guys, it should be working fine, but you might have to re-add the application under Privacy&Security / Accessibility. If all things fail, you can reset the entire accessibility list and then re-add the application. > > it works thanks no, sorry, it works for 1 minute after reboot. Then only the volume buttons work. I don't have any other brightness control apps. Maybe there is an opportunity to take the application logs and send it? P.S. Volume buttons work even without setting in the Privacy&Security / Accessibility

gitea-mirror commented

2026-05-05 06:32:37 -06:00

Author

Owner

@waydabber commented on GitHub (Nov 15, 2022):

Well, I am not sure app logs will help much as it should generally work, but MC might have some other Ventura specific issues (these should be investigated, maybe there is a connection, but there was no similar reports from others so far - #1221).

You can also try the latest beta of BetterDisplay and see if that works. That version contains some Ventura specific fixes and should not have any issues + it has brightness control feature as well. If BD exhibits the same problem then that gives some additional insights and helps figuring out what could be going on.

An other approach is to reset the accessibility permissions database by issuing the sudo tccutil reset Accessibility or if it fails sudo tccutil reset All command in Terminal. Note, that you'll have to re-add the the app and all other apps as this creates a blank slate.

@waydabber commented on GitHub (Nov 15, 2022): Well, I am not sure app logs will help much as it should generally work, but MC might have some other Ventura specific issues (these should be investigated, maybe there is a connection, but there was no similar reports from others so far - #1221). You can also try the latest beta of [BetterDisplay](https://github.com/waydabber/BetterDisplay/releases) and see if that works. That version contains some Ventura specific fixes and should not have any issues + it has brightness control feature as well. If BD exhibits the same problem then that gives some additional insights and helps figuring out what could be going on. An other approach is to reset the accessibility permissions database by issuing the `sudo tccutil reset Accessibility` or if it fails `sudo tccutil reset All` command in Terminal. Note, that you'll have to re-add the the app and all other apps as this creates a blank slate.

gitea-mirror commented

2026-05-05 06:32:39 -06:00

Author

Owner

@Fire5Lion commented on GitHub (Nov 15, 2022):

BetterDisplay also worked for a minute after a reboot.

I uninstalled BetterDisplay, run sudo tccutil reset Accessibility and sudo tccutil reset All , rebooted, opened the monitor control, added it to Privacy&Security / Accessibility. It Works.
Then added Chrome Remote Desktop and VMware Horizon Client to Privacy&Security / Accessibility. Now MonitorControl works. watching

@Fire5Lion commented on GitHub (Nov 15, 2022): BetterDisplay also worked for a minute after a reboot. I uninstalled BetterDisplay, run sudo tccutil reset Accessibility and sudo tccutil reset All , rebooted, opened the monitor control, added it to Privacy&Security / Accessibility. It Works. Then added Chrome Remote Desktop and VMware Horizon Client to Privacy&Security / Accessibility. Now MonitorControl works. watching

gitea-mirror commented

2026-05-05 06:32:42 -06:00

Author

Owner

@waydabber commented on GitHub (Nov 15, 2022):

All right, then the problem was not BD vs MC, but simply a corrupted permissions database. It probably got messed up during the update.

@waydabber commented on GitHub (Nov 15, 2022): All right, then the problem was not BD vs MC, but simply a corrupted permissions database. It probably got messed up during the update.

gitea-mirror commented

2026-05-05 06:32:44 -06:00

Author

Owner

@waydabber commented on GitHub (Nov 15, 2022):

I pinned this issue so others can easily find the solution, probably more ppl will encounter this.

@waydabber commented on GitHub (Nov 15, 2022): I pinned this issue so others can easily find the solution, probably more ppl will encounter this.

gitea-mirror commented

2026-05-05 06:32:45 -06:00

Author

Owner

@jvanakker commented on GitHub (Apr 18, 2023):

Hi guys, it should be working fine, but you might have to re-add the application under Privacy&Security / Accessibility. If all things fail, you can reset the entire accessibility list and then re-add the application.

This solved the issue for me on macOS Monterey.

@jvanakker commented on GitHub (Apr 18, 2023): > Hi guys, it should be working fine, but you might have to re-add the application under Privacy&Security / Accessibility. If all things fail, you can reset the entire accessibility list and then re-add the application. This solved the issue for me on macOS Monterey.

gitea-mirror referenced this issue

2026-05-05 07:07:04 -06:00

[PR #703] [CLOSED] New translation #1185