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-3209GitHub issuePublicReceived

Studio Display brightness not working / asdcontrol not present on a fresh install

Reported by miharekar · filed Oct 7, 2025Closed upstream on 2025-10-07 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

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

Studio Display brightness not working / asdcontrol not present on a fresh installrevision 1 · captured 2026-10-04 11:35 UTC via poll

System details

Framework Desktop, Omarchy 3.0.2

What's wrong?

I got my Framework Desktop yesterday and after fiddling around this awesome new env, one thing that didn't work was brightness control on my Studio Display. First I thought it's the keyboard keys not being mapped correctly (F keys vs media keys) because if I called asdcontrol directly, it all worked fine.

But then after spending some time in omarchy github, I saw that this expects /usr/local/bin/asdcontrol
to be there which it wasn't for me on a fresh install. Once I added ln -s the brightness keys started working.

Not sure what went wrong for me and/or if I'm missing any other symlinks / executables there.

This is what I have:

~ ❯ ls /usr/local/bin/
Permissions Size User      Date Modified Name
lrwxrwxrwx     - root       7 Oct 08:19  󰡯 asdcontrol -> /usr/bin/asdcontrol
.rwxr-xr-x   530 root       6 Oct 15:55  󰡯 mkinitcpio
.rwxr-xr-x   16k miharekar  6 Oct 07:39  󰡯 seamless-login
View raw text
### System details

Framework Desktop, Omarchy 3.0.2

### What's wrong?

I got my Framework Desktop yesterday and after fiddling around this awesome new env, one thing that didn't work was brightness control on my Studio Display. First I thought it's the keyboard keys not being mapped correctly (F keys vs media keys) because if I called `asdcontrol` directly, it all worked fine.

But then after spending some time in omarchy github, I saw that [this](https://github.com/basecamp/omarchy/blob/master/install/config/sudoless-asdcontrol.sh#L2) expects `/usr/local/bin/asdcontrol`
to be there which it wasn't for me on a fresh install. Once I added `ln -s` the brightness keys started working.

Not sure what went wrong for me and/or if I'm missing any other symlinks / executables there.

This is what I have:

```
~ ❯ ls /usr/local/bin/
Permissions Size User      Date Modified Name
lrwxrwxrwx     - root       7 Oct 08:19  󰡯 asdcontrol -> /usr/bin/asdcontrol
.rwxr-xr-x   530 root       6 Oct 15:55  󰡯 mkinitcpio
.rwxr-xr-x   16k miharekar  6 Oct 07:39  󰡯 seamless-login
```

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.