Hello @thndgonz, if you completely close Steam, then run steam-runtime from a terminal and reproduce the issue, are there any hints in the terminal spew after reproducing this issue? Also, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.
I'll report as soon as I can if it's spewing hints on the terminal I did try with the steam-runtime thinking the native version perhaps was more experimental but both were reproduced equally. I'll attached any output Ill find soon. Here's the system info
https://gist.github.com/thndgonz/9b2c3a8bb8d9d67af60c8bc1212f3ecf
Steam-runtime output
https://gist.github.com/thndgonz/9d8522cf51187f860dd198e362a66bbf
Attached dump file generated
crash_20221012014939_46.tar.gz
For reference, the attached minidump is a SIGSEGV in libSDL2-2.0.so.0.
Nothing extracted yet.
Your system information
Please describe your issue in as much detail as possible:
I noticed that remote playing works under typical conditions of just leaving the monitors on. However all of this changes if you try to turn them on but leaving the steam client on with remote play. Sometimes I did this on Windows because I just wanted to save energy rather than leave them idling by if I was going to leave for a while
What should happen is that Steam and games would still work. However I do not know how viable it is with X.org display server as I don't know if the issue is X.org becoming "unavailable" until I turn off the monitors or not and launching the title would look for the display server.
Steps for reproducing this issue: