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

Shell segfaults (SIGSEGV) in hot-reload when plugin update replaces a plugin's files

Reported by tymurbogach · filed Sep 22, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 3 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

Shell segfaults (SIGSEGV) in hot-reload when plugin update replaces a plugin's filesrevision 1 · captured 2026-09-28 21:23 UTC via poll

The shell crashed with signal 11 while omarchy plugin update moved a plugin's git checkout underneath the live file watcher.

Repro:

  1. Have a third-party bar widget installed and enabled.
  2. Run omarchy plugin update <id> (or the plugin's own update button, which calls it) when the remote has new commits.
  3. The inotify watcher fires one localPluginChanged per file written by git merge --ff-only (6 events in my log), the 150 ms debounce fires reloadPlugins(), and the shell segfaults while recreating the component.

Versions: Quickshell 0.3.1 (Arch), Qt 6.11.2, Omarchy 4.0.4. Plugin update was io.github.tymurbogach.hardwarchy 2.3.1 -> 2.3.2, but the plugin is incidental: the stack dies in __dynamic_cast -> QQmlObjectCreator::finalize -> QQmlComponent::createObject, i.e. in the platform recreate path, not in plugin JS/QML (which passed qmllint and runs fine after restart).

Log tail (from the crash dir):

Local plugin changed, reloading: io.github.tymurbogach.hardwarchy  (x6, same second)

Full crash dir available on request (report.txt + log.qslog.log, run id xogy3qsqlt).

Impact: cosmetic but scary. The shell restarts itself, the update completes (HEAD moved, validation passed), and user prefs survive. Still, every plugin update on every machine can flash-crash the desktop. A debounce that waits for write quiescence, or suspending the watcher while plugin update runs, would close the window.

View raw text
The shell crashed with signal 11 while `omarchy plugin update` moved a plugin's git checkout underneath the live file watcher.

Repro:

1. Have a third-party bar widget installed and enabled.
2. Run `omarchy plugin update <id>` (or the plugin's own update button, which calls it) when the remote has new commits.
3. The inotify watcher fires one `localPluginChanged` per file written by `git merge --ff-only` (6 events in my log), the 150 ms debounce fires `reloadPlugins()`, and the shell segfaults while recreating the component.

Versions: Quickshell 0.3.1 (Arch), Qt 6.11.2, Omarchy 4.0.4. Plugin update was `io.github.tymurbogach.hardwarchy` 2.3.1 -> 2.3.2, but the plugin is incidental: the stack dies in `__dynamic_cast` -> `QQmlObjectCreator::finalize` -> `QQmlComponent::createObject`, i.e. in the platform recreate path, not in plugin JS/QML (which passed `qmllint` and runs fine after restart).

Log tail (from the crash dir):

```
Local plugin changed, reloading: io.github.tymurbogach.hardwarchy  (x6, same second)
```

Full crash dir available on request (`report.txt` + `log.qslog.log`, run id `xogy3qsqlt`).

Impact: cosmetic but scary. The shell restarts itself, the update completes (HEAD moved, validation passed), and user prefs survive. Still, every plugin update on every machine can flash-crash the desktop. A debounce that waits for write quiescence, or suspending the watcher while `plugin update` runs, would close the window.

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 17:05 UTC