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

Lenovo notebooks trigger lid open event immediately after closing the lid

Reported by pkwagner · filed Apr 23, 2026Closed upstream on 2026-04-23 by its own reporter pkwagner. GitHub close reason: completed. Closed by its own reporter — not by itself evidence of a fix.

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

Lenovo notebooks trigger lid open event immediately after closing the lidrevision 1 · captured 2026-10-04 11:56 UTC via poll

System details

Omarchy 3.6.0, Lenovo IdeaPad Pro 5

What's wrong?

When closing the lid of my IdeaPad Pro 5 (and presumably all Lenovo/ThinkPad notebooks on the same hardware base), first a (correct) switch:on:Lid Switch event gets triggered, followed by a faulty switch:off:Lid Switch ~two seconds later~ when switching workspaces on the main monitor and without opening the lid in the meantime.

I verified the behavior with the following utilities.conf modification:

bindl = , switch:on:Lid Switch, exec, echo "$(date) Lid close" >> /home/pkwagner/LID_LOG && omarchy-hyprland-monitor-internal off
bindl = , switch:off:Lid Switch, exec, echo "$(date) Lid open" >> /home/pkwagner/LID_LOG && omarchy-hyprland-monitor-internal on

Leading to this ~/LID_LOG:

Thu Apr 23 05:03:32 PM CEST 2026 Lid close
Thu Apr 23 05:03:34 PM CEST 2026 Lid open

I don't yet have an idea on how to work around this from the Omarchy side, cause no second switch:off:Lid Switch gets re-triggered when really opening the lid.

View raw text
### System details

Omarchy 3.6.0, Lenovo IdeaPad Pro 5

### What's wrong?

When closing the lid of my IdeaPad Pro 5 (and presumably all Lenovo/ThinkPad notebooks on the same hardware base), first a (correct) `switch:on:Lid Switch` event gets triggered, followed by a faulty `switch:off:Lid Switch` ~two seconds later~ when switching workspaces on the main monitor and without opening the lid in the meantime.

I verified the behavior with the following `utilities.conf` modification:
```
bindl = , switch:on:Lid Switch, exec, echo "$(date) Lid close" >> /home/pkwagner/LID_LOG && omarchy-hyprland-monitor-internal off
bindl = , switch:off:Lid Switch, exec, echo "$(date) Lid open" >> /home/pkwagner/LID_LOG && omarchy-hyprland-monitor-internal on
```

Leading to this `~/LID_LOG`:
```
Thu Apr 23 05:03:32 PM CEST 2026 Lid close
Thu Apr 23 05:03:34 PM CEST 2026 Lid open
```

I don't yet have an idea on how to work around this from the Omarchy side, cause no second `switch:off:Lid Switch` gets re-triggered when really opening the lid.

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.