Maximilian Seidler

> At the moment there still seems to be a race, albeit one that is winnable with the right settings. That has been the situation without the protocol. At least...

Thanks @IiroUllin, let's move this to the hypridle issue. Hyprlock is only involved in terms of how it's first submitted frame looks.

@Vladimir-csp > I think the proper fix would be to disable fade in animation after it was played, or disable it when handling any new screen that was not present...

I managed to reproduce it. https://github.com/user-attachments/assets/f7ba7b48-632b-4cee-b36c-8a1a84ccc975 I confirmed that hyprlock's background widget renders the solid color as soon as it can (frame 0). If one downloads the video and steps...

Update: External monitor doesn't matter. It's when disabling a monitor, but not disconnecting it. I can reproduce it with `monitor disable && hyprlock& sleep 4 && monitor enable` on hyprland...

Reopening for tracking, as most people will be looking for a hyprlock issue. It is a compositor bug though.

~Can you please try hyprlock-git?~

Nevermind, this is a dupe of #434 You can try executing `hyprctl keyword monitor "FALLBACK,1920x1080@60,auto,1"` and i think that should fix it as well.

Yeah this is not a hyprlock issue, but hl/aq. Fixed with hyprwm/aquamarine@16bbbcb. > but hyprctl keyword monitor "FALLBACK,1920x1080@60,auto,1" works for me. You can put `monitor=FALLBACK,1920x1080@60,auto,1` in your config for now...

Use latest aquamarine git, or put `monitor=FALLBACK,1920x1080@60,auto,1` along your other monitor configurations as a temporary fix. I think this can be closed.