protonscr

Window switching issues with non-Steam launcher and game on Steam Deck OLED

steamopen overlayDistro Family: SteamOSnon-Steam application
ValveSoftware/steam-for-linux#12278 · opened 2025-08-18 by chefranov · updated 2025-09-10 · 1 comments · github
Cchefranov 2025-08-18 github

Your system information

  • Steam client version (build number or date): 1751405894
  • Distribution (e.g. Ubuntu): Steam Deck OLED
  • Opted into Steam client beta?: No
  • Have you checked for system updates?: Yes
  • Steam Logs:
  • GPU: (Steam Deck OLED, GPU not specified)
  • OS Version: 3.7.13
  • OS Build: 20250630.1

Please describe your issue in as much detail as possible:

When using a non-Steam launcher (battle.net added as "non-Steam" application), after launching Diablo 2: Ressurected from the launcher and entering the game, opening the side Steam menu with the "Steam" button presents two issues:

  1. I want to switch from the game window to the launcher window, but visually I cannot highlight the launcher window in the menu (although I can scroll to it physically and select it blindly).
  2. After clicking on the launcher window, the focus does not switch to it; I remain in the Steam menu. If I click back to the game window, the game remains accessible.

This behavior did not occur 2-3 months ago.

Steps for reproducing this issue:

  1. Add battle.net launcher as a non-Steam application in Steam.
  2. Launch the battle.net launcher and start Diablo 2: Ressurected.
  3. While the game is running, open the Steam side menu using the "Steam" button.
  4. Try to switch from the game window to the launcher window using the menu.
  5. Observe inability to visually highlight the launcher window and failure to switch focus to it.

https://github.com/user-attachments/assets/dad97cd9-ad3a-4c43-9098-0dda064c2276

Additional information:

  • This issue is new; it was not present 2-3 months ago.
  • Device: Steam Deck OLED
  • OS Version: 3.7.13, Build: 20250630.1
  • Steam client version: 1751405894
Cchefranov 2025-09-10 github

The issue №1 was fixed after latest release but 2nd issue is still exist.

Nothing extracted yet.