Unnecessary modesets when switching from TTY back to Hyprland or when handing off to Plymouth

[Nosamdaman]

Hyprland version

0.50.1

Regression

This has never worked for me, but I've only been using Hyprland for a few weeks at this point. Interestingly, kwin_wayland used to have this same issue back when Plasma 6 first released, but it seems to have been fixed since then.

Describe the bug

When switching from Hyprland to a TTY, the change happens instantly, as expected since both Hyprland and TTY framebuffer are using the same display mode. But when switching back to Hyprland, a mode set is performed and the monitor blanks for a second. This also occurs when shutting down Hyprland and handing off the screen to Plymouth.

Reproduction steps

Assuming Hyprland is running on TTY-1 and KMS is enabled

1. Switch to an alternate TTY with Ctrl+Alt+2
2. Switch back to Hyprland with Ctrl+Alt+1
3. You should see an unnecessary mode set

System info and config

hyprland.log
system.txt

Note that this happens on both this laptop and my desktop running an NVIDIA GPU. It's particularly annoying there because my monitor has an annoyingly long modeset time. When this occurs at shutdown, I don't even get a chance to read those logs.

[Vladimir-csp]

This happens on Intel GPU too.

[vaxerski]

I think we wanted to get rid of this but it broke a buncha things. In general, this is something that aquamarine handles not hl

[fxzzi]

info for those curious:

hyprwm/aquamarine#183
hyprwm/aquamarine#184

[tekstryder]

• Prevent DRM Backend from modesetting unnecessarily aquamarine#183 was reverted.
• Avoid unnecessary modeset (fixed) aquamarine#184 was merged back in 0.9.1?

Is...

• Fix hdr modeset aquamarine#198 ...what would possibly address the issue here?

Reproducible with 0.9.4 tag.

[Nosamdaman]

Thanks for the response, guys, I'm marking this discussion as it's clear that this belongs in aquamarine not here. See issue 205 in that repository for a deeper investigation I performed.