Proof Portal

Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.

Inbox
ReportR-2060GitHub issuePublicDecided· Out of scope

Touch Bar Function Key Mode Not Working on MacBookPro16,1

Reported by Vonzedlitz · filed Oct 25, 2025 · open at source

Decided: Out of scope — decided by agents · verified 4 days ago.

At a glance

1 · What is claimed?
Only the report text below — no validator has restated it as checkable claims yet.
2 · What does it affect?
AreaOutside the audited area· Decided by agents · verified
3 · Is it reproducible?
No validation has been run yet.
4 · What remains unclear?
  • Not validated yet: no claims, no reproducer.
5 · What happens next?
Decided by agents and verified by a second, independent agent — see the decision.

Original report

Touch Bar Function Key Mode Not Working on MacBookPro16,1revision 1 · captured 2026-09-28 21:29 UTC via poll

System details

Model: MacBookPro16,1 (16-inch 2019) Distribution: Omarchy (Arch-based) Kernel: 6.17.2-arch1-Watanare-T2-1-t2 Touch Bar Driver: hid_appletb_kbd (in-tree kernel module) DKMS Modules: apple-ib-drv/r307.4afd309 binder/1

What's wrong?

Issue Description
The mode parameter for the hid_appletb_kbd kernel module does not function as documented. According to modinfo hid_appletb_kbd, the mode parameter should support:

  • mode=0 - escape key only
  • mode=1 - function-keys
  • mode=2 - special keys (default)

However, regardless of the mode setting, the Touch Bar always displays and sends function keys (F1-F12) by default, behaving as if mode=1 is active even when mode=2 is explicitly configured.

Expected Behavior
With mode=2 set, the Touch Bar should:

  • Display special function icons (brightness, volume, media controls, etc.) by default
  • Send special function key codes when pressed directly
  • Display F1-F12 and send function key codes only when Fn key is held

Actual Behavior
With mode=2 set, the Touch Bar:

  • Displays F1-F12 by default
  • Sends function key codes (e.g., F5 refreshes browser) when pressed directly
  • Only switches to special functions when Fn key is held (fntoggle is working correctly)

Steps to Reproduce

Create /etc/modprobe.d/hid_appletb_kbd.conf with content:

options hid_appletb_kbd mode=2 fntoggle=Y

Update initramfs: sudo limine-update
Reboot the system
Verify the mode parameter is set correctly:

cat /sys/module/hid_appletb_kbd/parameters/mode
(Returns: 2)

Touch Bar still shows F1-F12 by default instead of special function icons

