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

Hyperland config error: group:col.border_locked_* = -1 is invalid gradient/color

Reported by robert-matusewicz · filed May 14, 2026Closed upstream on 2026-05-14 by its own reporter robert-matusewicz. GitHub close reason: completed. Closed by its own reporter — not by itself 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

Hyperland config error: group:col.border_locked_* = -1 is invalid gradient/colorrevision 1 · captured 2026-10-04 11:56 UTC via poll

System details

Omarchy 3.8.0, 7.0.5-arch1-1m hyperland 0.55.0

What's wrong?

After updating to Omarchy 3.8.0, I see config errors:

default/hypr/looknfeel.conf at line 53: Error parsing gradient: -1: failed to parse -1 as color
default/hypr/looknfeel.conf at line 54: Error parsing gradient: -1: failed to parse -1 as color

The problem lines are:

group {
  col.border_active = $activeBorderColor
  col.border_inactive = $inactiveBorderColor
  col.border_locked_active = -1
  col.border_locked_inactive = -1
}

Those should be gradient values, not integer ones.

The suggested fix I have is:

group {
   ...
   col.border_locked_active = $activeBorderColor
   col.border_locked_inactive = $inactiveBorderColor
}

On my env, this at least got rid of the config errors, but I am not sure it's good to have the same colors for locked groups, as they won't be distinct.

View raw text
### System details

Omarchy 3.8.0, 7.0.5-arch1-1m hyperland 0.55.0

### What's wrong?

After updating to Omarchy 3.8.0, I see config errors:

```
default/hypr/looknfeel.conf at line 53: Error parsing gradient: -1: failed to parse -1 as color
default/hypr/looknfeel.conf at line 54: Error parsing gradient: -1: failed to parse -1 as color
```

The problem lines are:
```
group {
  col.border_active = $activeBorderColor
  col.border_inactive = $inactiveBorderColor
  col.border_locked_active = -1
  col.border_locked_inactive = -1
}
```

Those should be gradient values, not integer ones.

The suggested fix I have is:
```
group {
   ...
   col.border_locked_active = $activeBorderColor
   col.border_locked_inactive = $inactiveBorderColor
}
```

On my env, this at least got rid of the config errors, but I am not sure it's good to have the same colors for locked groups, as they won't be distinct.

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

  • Related PRpr/13565· confirmed

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.