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.
Quickshell repeatedly SIGSEGVs in authentication_cancelled_cb after overlapping Polkit requests
Reported by nontradition · filed Aug 31, 2026 · open at source
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
What happened
The default Omarchy Quickshell crashed while completing a Polkit authentication request. The shell supervisor restarted it automatically.
This has happened twice, on 2026-08-30 and 2026-08-31. Both coredumps have the identical stack.
Expected behavior
Completing or cancelling a privileged-operation prompt should close the Polkit dialog without crashing the shell.
Evidence
Command line:
quickshell -n -p /usr/share/omarchy/shell
Immediately before the latest crash, Quickshell logged:
incoming authentication request for action "org.freedesktop.policykit.exec"
activating authentication request ... cookie "...-1-..."
activating authentication request ... cookie "...-2-..."
authentication session completed, gainedAuthorization = true, isCancelled = false
finishing authentication request for action "org.freedesktop.policykit.exec"
Received event: "closelayer>>omarchy-polkit"
The two activation messages had different cookies, suggesting overlapping authentication requests.
Arch debuginfod resolves the actual faulting Quickshell frame as:
authentication_cancelled_cb(_GCancellable, void)
The relevant stack is:
#4 authentication_cancelled_cb(_GCancellable, void)
#5 g_signal_emit
#6 g_cancellable_cancel
#7 libpolkit-agent-1
#8 libgio-2.0
#9 g_main_context_iteration
#10 QEventDispatcherGlib::processEvents
#11 QEventLoop::exec
#12 QCoreApplication::exec
The upper raise() frame is Quickshell's crash handler re-raising SIGSEGV and is not the original fault.
The previous retained coredump has the same Quickshell offset (+0x2d1ec2) and the same Polkit/GCancellable stack.
There was no OOM condition: approximately 12 GiB RAM was available, swap was unused, and the kernel journal contained no OOM kill or related hardware error.
This looks like invalid callback state during Polkit cancellation, possibly a lifecycle/use-after-free problem when overlapping requests finish. The stack establishes the crash location; it does not by itself prove which object became invalid.
Frequency and impact
Two identical crashes on consecutive days. The shell restarts in about one second, but the pending privileged operation fails and must be retried. No user-file loss was observed.
System details
- Omarchy: 4.0.2-1
- Quickshell: 0.3.1-1
- Qt: 6.11.2
- glib2: 2.88.3-1
- GPU: Intel, i915
- Quickshell configuration:
/usr/share/omarchy/shell/shell.qml
omarchy debug --no-sudo --print was attempted but this installation reports:
Unknown Omarchy command: omarchy debug --no-sudo --print
Filed by GPT-5 via Codex.
View raw text
## What happened
The default Omarchy Quickshell crashed while completing a Polkit authentication request. The shell supervisor restarted it automatically.
This has happened twice, on 2026-08-30 and 2026-08-31. Both coredumps have the identical stack.
## Expected behavior
Completing or cancelling a privileged-operation prompt should close the Polkit dialog without crashing the shell.
## Evidence
Command line:
quickshell -n -p /usr/share/omarchy/shell
Immediately before the latest crash, Quickshell logged:
incoming authentication request for action "org.freedesktop.policykit.exec"
activating authentication request ... cookie "...-1-..."
activating authentication request ... cookie "...-2-..."
authentication session completed, gainedAuthorization = true, isCancelled = false
finishing authentication request for action "org.freedesktop.policykit.exec"
Received event: "closelayer>>omarchy-polkit"
The two activation messages had different cookies, suggesting overlapping authentication requests.
Arch debuginfod resolves the actual faulting Quickshell frame as:
authentication_cancelled_cb(_GCancellable*, void*)
The relevant stack is:
#4 authentication_cancelled_cb(_GCancellable*, void*)
#5 g_signal_emit
#6 g_cancellable_cancel
#7 libpolkit-agent-1
#8 libgio-2.0
#9 g_main_context_iteration
#10 QEventDispatcherGlib::processEvents
#11 QEventLoop::exec
#12 QCoreApplication::exec
The upper `raise()` frame is Quickshell's crash handler re-raising SIGSEGV and is not the original fault.
The previous retained coredump has the same Quickshell offset (`+0x2d1ec2`) and the same Polkit/GCancellable stack.
There was no OOM condition: approximately 12 GiB RAM was available, swap was unused, and the kernel journal contained no OOM kill or related hardware error.
This looks like invalid callback state during Polkit cancellation, possibly a lifecycle/use-after-free problem when overlapping requests finish. The stack establishes the crash location; it does not by itself prove which object became invalid.
## Frequency and impact
Two identical crashes on consecutive days. The shell restarts in about one second, but the pending privileged operation fails and must be retried. No user-file loss was observed.
## System details
- Omarchy: 4.0.2-1
- Quickshell: 0.3.1-1
- Qt: 6.11.2
- glib2: 2.88.3-1
- GPU: Intel, i915
- Quickshell configuration: `/usr/share/omarchy/shell/shell.qml`
`omarchy debug --no-sudo --print` was attempted but this installation reports:
Unknown Omarchy command: omarchy debug --no-sudo --print
Filed by GPT-5 via Codex.
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 10:23 UTC