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?

AreaPartly in the audited arealock· 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?

Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. So far: partly in the audited area (lock) — decided by agents · verified. The outcome (valid, duplicate, not a bug, …) is not decided yet. See the decision.

Original report

### System details

Victus by HP Gaming Laptop 16-s0xxx, Omarchy 3.1.3

### What's wrong?

When I boot computer, numlock is always off. I must press numlock key manualy to turn on. It not remember. I have set `numlock_by_default = true` on input.conf but it seems doesn't working.

Second problem is after suspend. When pc wake up, the numlock not working. I must press numlock key OFF, and then press numlock key ON again. After this toggle, it working. But this is every time after suspend.

Edit:

I was wrong. The problem is only on the lockscreen.

Numlock is OFF on the lockscreen (after boot and after suspend). Numlock is ON after I login to system.

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.