regression: lockdead.png on idle

[user111111111111111111111111111111111]

version: abe2964
Using 2 monitors and opening a foot terminal in each of them, and leaving the cursor on the one with id 1 results in swaylock not starting and in the lockdead.png image
Happens about once each 5 attempts

regressed by 01971cb 06fcdbd by @PaideiaDilemma

swaylock.log

exec-once = swayidle -w timeout 6 'if pgrep -x swaylock; then hyprctl dispatch dpms off; fi' timeout 7 'hyprctl dispatch dpms off' timeout 8 'if ! pgrep -x swaylock; then swaylock; fi' resume 'hyprctl dispatch dpms on'

input {
    follow_mouse = 2 
}

$mainMod = ALT 

bind = $mainMod, Q, exec, foot 
bind = $mainMod, C, killactive, 

bind = $mainMod, left, movefocus, l
bind = $mainMod, right, movefocus, r
bind = $mainMod, up, movefocus, u
bind = $mainMod, down, movefocus, d

bind = $mainMod SHIFT, left, movewindow, l
bind = $mainMod SHIFT, right, movewindow, r
bind = $mainMod SHIFT, up, movewindow, u
bind = $mainMod SHIFT, down, movewindow, d

bind = $mainMod, 1, workspace, 1
bind = $mainMod, 2, workspace, 2

bind = $mainMod SHIFT, 1, movetoworkspace, 1
bind = $mainMod SHIFT, 2, movetoworkspace, 2

bindm = $mainMod, mouse:272, movewindow
bindm = $mainMod, mouse:273, resizewindow

bind = $mainMod, P, fullscreen,
bind = $mainMod, Space, togglefloating,

debug {
    enable_stdout_logs = true
    disable_logs = false
}

misc {
    mouse_move_enables_dpms = true
    key_press_enables_dpms = true
}

[PaideiaDilemma]

@user111111111111111111111111111111111 check #11278

What am I missing with the exec-once line? Why does resume trigger without input? Is that a bug as well?

[user111111111111111111111111111111111]

couldn't repro the issue with the PR

What am I missing with the exec-once line? Why does resume trigger without input? Is that a bug as well?

not sure what you mean by "resume trigger without input"