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

Installer: Scroll Lock backlight can lock input on SINO WEALTH 258a:0001 keyboards

Reported by EmpireOperating · filed Aug 15, 2026 · 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

Installer: Scroll Lock backlight can lock input on SINO WEALTH 258a:0001 keyboardsrevision 1 · captured 2026-09-28 21:29 UTC via poll

Summary

On an Alienware Aurora R16 with a SINO WEALTH USB keyboard (258a:0001), pressing the keyboard backlight key at the ISO installer's initial “Press Return to Start Setup” screen leaves keyboard input unusable. A hard reboot is required.

The backlight control is implemented as the keyboard's Scroll Lock LED. The problem reproduced twice during installation: the first press at the initial screen appeared to freeze the installer; after rebooting and progressing further, pressing the same key again produced the same input lockup. Pressing Return and completing setup without using that key worked normally.

Why this appears installer-specific

This happens in the ISO/live virtual-console environment, before the installed system and Hyprland configuration are available. Once installed, the keyboard works normally with the standard XKB option:

scrolllock:mod3

That option allows Hyprland to keep the Scroll Lock LED state synchronized, which is needed for this keyboard's backlight.

Related upstream behavior

This exact USB ID is tracked by the Linux kernel as bug 211679: HID: 258a:0001 SINO WEALTH USB KEYBOARD SCRLK/backlight button not work. Similar reports describe a Scroll Lock-wired backlight freezing keyboard input in an Arch live environment.

Impact

At a prompt that tells users to press Return, pressing an adjacent/non-obvious hardware backlight key can make the installer look completely frozen and force a reboot. There is no useful persistent log after a hard reboot from the live environment.

Proposed mitigation

For the installer console only, detect USB 258a:0001 and overlay a minimal console keymap that maps Scroll Lock (keycode 70) to VoidSymbol. This would make the problematic key a harmless no-op during setup without changing normal desktop behavior after installation.

At minimum, a known-hardware warning or installer documentation would prevent a confusing hard-reboot failure.

Environment

  • Machine: Alienware Aurora R16
  • Keyboard USB ID: 258a:0001 (SINO WEALTH USB KEYBOARD)
  • Installed Omarchy package after the successful retry: 4.0.0-1
View raw text
## Summary

On an Alienware Aurora R16 with a SINO WEALTH USB keyboard (`258a:0001`), pressing the keyboard backlight key at the ISO installer's initial **“Press Return to Start Setup”** screen leaves keyboard input unusable. A hard reboot is required.

The backlight control is implemented as the keyboard's Scroll Lock LED. The problem reproduced twice during installation: the first press at the initial screen appeared to freeze the installer; after rebooting and progressing further, pressing the same key again produced the same input lockup. Pressing Return and completing setup without using that key worked normally.

## Why this appears installer-specific

This happens in the ISO/live virtual-console environment, before the installed system and Hyprland configuration are available. Once installed, the keyboard works normally with the standard XKB option:

```
scrolllock:mod3
```

That option allows Hyprland to keep the Scroll Lock LED state synchronized, which is needed for this keyboard's backlight.

## Related upstream behavior

This exact USB ID is tracked by the Linux kernel as [bug 211679](https://bugzilla.kernel.org/show_bug.cgi?id=211679): `HID: 258a:0001 SINO WEALTH USB KEYBOARD SCRLK/backlight button not work`. Similar reports describe a Scroll Lock-wired backlight freezing keyboard input in an Arch live environment.

## Impact

At a prompt that tells users to press Return, pressing an adjacent/non-obvious hardware backlight key can make the installer look completely frozen and force a reboot. There is no useful persistent log after a hard reboot from the live environment.

## Proposed mitigation

For the installer console only, detect USB `258a:0001` and overlay a minimal console keymap that maps Scroll Lock (`keycode 70`) to `VoidSymbol`. This would make the problematic key a harmless no-op during setup without changing normal desktop behavior after installation.

At minimum, a known-hardware warning or installer documentation would prevent a confusing hard-reboot failure.

## Environment

- Machine: Alienware Aurora R16
- Keyboard USB ID: `258a:0001` (`SINO WEALTH USB KEYBOARD`)
- Installed Omarchy package after the successful retry: `4.0.0-1`

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 04:07 UTC