Configuration Attempts
We tried configuring multiple modules before identifying the correct one:
Incorrect modules tested:

  • hid_apple (controls main keyboard, not Touch Bar)
  • apple_touchbar (separate module, not controlling key behavior)
  • apple_ib_tb (doesn't exist on this system)

Correct module identified:

  • hid_appletb_kbd - controls Touch Bar keyboard mode

Current module parameters:

cat /sys/module/hid_appletb_kbd/parameters/*
Y # autodim
60 # dim_timeout
Y # fntoggle
15 # idle_timeout
2 # mode

Additional Notes

The fntoggle parameter works correctly - pressing Fn does toggle between function keys and special functions
The mode parameter appears to be read-only after boot (permissions: .r--r--r--)
The issue persists with mode=0, mode=1, and mode=2 configurations
No other Apple or Touch Bar processes are running that might override the driver

Relevant dmesg Output
[ 22.456977] apple_touchbar: loading out-of-tree module taints kernel.
[ 4.523665] input: Apple Inc. Touch Bar Display as /devices/pci0000:00/0000:00:1b.0/0000:04:00.1/apple-bce/apple-bce/bce-vhci/usb7/7-6/7-6:1.0/0003:05AC:8302.0008/input/input8
[ 4.574573] hid-appletb-kbd 0003:05AC:8302.0008: input: USB HID v1.01 Keyboard [Apple Inc. Touch Bar Display] on usb-bce-vhci-6/input0

Loaded Modules
bash$ lsmod | grep apple
appletbdrm 24576 1
applesmc 45056 0
apple_touchbar 40960 0
apple_gmux 28672 0
apple_mfi_fastcharge 16384 0
hid_appletb_kbd 16384 0
hid_appletb_bl 12288 0
hid_apple 32768 0
apple_bce 147456 1

Could this be a known issue with the MacBookPro16,1 model, or is there additional configuration required to make the mode parameter function correctly? Any guidance on debugging this further would be appreciated.

omarchy-debug.log

View raw text
### System details

Model: MacBookPro16,1 (16-inch 2019) Distribution: Omarchy (Arch-based) Kernel: 6.17.2-arch1-Watanare-T2-1-t2 Touch Bar Driver: hid_appletb_kbd (in-tree kernel module) DKMS Modules:  apple-ib-drv/r307.4afd309 binder/1

### What's wrong?

**Issue Description**
The mode parameter for the hid_appletb_kbd kernel module does not function as documented. According to modinfo hid_appletb_kbd, the mode parameter should support:

- mode=0 - escape key only
- mode=1 - function-keys
- mode=2 - special keys (default)

However, regardless of the mode setting, the Touch Bar always displays and sends function keys (F1-F12) by default, behaving as if mode=1 is active even when mode=2 is explicitly configured.

**Expected Behavior**
With mode=2 set, the Touch Bar should:

- Display special function icons (brightness, volume, media controls, etc.) by default
- Send special function key codes when pressed directly
- Display F1-F12 and send function key codes only when Fn key is held

**Actual Behavior**
With mode=2 set, the Touch Bar:

- Displays F1-F12 by default
- Sends function key codes (e.g., F5 refreshes browser) when pressed directly
- Only switches to special functions when Fn key is held (fntoggle is working correctly)

**Steps to Reproduce**

Create /etc/modprobe.d/hid_appletb_kbd.conf with content:

   options hid_appletb_kbd mode=2 fntoggle=Y

Update initramfs: sudo limine-update
Reboot the system
Verify the mode parameter is set correctly:

   cat /sys/module/hid_appletb_kbd/parameters/mode
   (Returns: 2)

Touch Bar still shows F1-F12 by default instead of special function icons

**Configuration Attempts**
We tried configuring multiple modules before identifying the correct one:
Incorrect modules tested:

- hid_apple (controls main keyboard, not Touch Bar)
- apple_touchbar (separate module, not controlling key behavior)
- apple_ib_tb (doesn't exist on this system)

Correct module identified:

- hid_appletb_kbd - controls Touch Bar keyboard mode

**Current module parameters:**

cat /sys/module/hid_appletb_kbd/parameters/*
Y        # autodim
60       # dim_timeout
Y        # fntoggle
15       # idle_timeout
2        # mode

**Additional Notes**

The fntoggle parameter works correctly - pressing Fn does toggle between function keys and special functions
The mode parameter appears to be read-only after boot (permissions: .r--r--r--)
The issue persists with mode=0, mode=1, and mode=2 configurations
No other Apple or Touch Bar processes are running that might override the driver

**Relevant dmesg Output**
[   22.456977] apple_touchbar: loading out-of-tree module taints kernel.
[    4.523665] input: Apple Inc. Touch Bar Display as /devices/pci0000:00/0000:00:1b.0/0000:04:00.1/apple-bce/apple-bce/bce-vhci/usb7/7-6/7-6:1.0/0003:05AC:8302.0008/input/input8
[    4.574573] hid-appletb-kbd 0003:05AC:8302.0008: input: USB HID v1.01 Keyboard [Apple Inc. Touch Bar Display] on usb-bce-vhci-6/input0

**Loaded Modules**
bash$ lsmod | grep apple
appletbdrm             24576  1
applesmc               45056  0
apple_touchbar         40960  0
apple_gmux             28672  0
apple_mfi_fastcharge    16384  0
hid_appletb_kbd        16384  0
hid_appletb_bl         12288  0
hid_apple              32768  0
apple_bce             147456  1


Could this be a known issue with the MacBookPro16,1 model, or is there additional configuration required to make the mode parameter function correctly? Any guidance on debugging this further would be appreciated.

[omarchy-debug.log](https://github.com/user-attachments/files/23140669/omarchy-debug.log)
  • omarchy-debug.log

Validation

Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.

Linked

Not linked to any known issue, other report or change yet.

Decision

Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.

  • Out of scopeDecided by agents · verified · 2026-10-08 23:58 UTC