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
When the device is suspended and woken up there are some interesting game breaking issues that occur:
The top and bottom Steam Gaming Mode panel is completely missing that contained information such as the time, battery life, downloads and wifi status (top) as well as the button prompts at the bottom.
Controls no longer work outside of Steam (including the touch screen), run a Steam game after suspending means controls no longer work.
Another interesting tidbit is that suspending from the power menu produces no animation yet suspending from the Steam menu plays it. Regardless of the method, resuming from suspension still breaks the top panel and controls.
A quick fix / workaround is going to Desktop Mode and then going back to Steam Gaming Mode as opposed to rebooting the device, but that works too.
What did you expect to happen?
I expected the device to resume from sleep and have functional controls and UI elements to stay in place.
Describe the bug
When the device is suspended and woken up there are some interesting game breaking issues that occur:
Another interesting tidbit is that suspending from the power menu produces no animation yet suspending from the Steam menu plays it. Regardless of the method, resuming from suspension still breaks the top panel and controls.
A quick fix / workaround is going to Desktop Mode and then going back to Steam Gaming Mode as opposed to rebooting the device, but that works too.
What did you expect to happen?
I expected the device to resume from sleep and have functional controls and UI elements to stay in place.
Output of
rpm-ostree status
Hardware
ROG Ally X RC72LA_RC72LA
Extra information or context
This is the last bug that I have found today.
Edit (Solution)
Turn off the waking animation after suspending in the Steam settings.
The text was updated successfully, but these errors were encountered: