Proof Portal

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

XPS 16 (Panther Lake, DA16260) capacitive function row emits no key events — Esc/F1–F12 dead

Reported by kaptivkapital · filed Jun 19, 2026 · open at source

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

XPS 16 (Panther Lake, DA16260) capacitive function row emits no key events — Esc/F1–F12 deadrevision 1 · captured 2026-09-28 21:29 UTC via poll

Machine: Dell XPS 16 DA16260 (Panther Lake)
Omarchy: 3.8.2 · Kernel: linux-ptl 7.0.9.arch1-1 (omarchy repo)

Symptom

The entire capacitive top row (Esc + F1–F12) produces no input whatsoever. The main keyboard works normally.

Cause

The capacitive-row HID device CUST0000:00 3558:2003 (0018:3558:2003.0002) is claimed by hid-multitouch and exposed purely as a pointer device:

N: Name="CUST0000:00 3558:2003"
P: Phys=i2c-CUST0000:00
H: Handlers=event11 mouse2
B: PROP=2          # POINTER
B: EV=1b
B: KEY=400 0 0 0 0 0   # BTN_LEFT only
B: ABS=660800001000003 # multitouch contacts

No key usages are exposed.

Tested

Unbound the device from hid-multitouch and bound it to hid-generic; tapping Esc/F-keys produces no events in libinput debug-events → the row exposes no key collection at all.
Only HID drivers present: hid-generic, hid-multitouch, hid-sensor-hub. No dedicated function-row driver.
BIOS FnLock attribute is present via dell-wmi-sysman (Disabled/Enabled) but has no effect, since the row emits nothing in any mode.
omarchy update did not bring a newer linux-ptl (still 7.0.9.arch1-1).

Ask

Is capacitive-row support for the Panther Lake XPS 16 (DA16260) planned for an upcoming linux-ptl build? Happy to test patched kernels and provide the HID report descriptor / additional diagnostics.

View raw text

**Machine:** Dell XPS 16 `DA16260` (Panther Lake)
**Omarchy:** 3.8.2 · **Kernel:** `linux-ptl 7.0.9.arch1-1` (omarchy repo)

### Symptom
The entire capacitive top row (Esc + F1–F12) produces no input whatsoever. The main keyboard works normally.

### Cause
The capacitive-row HID device `CUST0000:00 3558:2003` (`0018:3558:2003.0002`) is claimed by `hid-multitouch` and exposed purely as a pointer device:

```
N: Name="CUST0000:00 3558:2003"
P: Phys=i2c-CUST0000:00
H: Handlers=event11 mouse2
B: PROP=2          # POINTER
B: EV=1b
B: KEY=400 0 0 0 0 0   # BTN_LEFT only
B: ABS=660800001000003 # multitouch contacts
```

No key usages are exposed.

### Tested
- Unbound the device from `hid-multitouch` and bound it to `hid-generic`; tapping Esc/F-keys produces **no** events in `libinput debug-events` → the row exposes no key collection at all.
- Only HID drivers present: `hid-generic`, `hid-multitouch`, `hid-sensor-hub`. No dedicated function-row driver.
- BIOS `FnLock` attribute is present via `dell-wmi-sysman` (Disabled/Enabled) but has no effect, since the row emits nothing in any mode.
- `omarchy update` did not bring a newer `linux-ptl` (still `7.0.9.arch1-1`).

### Ask
Is capacitive-row support for the Panther Lake XPS 16 (`DA16260`) planned for an upcoming `linux-ptl` build? Happy to test patched kernels and provide the HID report descriptor / additional diagnostics.

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 03:53 UTC

Proof

History & reports

Reference