To clarify:

If I have a bunch of active windows/programs up on my main screen (set to primary) and NOTHING on my second screen, if I put my computer to sleep, or my monitors go to sleep, when they wake back up all of my active Windows are pushed to my second screen.

I have a feeling this is because Linux is detecting that my main screen isn't on yet and it needs to draw the active windows somewhere, so it pushes them onto the second screen which turns on a lot faster.

Is there any validity to this theory?

I thought this issue was related to X11, so I switched from Mint to Fedora 35 where Wayland is available. Wayland is nice in the sense that I can get the full 200hz from my main screen while my secondary 60hz screen is on but this active window wake from sleep issue is still present.

I dunno what to do this about this but I am very irritated by it.

Any suggestions?

Is your main/primary screen Xorg's default primary, or have you configured something to move primary attribution from the smaller screen to the larger screen? If the latter, how & where? If you used a DE tool, it may be being reapplied freshly during wakeup. If you make it the primary before your session starts, either via xrandr in a startup script, or via *.conf in /etc/X11/, you may find your windows staying on the larger screen.

1 members found this post helpful.

Where would I go on my machine to see all of that? Still Fedora 35 here. I'm pretty confident it's using Wayland but I do still have an /etc/X11 directory with some stuff in it.

I really appreciate you responding!

This has happened here. I can't currently remember all the thoughts that had been collected and written here. What follows is some that I can.

I/O posted here would provide us a summary of you current situation, including DE, and whether Xorg or Wayland, at the time it is run.

Most DEs I believe have some GUI tool for managing settings for local displays, among which, which display is primary, typically among others named "desktop settings" or "system settings" or similar. There's also a standalone GUI tool for this purpose named arandr. Settings saved by these methods normally aren't applied until after login succeeds for the user who saved them, though those created by arandr should be convertible to global use.

Global settings usually involve /etc/X11/xorg.con* and/or script(s) that manipulate settings using xrandr or other tools for managing display behavior. These take effect prior to user login, which makes them more fundamental than user saved settings, possibly to the extent that having windows jump to a different display when a wakeup even occurs might be avoided.

/etc/X11/xorg.con* and xrandr I'm familiar with. Whether or to what extent they might be employed by Wayland users I have no idea, as I have yet to attempt to use Wayland purposely in any way, shape or form.