Proof Portal

Sign in
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-3862GitHub issuePublicReceived

tiny-dfr and t2fanrd services don't auto-start on Intel T2 Macs

Reported by dimitrieh · filed Dec 6, 2025Closed upstream on 2025-12-11 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

Open at source
Received and recorded verbatim. Nothing has been checked yet.

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?
Not yet mapped to any requirement or component.
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?
Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.

Original report

tiny-dfr and t2fanrd services don't auto-start on Intel T2 Macsrevision 1 · captured 2026-10-04 11:49 UTC via poll

Problem

On Intel T2 Macs, the Touch Bar (tiny-dfr) and fan control (t2fanrd) services don't work out of the box after installation. Users must manually configure them.

Issues:

  1. User not in video group - tiny-dfr needs access to /dev/dri/card* devices
  2. Services not enabled - Neither tiny-dfr.service nor t2fanrd.service are enabled during installation
  3. tiny-dfr service file incompatibility - The upstream service file has BindsTo= dependencies on Apple Silicon devices that don't exist on Intel T2 Macs

Current Workaround

Users must manually run:

sudo usermod -aG video $USER
sudo systemctl enable t2fanrd.service
sudo systemctl enable tiny-dfr.service
# Plus create a systemd drop-in override for tiny-dfr

Fixes

Upstream fix (tiny-dfr-arch package)

I've submitted a PR to fix the service file incompatibility:
https://github.com/NoaHimesaka1873/tiny-dfr-arch/pull/2

Omarchy fix

I've submitted a PR to add the missing setup steps to fix-apple-t2.sh:
- Add user to video group
- Enable t2fanrd.service
- Enable tiny-dfr.service

Affected Systems

  • MacBook Pro 16,1 (2019) - confirmed
  • Likely all Intel Macs with T2 chip and Touch Bar

Environment

  • Omarchy v3.x
  • linux-t2 6.17.7-1
  • tiny-dfr v0.3.5
View raw text
## Problem

On Intel T2 Macs, the Touch Bar (`tiny-dfr`) and fan control (`t2fanrd`) services don't work out of the box after installation. Users must manually configure them.

### Issues:

1. **User not in video group** - `tiny-dfr` needs access to `/dev/dri/card*` devices
2. **Services not enabled** - Neither `tiny-dfr.service` nor `t2fanrd.service` are enabled during installation
3. **tiny-dfr service file incompatibility** - The upstream service file has `BindsTo=` dependencies on Apple Silicon devices that don't exist on Intel T2 Macs

## Current Workaround

Users must manually run:
```bash
sudo usermod -aG video $USER
sudo systemctl enable t2fanrd.service
sudo systemctl enable tiny-dfr.service
# Plus create a systemd drop-in override for tiny-dfr
```

## Fixes

### Upstream fix (tiny-dfr-arch package)
I've submitted a PR to fix the service file incompatibility:
https://github.com/NoaHimesaka1873/tiny-dfr-arch/pull/2

### Omarchy fix
I've submitted a PR to add the missing setup steps to `fix-apple-t2.sh`:
- Add user to video group
- Enable t2fanrd.service
- Enable tiny-dfr.service

## Affected Systems

- MacBook Pro 16,1 (2019) - confirmed
- Likely all Intel Macs with T2 chip and Touch Bar

## Environment

- Omarchy v3.x
- linux-t2 6.17.7-1
- tiny-dfr v0.3.5

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.

No decision has been recorded yet.