[GH-ISSUE #314] Shortcuts do not work with iterm2 and external keyboard #245

Closed
opened 2026-05-05 05:30:10 -06:00 by gitea-mirror · 2 comments
Owner

Originally created by @ibash on GitHub (Oct 30, 2020).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/314

Checklist

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

Describe the bug
When using iterm2 and monitor control the shortcuts to change brightness are not detected by monitor control.

To Reproduce
Steps to reproduce the behavior:

  1. Install iterm2 and monitor control
  2. Connct an external keyboard and monitor
  3. Open iterm2 and give it focus
  4. Press the f14 / f15 shortcuts to change brightness

Expected behavior
Brightness changes

Actual
Brightness does not change

Additional context
This might be an iterm2 only issue, but I wanted to see if anyone else has hit this or not.

Environment Information (please complete the following information):

  • macOS version: 10.15.7
  • MonitorControl version: 2.1.0
  • Monitor(s): viewsonic vp2768-4k
Originally created by @ibash on GitHub (Oct 30, 2020). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/314 **Checklist** <!-- Before you submit your issue, please make sure to check the following boxes by putting an x in the [ ] (don't: [x ], [ x], do: [x]) --> - [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** When using iterm2 and monitor control the shortcuts to change brightness are not detected by monitor control. **To Reproduce** Steps to reproduce the behavior: 1. Install iterm2 and monitor control 2. Connct an external keyboard and monitor 3. Open iterm2 and give it focus 4. Press the f14 / f15 shortcuts to change brightness **Expected behavior** Brightness changes **Actual** Brightness does not change **Additional context** This might be an iterm2 only issue, but I wanted to see if anyone else has hit this or not. **Environment Information (please complete the following information):** - macOS version: 10.15.7 - MonitorControl version: 2.1.0 - Monitor(s): viewsonic vp2768-4k
gitea-mirror 2026-05-05 05:30:10 -06:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@JoniVR commented on GitHub (Oct 30, 2020):

Possibly a duplicate of #282? Could be related to the secure keyboard entry setting.

<!-- gh-comment-id:719710079 --> @JoniVR commented on GitHub (Oct 30, 2020): Possibly a duplicate of #282? Could be related to the secure keyboard entry setting.
Author
Owner

@ibash commented on GitHub (Oct 30, 2020):

Yep! Thank you! Not sure why I didn't find that in my search...

<!-- gh-comment-id:719748745 --> @ibash commented on GitHub (Oct 30, 2020): Yep! Thank you! Not sure why I didn't find that in my search...
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#245
No description provided.