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.
USB autosuspend modprobe config is ignored (usbcore built into kernel)
Reported by mabster · filed Aug 10, 2026Closed upstream on 2026-08-11 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
Omarchy 3.8.4 but also Quattro
What's wrong?
(Full disclosure - an LLM wrote this issue based on my conversation history with it. Confirmed on the Discord that I'm not the only person seeing the behaviour.)
The current codebase includes a configuration file under /etc/modprobe.d/ to disable USB autosuspend. However, this file is entirely ignored by the system because usbcore is built statically into the kernel rather than compiled as a loadable module (m).
Modprobe files are only parsed for external modules, so this setting never applies to built-in kernel components.
USB autosuspend remains enabled by default. This can cause target USB devices (such as keyboards, mice, or storage drives) to sleep, lag, or drop connections unexpectedly during periods of inactivity.
Suggested Fixes
This can be resolved in one of two ways:
Kernel Command Line:
Append usbcore.autosuspend=-1 to the bootloader/Limine kernel arguments.
Udev Rule:
Replace the modprobe file with a runtime udev rule (e.g., /etc/udev/rules.d/50-usb-autosuspend.rules) containing:
ACTION=="add", SUBSYSTEM=="usb", ATTR{power/control}="on"
I'm not sure if this is a real issue, but it seems like the modprobe.d file was created in an attempt to disable USB autosuspend, so if that was the intent, it doesn't seem to be working.
View raw text
### System details
Omarchy 3.8.4 but also Quattro
### What's wrong?
(Full disclosure - an LLM wrote this issue based on my conversation history with it. Confirmed on the Discord that I'm not the only person seeing the behaviour.)
The current codebase includes a configuration file under /etc/modprobe.d/ to disable USB autosuspend. However, this file is entirely ignored by the system because usbcore is built statically into the kernel rather than compiled as a loadable module (m).
Modprobe files are only parsed for external modules, so this setting never applies to built-in kernel components.
USB autosuspend remains enabled by default. This can cause target USB devices (such as keyboards, mice, or storage drives) to sleep, lag, or drop connections unexpectedly during periods of inactivity.
**Suggested Fixes**
This can be resolved in one of two ways:
Kernel Command Line:
Append usbcore.autosuspend=-1 to the bootloader/Limine kernel arguments.
Udev Rule:
Replace the modprobe file with a runtime udev rule (e.g., /etc/udev/rules.d/50-usb-autosuspend.rules) containing:
`ACTION=="add",` SUBSYSTEM=="usb", ATTR{power/control}="on"
I'm not sure if this is a real issue, but it seems like the modprobe.d file was created in an attempt to disable USB autosuspend, so if that was the intent, it doesn't seem to be working.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.
No decision has been recorded yet.