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-4787GitHub issuePublicReceived

v4.0.2 package missing hover-revealed notification close button (#6946)

Reported by johnpippett · filed Aug 31, 2026Closed upstream on 2026-09-21 by bjarneo via an automated message, as a duplicate of #7711 (R-1594). GitHub close reason: completed.

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

v4.0.2 package missing hover-revealed notification close button (#6946)revision 1 · captured 2026-10-04 12:03 UTC via poll

System details

Omarchy 4.0.2-1, quickshell 0.3.1-1 (Adamantite)

What's wrong?

PR #6946 (merged into quattro as 9b72edcc) added a hover-revealed ✕ on notification toasts so you can dismiss without invoking the default action (and without needing to know about right-click).

That button is present on the quattro branch tip (NotificationCard.qml ~228 lines, contains ✕) but absent from the v4.0.2 tag / packaged tree (/usr/share/omarchy/shell/plugins/notifications/components/NotificationCard.qml is still 196 lines with right-click-only dismiss).

This matches user reports like #7711: critical actionable toasts (e.g. Process crashed) look undismissable if you don't know right-click / Super+, .

Expected

Packaged 4.0.2 (or a follow-up point release) should include the #6946 close affordance from quattro.

Workaround used locally

omarchy plugin clone omarchy.notifications → backport the #6946 close button into ~/.config/omarchy/plugins/<user>.notifications/components/NotificationCard.qml.

View raw text
### System details

Omarchy 4.0.2-1, quickshell 0.3.1-1 (Adamantite)

### What's wrong?

PR #6946 (merged into `quattro` as 9b72edcc) added a hover-revealed ✕ on notification toasts so you can dismiss without invoking the default action (and without needing to know about right-click).

That button is present on the `quattro` branch tip (`NotificationCard.qml` ~228 lines, contains ✕) but **absent from the v4.0.2 tag / packaged tree** (`/usr/share/omarchy/shell/plugins/notifications/components/NotificationCard.qml` is still 196 lines with right-click-only dismiss).

This matches user reports like #7711: critical actionable toasts (e.g. Process crashed) look undismissable if you don't know right-click / Super+, .

### Expected

Packaged 4.0.2 (or a follow-up point release) should include the #6946 close affordance from `quattro`.

### Workaround used locally

`omarchy plugin clone omarchy.notifications` → backport the #6946 close button into `~/.config/omarchy/plugins/<user>.notifications/components/NotificationCard.qml`.

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.