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

Touchpad right-click stops working after 4.0 update

Reported by ohai89 · 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

Touchpad right-click stops working after 4.0 updaterevision 1 · captured 2026-09-28 21:29 UTC via poll

System details

Omarchy 4.0.0, Hyprland 0.56 (Lua config) Touchpad: SNSL0028:00 2C2F:0028 (Framework), i2c

What's wrong?

After updating from an earlier Omarchy version (with the old .conf-based Hyprland config) to 4.0.0, touchpad right-click stopped working entirely — neither two-finger tap/click nor lower-right-corner click registered as right-click in any app (tested in Chromium, Thunderbird, Ghostty, GTK apps).

My old ~/.config/hypr/input.conf had clickfinger_behavior commented out:

touchpad {
  # Use two-finger clicks for right-click instead of lower-right corner
  # clickfinger_behavior = true
  scroll_factor = 0.4
}

This relied on Hyprland's old .conf parser default, which worked correctly (right-click via the lower-right corner zone).

The 4.0 migration correctly converted this file to the new Lua format, preserving the same commented-out state:

touchpad = {
    -- Use two-finger clicks for right-click instead of lower-right corner.
    -- clickfinger_behavior = true,
    scroll_factor = 0.4,
},

With it left unset in the new Lua config, right-click doesn't work at all — not via corner-click, not via two-finger tap. libinput list-devices correctly reports button-areas as the active click method and libinput debug-events confirms BTN_RIGHT events are being emitted by the touchpad correctly. So this isn't a libinput/hardware detection issue — the button press is reaching libinput fine, it's just not resulting in a working right-click at the Hyprland/app level unless clickfinger_behavior is explicitly set (to either true or false) in the Lua config.

Steps to reproduce
- Have an existing Omarchy install with clickfinger_behavior left at its commented-out default in input.conf
- Update to 4.0.0 (Lua config migration runs)
- Right-click via lower-right touchpad corner — nothing happens
- Explicitly set clickfinger_behavior = true (or false) in input.lua, reload — right-click works again
- Expected behavior

Leaving clickfinger_behavior commented out/unset in the Lua config should preserve the same working default behavior it had under the old .conf format (right-click available via corner click), since this is the state most existing users were migrated into.

Suggested fix

Either:

Set an explicit default value for clickfinger_behavior somewhere in Omarchy's default.hypr.input module so an unset value in the user's input.lua doesn't leave the click method effectively broken, or
Have the 4.0 migration explicitly uncomment/set clickfinger_behavior = false (matching old corner-click behavior) in generated input.lua files for users who had it unset

This seems likely to affect most people upgrading from pre-4.0 Omarchy who never touched this setting, since it's shipped commented out by default.

View raw text
### System details

Omarchy 4.0.0, Hyprland 0.56 (Lua config) Touchpad: SNSL0028:00 2C2F:0028 (Framework), i2c

### What's wrong?

After updating from an earlier Omarchy version (with the old .conf-based Hyprland config) to 4.0.0, touchpad right-click stopped working entirely — neither two-finger tap/click nor lower-right-corner click registered as right-click in any app (tested in Chromium, Thunderbird, Ghostty, GTK apps).

My old `~/.config/hypr/input.conf` had `clickfinger_behavior` commented out:

```
touchpad {
  # Use two-finger clicks for right-click instead of lower-right corner
  # clickfinger_behavior = true
  scroll_factor = 0.4
}
```

This relied on Hyprland's old .conf parser default, which worked correctly (right-click via the lower-right corner zone).

The 4.0 migration correctly converted this file to the new Lua format, preserving the same commented-out state:

```lua
touchpad = {
    -- Use two-finger clicks for right-click instead of lower-right corner.
    -- clickfinger_behavior = true,
    scroll_factor = 0.4,
},
```

With it left unset in the new Lua config, right-click doesn't work at all — not via corner-click, not via two-finger tap. libinput list-devices correctly reports button-areas as the active click method and `libinput` debug-events confirms `BTN_RIGHT` events are being emitted by the touchpad correctly. So this isn't a libinput/hardware detection issue — the button press is reaching libinput fine, it's just not resulting in a working right-click at the Hyprland/app level unless `clickfinger_behavior` is explicitly set (to either true or false) in the Lua config.

Steps to reproduce
- Have an existing Omarchy install with clickfinger_behavior left at its commented-out default in input.conf
- Update to 4.0.0 (Lua config migration runs)
- Right-click via lower-right touchpad corner — nothing happens
- Explicitly set clickfinger_behavior = true (or false) in input.lua, reload — right-click works again
- Expected behavior

Leaving clickfinger_behavior commented out/unset in the Lua config should preserve the same working default behavior it had under the old .conf format (right-click available via corner click), since this is the state most existing users were migrated into.

Suggested fix

Either:

Set an explicit default value for clickfinger_behavior somewhere in Omarchy's default.hypr.input module so an unset value in the user's input.lua doesn't leave the click method effectively broken, or
Have the 4.0 migration explicitly uncomment/set clickfinger_behavior = false (matching old corner-click behavior) in generated input.lua files for users who had it unset

This seems likely to affect most people upgrading from pre-4.0 Omarchy who never touched this setting, since it's shipped commented out by default.

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:06 UTC