The currently open omacom/omarchy#14816 was opened by dsundt on October 10. In an in-day follow-up, dsundt reported that every completed unlock on the tested machine left the shell believing it remained locked, causing the next lock request to do nothing. Restarting the shell was the reported workaround. omacom/omarchy#14816:issuecomment-6100203282 supplies that observation independently of the issue body's later edits.
scottadair reported the same state on another laptop, including two lid-close suspends without a secure lock and nonfunctional manual locking. rafalyovson connected the report to an existing Quickshell investigation and competing fixes, while reporting reproduction on the latest tested edge build. These are contributor reports and diagnosis, rather than evidence of a merged repair. omacom/omarchy#14816:issuecomment-6097484047 and omacom/omarchy#14816:issuecomment-6099485761 document the progression.
