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-1158GitHub issuePublicDecided· Out of scope

Update > Hardware > Trackpad silently no-ops on Apple bcm5974 trackpads

Reported by cmyk · filed Aug 31, 2026 · 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

Update > Hardware > Trackpad silently no-ops on Apple bcm5974 trackpadsrevision 1 · captured 2026-09-28 21:24 UTC via poll

What happened

On a 2011 MacBook Pro, selecting Super menu → Update → Hardware → Trackpad opens a floating terminal that immediately disappears without displaying or doing anything.

This menu entry looks like a trackpad control/settings item, but it invokes:

omarchy-launch-floating-terminal-with-presentation omarchy-restart-trackpad

Running the underlying command directly confirms the silent success:

$ omarchy-restart-trackpad
$ echo $?
0

The trackpad is unchanged.

Root cause

omarchy-restart-trackpad only handles:

  1. devices under /sys/bus/i2c/drivers/i2c_hid_acpi/i2c-*
  2. the intel_quicki2c module

This MacBook's correctly detected internal trackpad is USB and uses the bcm5974 driver:

Hyprland device name: bcm5974
ID_INPUT_TOUCHPAD=1
ID_INPUT_TOUCHPAD_INTEGRATION=internal
ID_MODEL=Apple_Internal_Keyboard___Trackpad
ID_MODEL_ID=0246
ID_USB_DRIVER=bcm5974

There are no matching i2c_hid_acpi devices and intel_quicki2c is not loaded. Both branches are therefore skipped, the script prints nothing, and exits 0. Because the menu entry is displayed unconditionally, it presents a dead action on this hardware.

Steps to reproduce

  1. Boot Omarchy on a MacBook using the bcm5974 trackpad driver.
  2. Open the Super menu.
  3. Select Update → Hardware → Trackpad.
  4. Observe the floating terminal disappear immediately and the trackpad remain unchanged.
  5. Run omarchy-restart-trackpad directly; it produces no output and exits 0.

Expected behavior

One of:

  • support resetting the detected bcm5974 device safely;
  • hide the recovery action when none of its supported driver paths exists; or
  • retain the action but report clearly that this trackpad driver is unsupported and return a non-zero status.

System details

  • Omarchy: 4.0.2-1
  • Kernel: 7.1.9-arch1-2
  • Hardware: 2011 15-inch MacBook Pro
  • Trackpad: Apple Internal Keyboard / Trackpad, USB ID 05ac:0246
  • Driver: bcm5974

Related but distinct

#9190 covers omarchy-hw-touchpad failing to recognize the name bcm5974, which hides/breaks the touchpad enable/disable toggle. Fixing that detector does not fix this issue: the separately exposed omarchy-restart-trackpad action still only implements I2C/Intel reset paths.

View raw text
## What happened

On a 2011 MacBook Pro, selecting **Super menu → Update → Hardware → Trackpad** opens a floating terminal that immediately disappears without displaying or doing anything.

This menu entry looks like a trackpad control/settings item, but it invokes:

```text
omarchy-launch-floating-terminal-with-presentation omarchy-restart-trackpad
```

Running the underlying command directly confirms the silent success:

```console
$ omarchy-restart-trackpad
$ echo $?
0
```

The trackpad is unchanged.

## Root cause

`omarchy-restart-trackpad` only handles:

1. devices under `/sys/bus/i2c/drivers/i2c_hid_acpi/i2c-*`
2. the `intel_quicki2c` module

This MacBook's correctly detected internal trackpad is USB and uses the `bcm5974` driver:

```text
Hyprland device name: bcm5974
ID_INPUT_TOUCHPAD=1
ID_INPUT_TOUCHPAD_INTEGRATION=internal
ID_MODEL=Apple_Internal_Keyboard___Trackpad
ID_MODEL_ID=0246
ID_USB_DRIVER=bcm5974
```

There are no matching `i2c_hid_acpi` devices and `intel_quicki2c` is not loaded. Both branches are therefore skipped, the script prints nothing, and exits 0. Because the menu entry is displayed unconditionally, it presents a dead action on this hardware.

## Steps to reproduce

1. Boot Omarchy on a MacBook using the `bcm5974` trackpad driver.
2. Open the Super menu.
3. Select **Update → Hardware → Trackpad**.
4. Observe the floating terminal disappear immediately and the trackpad remain unchanged.
5. Run `omarchy-restart-trackpad` directly; it produces no output and exits 0.

## Expected behavior

One of:

- support resetting the detected `bcm5974` device safely;
- hide the recovery action when none of its supported driver paths exists; or
- retain the action but report clearly that this trackpad driver is unsupported and return a non-zero status.

## System details

- Omarchy: 4.0.2-1
- Kernel: 7.1.9-arch1-2
- Hardware: 2011 15-inch MacBook Pro
- Trackpad: Apple Internal Keyboard / Trackpad, USB ID `05ac:0246`
- Driver: `bcm5974`

## Related but distinct

#9190 covers `omarchy-hw-touchpad` failing to recognize the name `bcm5974`, which hides/breaks the touchpad enable/disable toggle. Fixing that detector does not fix this issue: the separately exposed `omarchy-restart-trackpad` action still only implements I2C/Intel reset paths.

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-09 10:19 UTC