summaryrefslogtreecommitdiff
path: root/src/managers/SessionLockManager.hpp
Commit message (Collapse)AuthorAgeFilesLines
* sessionLock: send locked instead of denied when missing a lock frame for 5 ↵Maximilian Seidler2026-05-031-2/+2
| | | | | | | | | | | | | | | | seconds (#14271) The protocol seems to allow this, because it explicitly mentions either session lock surface or compositor blanking the output in this sentence: > The locked event must not be sent until a new "locked" frame (either from a session lock surface or the compositor blanking the output) has been presented on all outputs and no security sensitive normal/unlocked content is possibly visible. Since `locked_screen_delay` is capped to 5 seconds, after the 5 seconds this timer is registered for, we assume that all outputs are covered either by lockedead or by an actual lock frame. Thus sending locked is ok.
* desktop: cleanup, unify desktop elements as views (#12563)Vaxry2025-12-081-1/+1
|
* session-lock: don't render workspaces when locked (#10865)Maximilian Seidler2025-07-141-5/+7
| | | Avoid rendering the workspace behind if we are locked
* managers: refactor class member vars (#10242)davc0n2025-05-021-4/+4
|
* time: move to stl's clocks and move timerVaxry2025-04-161-1/+1
|
* input: pass touch events to lock screens (#9129)Junxuan Liao2025-01-251-9/+9
| | | | | * refactor: use weak pointers for session lock surfaces * input: pass touch events to lock screens
* core: move all shared_ptrs from the STL to hyprutils (#9143)Vaxry2025-01-231-5/+5
|
* renderer: add lockdead_screen_delay (#8467)Alexandre Acebedo2024-11-171-0/+3
|
* renderer: better lockscreen dead behavior (#7574)Vaxry2024-08-291-0/+1
| | | | | --------- Co-authored-by: Mihai Fufezan <mihai@fufexan.net>
* session-lock: send `locked` after the lock screen is properly rendered (#6850)Junxuan Liao2024-07-131-1/+7
| | | | | | | | | | The protocol says: > The locked event "must not be sent until a new "locked" frame (either from a > session lock surface or the compositor blanking the output) has been presented > on all outputs and no security sensitive normal/unlocked content is possibly > visible". This helps users ensure the screen is properly locked before suspending the machine. (e.g. with swaylock --ready-fd)
* core: move to hyprutils for utils (#6385)Vaxry2024-06-111-1/+1
| | | | | | | | | | | | | * core: move to hyprutils for utils Nix: add hyprutils dep * Meson: add hyprutils dep * flake.lock: update --------- Co-authored-by: Mihai Fufezan <mihai@fufexan.net>
* wayland/core: move to new impl (#6268)Vaxry2024-06-081-3/+4
| | | | | * wayland/core/dmabuf: move to new impl it's the final countdown
* session-lock: move to new implVaxry2024-04-301-16/+30
|
* lock: fix red screen issues with multiple monitors (#5100)Maximilian Seidler2024-03-151-2/+8
| | | | | | | | | | | * lock: use uint64_t for iMonitorID * lock: move activateLock to onNewSessionLock * lock: add red screen fade * lock: damage when fading the red screen and delay for screencopy * lock: remove redundant scheduleFrameForMonitor
* Implement ext-session-lock-v1vaxerski2023-02-031-0/+46
generated by cgit v1.2.3 (git 2.25.1) at 2026-11-01 20:55:57 +0000