Persistent workspaces broken

[Frodojj]

Vaxry suggested that I made a discussion on this issue, as documented on the forum. There seems to be a regression with workspace created. In the latest update, a monitor needs to be specified otherwise the workspaces aren't persistent. The following rules don't work, for example:

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

bind = $mainMod, left, workspace, e-1 # also happens with m-1
bind = $mainMod, right, workspace, e+1 # also happens with m+1

workspace = 1, persistent:true
workspace = 2, persistent:true
workspace = 3, persistent:true

When I first log in, I cannot scroll to workspace 2 or 3 with mainMod + left/right binds until I go there directly mainMod+1/2/3. Then I can switch workspaces until the config is read again, either by changing a line (like adding a newline) or when the monitor turns off with hypridle. Even the first workspace is transient unless a window is opened on it or I go their directly from another workspace with mainMod+1.

[vaxerski]

#11762

[Frodojj]

So Hyprland seems to exhibit a weird behavior possibly related to this bug. I'm using Waybar to view the current workspace that I'm on. I bound the persistent workspaces to a monitor with the following rules:

bind = $mainMod, left, workspace, m-1
bind = $mainMod, right, workspace, m+1

workspace = 1, monitor:0, persistent:true
workspace = 2, monitor:0, persistent:true
workspace = 3, monitor:0, persistent:true

When logging in, Waybar indicates the current workspace is 4, although workspaces 1, 2, and 3 exist. (After deleting workspace 3 from the config, then logging in goes to non-persistent workspace 3 initially).

(Should I post this in #11762 instead?)

[vaxerski]

I assume switching to a workspace fixes it? Might be just a socket2 bug, pretty minor

[Frodojj]

Switching does when using monitor:0. Switching does not when not using that rule.