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.
numlock_by_default silently breaks letter keys on old Apple Bluetooth keyboards (hid-apple numpad emulation)
Reported by roju · filed Sep 11, 2026Closed upstream on 2026-09-21 by bjarneo via an automated message, as a duplicate of #8912 (R-1277). GitHub close reason: completed.
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 4.0.3-1, Hyprland 0.56.2, Linux 7.2.3-arch1-3, Apple "Magic Keyboard" A1314 (pre-2015 Bluetooth, no physical numpad; Bus=0005 Vendor=05ac Product=0255)
What's wrong?
Pairing an old (pre-2015) Apple Bluetooth "Magic Keyboard" — one with no physical numeric keypad — and typing normally silently produces wrong characters on 8 keys:
| Key pressed | U | I | O | P | J | K | L | M |
|---|---|---|---|---|---|---|---|---|
| Typed | 4 | 5 | 6 | * | 1 | 2 | 3 | 0 |
All other letters are unaffected. This looks exactly like a wrong keyboard layout, but it isn't — it's a NumLock interaction.
Root cause: Omarchy's default hypr/input.lua sets numlock_by_default = true unconditionally for every keyboard. This specific class of old Apple keyboard has no numpad and no NumLock key/LED of its own, but Linux's hid-apple driver still implements Apple's numpad-emulation overlay for it (mirroring a macOS feature meant for numpad-less Macs), active only while NumLock is logically on for that input device. Because Omarchy forces NumLock on by default, and this hardware has no visible NumLock indicator or key to toggle it back off, the breakage is silent and (to the user) looks like a random layout bug rather than a NumLock state.
Steps to reproduce:
1. Pair an old Apple "Magic Keyboard" (Bluetooth, no numpad) with a fresh Omarchy install (default numlock_by_default = true).
2. Type u, i, o, p, j, k, l, or m.
3. Observe 4, 5, 6, *, 1, 2, 3, 0 instead.
Confirming diagnosis:
$ grep -A6 'Name="Magic Keyboard"' /proc/bus/input/devices
I: Bus=0005 Vendor=05ac Product=0255 Version=0050
N: Name="Magic Keyboard"
H: Handlers=sysrq kbd leds event3
$ cat /sys/class/leds/input28::numlock/brightness
1Setting that LED to 0 (e.g. pkexec sh -c 'echo 0 > /sys/class/leds/input28::numlock/brightness') immediately restores correct typing — until Omarchy's forced default reasserts it.
Workaround: override in ~/.config/hypr/input.lua:
hl.config({ input = { numlock_by_default = false } })Suggested fix: don't unconditionally force NumLock on for every keyboard. Options, roughly in order of invasiveness:
- Default numlock_by_default to false (matches most distros' out-of-the-box behavior; users who want NumLock-on-boot already know to opt in).
- Skip forcing NumLock for keyboards with no physical numpad (harder to detect generically, but this Apple keyboard family is a known, bounded set of hid-apple-driven product IDs).
- At minimum, document this interaction next to numlock_by_default in default/hypr/input.lua so the next person with this hardware doesn't lose an evening to what looks like a layout bug.
View raw text
### System details
Omarchy 4.0.3-1, Hyprland 0.56.2, Linux 7.2.3-arch1-3, Apple "Magic Keyboard" A1314 (pre-2015 Bluetooth, no physical numpad; Bus=0005 Vendor=05ac Product=0255)
### What's wrong?
Pairing an old (pre-2015) Apple Bluetooth "Magic Keyboard" — one with no physical numeric keypad — and typing normally silently produces wrong characters on 8 keys:
| Key pressed | U | I | O | P | J | K | L | M |
|---|---|---|---|---|---|---|---|---|
| Typed | 4 | 5 | 6 | * | 1 | 2 | 3 | 0 |
All other letters are unaffected. This looks exactly like a wrong keyboard layout, but it isn't — it's a NumLock interaction.
**Root cause:** Omarchy's default `hypr/input.lua` sets `numlock_by_default = true` unconditionally for every keyboard. This specific class of old Apple keyboard has no numpad and no NumLock key/LED of its own, but Linux's `hid-apple` driver still implements Apple's numpad-emulation overlay for it (mirroring a macOS feature meant for numpad-less Macs), active only while NumLock is logically on for that input device. Because Omarchy forces NumLock on by default, and this hardware has no visible NumLock indicator or key to toggle it back off, the breakage is silent and (to the user) looks like a random layout bug rather than a NumLock state.
**Steps to reproduce:**
1. Pair an old Apple "Magic Keyboard" (Bluetooth, no numpad) with a fresh Omarchy install (default `numlock_by_default = true`).
2. Type `u`, `i`, `o`, `p`, `j`, `k`, `l`, or `m`.
3. Observe `4`, `5`, `6`, `*`, `1`, `2`, `3`, `0` instead.
**Confirming diagnosis:**
```
$ grep -A6 'Name="Magic Keyboard"' /proc/bus/input/devices
I: Bus=0005 Vendor=05ac Product=0255 Version=0050
N: Name="Magic Keyboard"
H: Handlers=sysrq kbd leds event3
$ cat /sys/class/leds/input28::numlock/brightness
1
```
Setting that LED to `0` (e.g. `pkexec sh -c 'echo 0 > /sys/class/leds/input28::numlock/brightness'`) immediately restores correct typing — until Omarchy's forced default reasserts it.
**Workaround:** override in `~/.config/hypr/input.lua`:
```lua
hl.config({ input = { numlock_by_default = false } })
```
**Suggested fix:** don't unconditionally force NumLock on for every keyboard. Options, roughly in order of invasiveness:
- Default `numlock_by_default` to `false` (matches most distros' out-of-the-box behavior; users who want NumLock-on-boot already know to opt in).
- Skip forcing NumLock for keyboards with no physical numpad (harder to detect generically, but this Apple keyboard family is a known, bounded set of `hid-apple`-driven product IDs).
- At minimum, document this interaction next to `numlock_by_default` in `default/hypr/input.lua` so the next person with this hardware doesn't lose an evening to what looks like a layout bug.
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.