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

bug: Internal keyboard key repeat loop and severe input delay on AMD Ryzen 5 laptop

Reported by carefullyza-afk · filed Jun 11, 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

bug: Internal keyboard key repeat loop and severe input delay on AMD Ryzen 5 laptoprevision 1 · captured 2026-09-28 21:29 UTC via poll

System details

Laptop Axioo AMD Ryzan 5 5500u

What's wrong?

Description

A severe keyboard input issue occurs on an internal laptop keyboard using Omarchy OS. The keyboard randomly suffers from a perpetual key repeat loop (spamming characters endlessly) combined with an extreme input delay/lag on the initial keypress.

Adjusting the repeat_rate and repeat_delay inside hypr/input.conf does not solve the problem; lowering the repeat configuration to zero stops the spamming but triggers an unusable typing delay, while standard rates cause immediate character looping. This behavior indicates a synthetic key event synchronization bug or buffer queue deadlock within the input subsystem handling on certain AMD Ryzen laptop platforms.

Hardware Environment

  • Laptop Brand/Model: Axioo (Mybook Hype 5 series)
  • CPU: AMD Ryzen 5
  • Keyboard Type: Internal Laptop Keyboard

Software Environment

  • OS: Omarchy OS
  • Display Server/Compositor: Hyprland (Wayland-based)
  • Input Driver: libinput / xkb

Steps to Reproduce

  1. Open any terminal or text editor on Omarchy OS.
  2. Press and release any key on the internal laptop keyboard.
  3. The system either fails to register the keypress immediately (severe delay) or gets stuck in a loop, spamming the character endlessly until a hardware reset or configuration reload.

Expected Behavior

The internal keyboard should register keypresses instantly with normal responsiveness, and release key events promptly without entering an infinite repetition loop.

Additional Context & Troubleshooting Attempted

  • Tested with an external USB keyboard, which works perfectly fine without any delay or looping issues. The issue is strictly isolated to the internal laptop keyboard handling.
  • Attempted to modify input.conf values (repeat_delay = 0 / repeat_rate = 0), which successfully suppressed the looping but caused severe latency on the first keystroke.
  • Resetting the input.conf back to the default Omarchy configuration (repeat_delay = 600, repeat_rate = 40) brings back the combination of heavy lag followed by an uncontrollable character spam loop.
View raw text
### System details

Laptop Axioo AMD Ryzan 5 5500u 

### What's wrong?

### Description
A severe keyboard input issue occurs on an internal laptop keyboard using Omarchy OS. The keyboard randomly suffers from a perpetual key repeat loop (spamming characters endlessly) combined with an extreme input delay/lag on the initial keypress. 

Adjusting the `repeat_rate` and `repeat_delay` inside `hypr/input.conf` does not solve the problem; lowering the repeat configuration to zero stops the spamming but triggers an unusable typing delay, while standard rates cause immediate character looping. This behavior indicates a synthetic key event synchronization bug or buffer queue deadlock within the input subsystem handling on certain AMD Ryzen laptop platforms.

### Hardware Environment
- **Laptop Brand/Model:** Axioo (Mybook Hype 5 series)
- **CPU:** AMD Ryzen 5
- **Keyboard Type:** Internal Laptop Keyboard

### Software Environment
- **OS:** Omarchy OS
- **Display Server/Compositor:** Hyprland (Wayland-based)
- **Input Driver:** libinput / xkb

### Steps to Reproduce
1. Open any terminal or text editor on Omarchy OS.
2. Press and release any key on the internal laptop keyboard.
3. The system either fails to register the keypress immediately (severe delay) or gets stuck in a loop, spamming the character endlessly until a hardware reset or configuration reload.

### Expected Behavior
The internal keyboard should register keypresses instantly with normal responsiveness, and release key events promptly without entering an infinite repetition loop.

### Additional Context & Troubleshooting Attempted
- Tested with an **external USB keyboard**, which works **perfectly fine** without any delay or looping issues. The issue is strictly isolated to the internal laptop keyboard handling.
- Attempted to modify `input.conf` values (`repeat_delay = 0` / `repeat_rate = 0`), which successfully suppressed the looping but caused severe latency on the first keystroke.
- Resetting the `input.conf` back to the default Omarchy configuration (`repeat_delay = 600`, `repeat_rate = 40`) brings back the combination of heavy lag followed by an uncontrollable character spam loop.

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 03:52 UTC