You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been figuring this out with the dev of a different project, but there are multiple display-dependent (non-tiled, like bars or wallpaper managers including Hyprpaper) that I use or have used that seem to misbehave whenever I run systemctl suspend. We've come to the conclusion that this isn't actually a systemd issue, but it instead freaks out because the physical monitor powers off. When the system resumes, for ~3 seconds the system is active and generating output to the display, but the display hasn't yet powered on.
In addition to these display-specific apps crashing, Hyprland also will switch to the first available empty workspace, and I am met with the default wallpaper and nothing else on screen. This makes it look like all apps have crashed, which while fortunately not true is still slightly concerning if not for a second.
The easiest workaround is simply power on the monitor before resuming the system, which does work, but I can't help but feel this is unintended behavior. Is there something baked into Hyprland that manages this 3 second limbo time that I just don't have configured correctly? Should I be using a different command to sleep my system? If neither, should I open an issue?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I've been figuring this out with the dev of a different project, but there are multiple display-dependent (non-tiled, like bars or wallpaper managers including Hyprpaper) that I use or have used that seem to misbehave whenever I run
systemctl suspend
. We've come to the conclusion that this isn't actually a systemd issue, but it instead freaks out because the physical monitor powers off. When the system resumes, for ~3 seconds the system is active and generating output to the display, but the display hasn't yet powered on.In addition to these display-specific apps crashing, Hyprland also will switch to the first available empty workspace, and I am met with the default wallpaper and nothing else on screen. This makes it look like all apps have crashed, which while fortunately not true is still slightly concerning if not for a second.
The easiest workaround is simply power on the monitor before resuming the system, which does work, but I can't help but feel this is unintended behavior. Is there something baked into Hyprland that manages this 3 second limbo time that I just don't have configured correctly? Should I be using a different command to sleep my system? If neither, should I open an issue?
Beta Was this translation helpful? Give feedback.
All reactions