Proof Portal

Sign in
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-2661GitHub issuePublicReceived

[Omarchy 2.0] keyboard shortcuts not work after upgrade

Reported by grumpydumpty · filed Aug 27, 2025Closed upstream on 2025-08-28 by its own reporter grumpydumpty. GitHub close reason: completed. Closed by its own reporter — not by itself evidence of a fix.

Open at source
Received and recorded verbatim. Nothing has been checked yet.

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

[Omarchy 2.0] keyboard shortcuts not work after upgraderevision 1 · captured 2026-10-04 11:27 UTC via poll

TL:DR;

Just upgraded to latest Omarchy 2.0.1 from (vanilla v1.4.1) and it didn't go well.

Is there a way to force Omarchy (and the system) to forget previous settings for browser, shell, etc and update to ones provided by Omarchy 2.0.1?

Background

Install seemed to go well, however post-reboot there are a number of shortcuts that appear broken:

  • super + return
  • super + space
  • super + b
  • super + alt + space

Kind of annoying as need super + enter and super + space are so key to getting a shell to troubleshooting and dig into issue.

Tracing through ~/.config/hypr/bindings.conf found the following:

  1. For super + return, running uwsm app -- alacritty --working-directory $(~/.local/share/omarchy/bin/moarchy-cmd-terminal-cwd) launches correctly so I am not sure why the binding isn't working.
  2. For super + space, there is no walker file/binary on the system.
  3. For super + b, it appears system thinks chromium is the browser but it looks to have been removed. Running ~/.local/share/omarchy/bin/moarchy-launch-browser returns path /usr/bin/chromium not found. The above uses xdg-settings and running xdg-settings get default-browser returns /usr/bin/chromium

This is a new system, setup in July (when v1.4.1 was latest) and this is my first Omarchy upgrade - I can blow it away and start again but was hoping there a way to force omarchy (and the system) to forget previous settings for browser, shell, etc and update to ones provided by Omarchy 2.0.1.

Any help would be appreciated.

View raw text
## TL:DR;

Just upgraded to latest Omarchy 2.0.1 from (vanilla v1.4.1) and it didn't go well.

Is there a way to force Omarchy (and the system) to forget previous settings for browser, shell, etc and update to ones provided by Omarchy 2.0.1?

## Background

Install seemed to go well, however post-reboot there are a number of shortcuts that appear broken:

- `super` + `return`
- `super` + `space`
- `super` + `b`
- `super` + `alt` + `space`

Kind of annoying as need `super` + `enter` and `super` + `space` are so key to getting a shell to troubleshooting and dig into issue.

Tracing through `~/.config/hypr/bindings.conf` found the following:

1. For `super` + `return`, running `uwsm app -- alacritty --working-directory $(~/.local/share/omarchy/bin/moarchy-cmd-terminal-cwd)` launches correctly so I am not sure why the binding isn't working.
1. For `super` + `space`, there is no `walker` file/binary on the system.
1. For `super` + `b`, it appears system thinks chromium is the browser but it looks to have been removed. Running `~/.local/share/omarchy/bin/moarchy-launch-browser` returns path `/usr/bin/chromium` not found. The above uses `xdg-settings` and running `xdg-settings get default-browser` returns `/usr/bin/chromium`

This is a new system, setup in July (when v1.4.1 was latest) and this is my first Omarchy upgrade - I can blow it away and start again but was hoping there a way to force omarchy (and the system) to forget previous settings for browser, shell, etc and update to ones provided by Omarchy 2.0.1.

Any help would be appreciated.

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.