Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA 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.
[BUG] Input Device Flood / Infinite Loop caused by Makima
Reported by pussilemon · filed Mar 9, 2026Closed upstream on 2026-07-18 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
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
System details
Laptop ASUS TUF FX505DU with AMD Ryzen 7 3750H and NVIDIA GTX 1660 Ti Omarchy v3.4.2
What's wrong?
On certain hardware (specifically ASUS TUF FX505DU with AMD Ryzen 7 3750H and NVIDIA GTX 1660 Ti), the makima service/udev rules trigger an infinite loop of virtual input device creation. This leads to a system-wide "freeze" where local mouse and keyboard stop responding due to CPU/Input subsystem overhead, although the system remains reachable via SSH.
I have been using a custom key remap (Caps Lock to Escape) for a long time without any issues. This
configuration worked perfectly on previous versions of Omarchy/Makima.
To Reproduce
Steps to reproduce the behavior:
1)Boot Omarchy on an ASUS TUF series laptop.
2) Observe dmesg logs.
3) Every 4 seconds, new virtual devices are created (e.g., Makima Virtual Keyboard/Mouse as /devices/virtual/input/inputX).
4)The input ID (input50, input51, etc.) increments indefinitely until the UI freezes.
Logs / Screenshots
dmesg output during the loop:
[ 66.057374] input: Makima Virtual Keyboard/Mouse as /devices/virtual/input/input47
[ 66.057575] input: Makima Virtual Pointer as /devices/virtual/input/input48
[ 66.057769] input: Makima Virtual Pen/Tablet as /devices/virtual/input/input49
[ 70.056753] input: Makima Virtual Keyboard/Mouse as /devices/virtual/input/input50
[ 70.056955] input: Makima Virtual Pointer as /devices/virtual/input/input51
[ 70.057164] input: Makima Virtual Pen/Tablet as /devices/virtual/input/input52
Workaround found
The issue was resolved by:
1) Disabling the udev rule: mv /etc/udev/rules.d/50-makima.rules /etc/udev/rules.d/50-makima.rules.bak
2)Disabling the service: systemctl disable --now makima
3) Reloading udev: udevadm control --reload-rules && udevadm trigger
View raw text
### System details
Laptop ASUS TUF FX505DU with AMD Ryzen 7 3750H and NVIDIA GTX 1660 Ti Omarchy v3.4.2
### What's wrong?
On certain hardware (specifically ASUS TUF FX505DU with AMD Ryzen 7 3750H and NVIDIA GTX 1660 Ti), the makima service/udev rules trigger an infinite loop of virtual input device creation. This leads to a system-wide "freeze" where local mouse and keyboard stop responding due to CPU/Input subsystem overhead, although the system remains reachable via SSH.
I have been using a custom key remap (Caps Lock to Escape) for a long time without any issues. This
configuration worked perfectly on previous versions of Omarchy/Makima.
To Reproduce
Steps to reproduce the behavior:
1)Boot Omarchy on an ASUS TUF series laptop.
2) Observe dmesg logs.
3) Every 4 seconds, new virtual devices are created (e.g., Makima Virtual Keyboard/Mouse as /devices/virtual/input/inputX).
4)The input ID (input50, input51, etc.) increments indefinitely until the UI freezes.
Logs / Screenshots
dmesg output during the loop:
[ 66.057374] input: Makima Virtual Keyboard/Mouse as /devices/virtual/input/input47
[ 66.057575] input: Makima Virtual Pointer as /devices/virtual/input/input48
[ 66.057769] input: Makima Virtual Pen/Tablet as /devices/virtual/input/input49
[ 70.056753] input: Makima Virtual Keyboard/Mouse as /devices/virtual/input/input50
[ 70.056955] input: Makima Virtual Pointer as /devices/virtual/input/input51
[ 70.057164] input: Makima Virtual Pen/Tablet as /devices/virtual/input/input52
Workaround found
The issue was resolved by:
1) Disabling the udev rule: mv /etc/udev/rules.d/50-makima.rules /etc/udev/rules.d/50-makima.rules.bak
2)Disabling the service: systemctl disable --now makima
3) Reloading udev: udevadm control --reload-rules && udevadm triggerValidation
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.