Sleep with mutiple monitors trashes workspaces

[Logical-sh]

Hyprland Version

System/Version info

Hyprland, built from branch HEAD at commit 03ebbe18ed8517ee22591eac82cd54322f42cb7d  (props: bump ver to 0.34.0).
Date: Mon Jan 1 12:03:15 2024
Tag: v0.34.0

flags: (if any)

Bug or Regression?

Bug

Description

Using swaylock

If I let it lock, and dpms goes off, when I return and unlock, my workspaces are shuffled around and my special workspaces are all open (I found a separate bug for this so not focusing on it).

All of the workspaces seem to be moved off of my third monitor, and calling the dispatcher wont work to move them to that monitor anymore. I have to create a brand new workspace on the 3rd monitor, move the windows into that, and then move the normal expected workspace into that monitor.

How to reproduce

Still working on exacts. But definitely happens after extended lock and dpms time, quickly toggling dpms alone will not trigger. I am guessing it's tied to monitor sleep.

Crash reports, logs, images, videos

No response

[robertoash]

I am experiencing the same thing.

For me, running hyprctl monitors -j shows that the monitors have changed names which leads me to believe that Hyprland identifies them as completely new monitors and, hence, initializes them with all default settings. All of my existing workspaces are bunched up into one monitor and the other monitor just gets a new empty workspace.

All of these settings are bound to the monitor name so they are not being applied:

• Monitor settings (ex.: monitor = DP-3, 2560x1440, 0x0, 1, transform, 1)
• Workspace settings (ex.: workspace = 15, monitor:DP-4, layoutopt:orientation:left)

Everything was working fine for me before so I think this is a regression.

[kopsis]

I'm seeing what may be the same issue with just a single monitor. I find that if I use the key bound to reloading hyprland config it usually recovers (though I sometimes see one or more apps killed in the process). I will see if I can get a "hyperctl monitors -j" output next time it happens.

[lacamar]

I'm also seeing this issue. After coming back from dpms off, all of my special workspaces are up and have to be cleared one by one.

[AndreasBackx]

Also am facing this. The log only contains Active window is incorrect: . when looking at it after the fact. It also does not happen every single time, but quite frequently.

[AndreasBackx]

Important details that I noticed.

I have a side monitor that often has 3 workspaces active/open with IDs 1, 3, and 5. When this bug occurs, workspace 3 and 5 move to my center monitor and act like they are attached to that monitor. ID 1 stays on the side monitor.

Then to restore it, I need to move all windows away from the "bad" moved workspaces, move away from it so it closes, and them back to the previously bad workspace. Then it'll be back on the side monitor.

It's odd that monitor 1 stays on the side monitor.

---

Additionally, when I boot I am experiencing this bug as well but for my laptop monitor. I boot my laptop closed and when Hyprland opens, it has moved monitor ID 301 (which was the one on the closed laptop screen) to my center monitor. Again I have to move away from it to make it disappear and fix itself.