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

bug: Screen does not wake up after some interval of either lid closed and reopened or leave to sit for a while

Reported by aashish-thapa · filed Nov 22, 2025 · 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

bug: Screen does not wake up after some interval of either lid closed and reopened or leave to sit for a whilerevision 1 · captured 2026-09-28 21:29 UTC via poll

System details

ThinkPad T14 Gen 5

What's wrong?

After I close the lid, and re open it, the display does not wake back up. I tried to force logind as well:

HandleLidSwitch=ignore  
HandleLidSwitchExternalPower=ignore  
HandleLidSwitchDocked=ignore

this does not seem to be working
the wakeup thats being used

❯ cat /proc/acpi/wakeup
Device  S-state   Status   Sysfs node
GPP0      S0    *disabled
GPP2      S3    *disabled
GPP5      S0    *enabled   pci:0000:00:02.1
GPP6      S4    *enabled   pci:0000:00:02.2
GP11      S4    *enabled   pci:0000:00:03.1
SWUS      S4    *disabled
GP12      S4    *enabled   pci:0000:00:04.1
SWUS      S4    *disabled
XHC0      S3    *enabled   pci:0000:c4:00.3
XHC1      S4    *enabled   pci:0000:c4:00.4
XHC2      S4    *disabled  pci:0000:c6:00.0
NHI0      S3    *enabled   pci:0000:c6:00.5
XHC3      S3    *enabled   pci:0000:c6:00.3
NHI1      S4    *enabled   pci:0000:c6:00.6
XHC4      S3    *enabled   pci:0000:c6:00.4
LID   S4    *enabled   platform:PNP0C0D:00
SLPB      S3    *enabled   platform:PNP0C0E:00

If anyone has the fix for it, please let me know.

View raw text
### System details

ThinkPad T14 Gen 5

### What's wrong?

After I close the lid, and re open it, the display does not wake back up. I tried to force logind as well:
```bash
HandleLidSwitch=ignore  
HandleLidSwitchExternalPower=ignore  
HandleLidSwitchDocked=ignore
```
this does not seem to be working
the wakeup thats being used
```bash
❯ cat /proc/acpi/wakeup
Device  S-state   Status   Sysfs node
GPP0      S0    *disabled
GPP2      S3    *disabled
GPP5      S0    *enabled   pci:0000:00:02.1
GPP6      S4    *enabled   pci:0000:00:02.2
GP11      S4    *enabled   pci:0000:00:03.1
SWUS      S4    *disabled
GP12      S4    *enabled   pci:0000:00:04.1
SWUS      S4    *disabled
XHC0      S3    *enabled   pci:0000:c4:00.3
XHC1      S4    *enabled   pci:0000:c4:00.4
XHC2      S4    *disabled  pci:0000:c6:00.0
NHI0      S3    *enabled   pci:0000:c6:00.5
XHC3      S3    *enabled   pci:0000:c6:00.3
NHI1      S4    *enabled   pci:0000:c6:00.6
XHC4      S3    *enabled   pci:0000:c6:00.4
LID   S4    *enabled   platform:PNP0C0D:00
SLPB      S3    *enabled   platform:PNP0C0E:00
```
If anyone has the fix for it, please let me know.

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.