fix(resume): drop the hyprlock cover, pin workspace on wake

The qs restart no longer stacks hyprlock on the still-active session lock,
which read as a compositor crash. Disables workspace_swipe_create_new and
focus_on_activate, and logs compositor state after each wake until the
workspace jump is pinned. Also drops the vmware exec: this is bare metal.

Assisted-by: AI

Author: AndrewDemsDS

hypr/custom/execs.lua

@@ -1,8 +1,3 @@
 -- This file will not be overwritten across dots-hyprland updates.
 -- The file name is for the sake of organization and does not matter
 -- See the corresponding files in ~/.config/hypr/hyprland for examples
-
-hl.on("hyprland.start", function ()
-    -- VMware guest clipboard/resize bridge (no-ops on bare metal)
-    hl.exec_cmd("/usr/bin/vmware-user-suid-wrapper")
-end)

hypr/custom/general.lua

@@ -7,4 +7,18 @@ hl.config({
         kb_layout = "us,gr",
         kb_options = "grp:win_space_toggle,grp:alt_shift_toggle",
     },
+
+    -- Two upstream defaults that can silently move me off workspace 1 on resume.
+    -- With workspaceGroupSize = 10 the jump is sticky: from ws 23, SUPER+1 goes to
+    -- 21, not 1, so it has to be undone by hand.
+    gestures = {
+        -- A palm on the touchpad while opening the lid reads as a 4-finger
+        -- horizontal swipe; create_new then keeps inventing workspaces past the end.
+        workspace_swipe_create_new = false,
+    },
+    misc = {
+        -- An app firing xdg-activation on wake would otherwise drag focus (and me)
+        -- to whatever workspace it lives on.
+        focus_on_activate = false,
+    },
 })

hypr/custom/scripts/resume_debug_snapshot.sh

@@ -0,0 +1,32 @@
+#!/usr/bin/env bash
+# Record compositor state right after a wake, to pin down why resume sometimes
+# lands on a high workspace number. Runs from resume_restart_quickshell.sh.
+#
+# Reads three things:
+#   - whether eDP-1 was torn down and re-added (Hyprland assigns a fresh, higher
+#     workspace ID to a monitor it re-creates)
+#   - whether a gesture or an activation request moved the focus
+#   - which workspaces exist and which one is focused
+#
+# Delete this script and its call in resume_restart_quickshell.sh once the cause
+# is known.
+
+LOGFILE="$HOME/notes/resume-debug.log"
+mkdir -p "$(dirname "$LOGFILE")"
+
+sleep 3 # let the compositor and the relaunched shell settle
+
+{
+    echo "===== wake $(date -Is) ====="
+    echo "--- active workspace ---"
+    hyprctl activeworkspace 2>&1 | head -5
+    echo "--- workspaces ---"
+    hyprctl workspaces 2>&1 | grep -E "^workspace|windows:"
+    echo "--- monitors ---"
+    hyprctl monitors 2>&1 | grep -E "^Monitor|active workspace|dpmsStatus|disabled"
+    echo "--- hyprland log tail ---"
+    HL=$(ls -t /run/user/"$(id -u)"/hypr/*/hyprland.log 2>/dev/null | head -1)
+    [ -n "$HL" ] && grep -iE "monitor|workspace|gesture|activate|dpms|destroy" "$HL" \
+        | grep -viE "GL_|extensions" | tail -40
+    echo
+} >>"$LOGFILE" 2>&1

hypr/custom/scripts/resume_restart_quickshell.sh

@@ -1,12 +1,11 @@
 #!/usr/bin/env bash
 # Quickshell's renderer can freeze after suspend/resume with no recovery
 # (end-4/dots-hyprland #2320, #2971) — restart it on wake.
-# The qs lock screen dies with the restart, so cover the gap with hyprlock first.
-
-if ! pidof hyprlock >/dev/null; then
-    hyprlock &
-    sleep 0.5 # let hyprlock grab the session before the qs locker dies
-fi
+#
+# No hyprlock cover: this used to start hyprlock before killing qs, which left two
+# lock screens stacked on every wake and read as a compositor crash. The session is
+# still locked by logind, and misc.allow_session_lock_restore = true lets the
+# relaunched qs re-attach to that lock, so the gap covers itself.
 
 qs kill -c ii 2>/dev/null
 pkill -x qs 2>/dev/null # fallback if the freeze took the IPC socket with it
@@ -22,3 +21,5 @@ done
 pkill -9 -x qs 2>/dev/null # force-kill a frozen holdout that ignored SIGTERM
 
 qs -c ii -d # no -n: the old instance is gone, nothing to duplicate
+
+~/.config/hypr/custom/scripts/resume_debug_snapshot.sh &