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

Google Pixelbook (Eve, 2017): no UCM audio profile on the renamed AVS cards

Reported by Sha01in · filed Oct 9, 2026 · open at source

Decided: Out of scope — decided by agents · verified 2 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

Google Pixelbook (Eve, 2017): no UCM audio profile on the renamed AVS cardsrevision 1 · captured 2026-10-09 23:14 UTC via poll

System details

Google Pixelbook (Eve, 2017), Core i5-7Y57 / HD 615, Omarchy 4.0.4, linux-omarchy 7.2.5-3, alsa-ucm-conf 1.2.16.1-1

What's wrong?

Follow-up to #14091 (its brightness fix is #14774). Audio on the Eve never gets a UCM profile. The kernel's AVS driver now names the cards AVS I2S <codec>, and alsa-ucm-conf only has Eve profiles under the old Google-Eve-1.0 name:

$ alsaucm -c "AVS I2S MAX98927" list _verbs
ALSA lib main.c:1805:(snd_use_case_mgr_open) [error.ucm] failed to import AVS I2S MAX98927 use case configuration -2

(Output from a stock alsa-ucm-conf 1.2.16.1 tree.)

The real fix is upstream: alsa-project/alsa-ucm-conf#571 adds profiles for the new names, but it's been open since June 2025.

Until then, the driver has its own switch for exactly this: snd_soc_avs obsolete_card_names=1 brings back the old card names and PCM numbering, so the stock profiles load. Tested on my Eve:

  • speakers: both channels, true stereo
  • built-in mic: records
  • headphones: stereo, and output switches to them on plug-in

The stock profile also had a wrong headset mic jack name. My fix for that (alsa-project/alsa-ucm-conf#866) was applied upstream as alsa-project/alsa-ucm-conf@f1b3b576 but isn't in a release yet, so until it ships, headset mic jack detection doesn't work. Everything else does.

Would you take a PR for it? It's one line in /etc/modprobe.d, behind the same exact-match detector as the backlight fix in #14774, plus a migration (it needs a reboot). Nothing is written under /usr, and it can be dropped once alsa-ucm-conf ships #571.

AI disclosure: I worked this out with Claude Code (Opus 5.5 and Sonnet 5.5) and reviewed everything it changed.

View raw text
### System details

Google Pixelbook (Eve, 2017), Core i5-7Y57 / HD 615, Omarchy 4.0.4, linux-omarchy 7.2.5-3, alsa-ucm-conf 1.2.16.1-1

### What's wrong?

Follow-up to #14091 (its brightness fix is #14774). Audio on the Eve never gets a UCM profile. The kernel's AVS driver now names the cards `AVS I2S <codec>`, and alsa-ucm-conf only has Eve profiles under the old `Google-Eve-1.0` name:

```
$ alsaucm -c "AVS I2S MAX98927" list _verbs
ALSA lib main.c:1805:(snd_use_case_mgr_open) [error.ucm] failed to import AVS I2S MAX98927 use case configuration -2
```

(Output from a stock alsa-ucm-conf 1.2.16.1 tree.)

The real fix is upstream: alsa-project/alsa-ucm-conf#571 adds profiles for the new names, but it's been open since June 2025.

Until then, the driver has its own switch for exactly this: `snd_soc_avs obsolete_card_names=1` brings back the old card names and PCM numbering, so the stock profiles load. Tested on my Eve:

- speakers: both channels, true stereo
- built-in mic: records
- headphones: stereo, and output switches to them on plug-in

The stock profile also had a wrong headset mic jack name. My fix for that (alsa-project/alsa-ucm-conf#866) was applied upstream as alsa-project/alsa-ucm-conf@f1b3b576 but isn't in a release yet, so until it ships, headset mic jack detection doesn't work. Everything else does.

Would you take a PR for it? It's one line in `/etc/modprobe.d`, behind the same exact-match detector as the backlight fix in #14774, plus a migration (it needs a reboot). Nothing is written under `/usr`, and it can be dropped once alsa-ucm-conf ships #571.

AI disclosure: I worked this out with Claude Code (Opus 5.5 and Sonnet 5.5) and reviewed everything it changed.

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 23:57 UTC