Your system information

• Steam client version (build number or date): 1715891371
• Distribution: SteamOS 3.6.3 (20240516.100)
• Opted into Steam client beta?: No
• Have you checked for system updates?: Yes
• Steam Logs: steam-logs.tar.gz
• GPU: AMD Custom GPU 0405

Please describe your issue in as much detail as possible:

What I Expected:
Resuming a non-Steam game on the Steam Deck, from sleep mode, shouldn't cause my Desktop Client to close a currently running Steam game and log me out.

What Happened:
This only happened for me when I specifically resumed a non-Steam game on the Steam Deck. Initially, launching the non-Steam game presented no issue; however, going into sleep mode then waking the device terminates my desktop log-in when it re-connected to wifi.

In my opinion, this shouldn't happen. Reason: non-Steam games aren't tied to the DRM library (or rather, they shouldn't) because it isn't an attempt at circumventing it when the game on the second device (the Steam Deck in this case) isn't from Steam and/or is DRM-free. It makes sense if you were trying to prevent two Steam games from running on the same account at once, but that is not what's happening here.
(In my case, the reason why I even had this setup was because I was waiting for a "timer" on my desktop game and was resuming a playthrough of a DRM-free game on my Steam Deck while I waited to then be disappointment when I was logged out of FFXIV on my desktop (which has a launcher that needs to be logged into every time) and now I'm forced to keep my Steam Deck offline because of this faulty DRM-check.)

Steps for reproducing this issue:

1. Launch a game on an online Steam desktop client
2. Launch a non-Steam game on a Steam Deck while online (Possibly applicable to other desktop clients, maybe?)
3. Put the Steam Deck into sleep mode
4. Wake the Steam Deck from sleep mode
5. Desktop client terminates the active game, logs the user out, and fully shuts itself down