protonscr

Steam game overlay process doesn't close

steamopen overlayDistro Family: Gentoo
ValveSoftware/steam-for-linux#12402 · opened 2025-10-21 by orbea · updated 2025-11-08 · 2 comments · github
Oorbea 2025-10-21 github

Your system information

  • Steam client version (build number or date): 1759461205
  • Distribution (e.g. Ubuntu): Gentoo
  • Opted into Steam client beta?: No
  • Have you checked for system updates?: Yes
  • Steam Logs: steam-logs.tar.gz
  • GPU: AMD

Please describe your issue in as much detail as possible:

Sometimes the process for the steam game overlay doesn't close correctly when closing the game and requires killing the process with SIGKILL. This is a problem because until the game overlay process is closed or otherwise killed it prevents my monitor from entering the suspend state from inactivity.

Steps for reproducing this issue:

  1. Start a game with the overlay enabled.
  2. Close game.
  3. Sometimes the overlay process gets stuck and doesn't close until using SIGKILL.
Oorbea 2025-10-27 github

A script like this works around this issue.

#!/bin/sh

set -eu

gpid="$(pidof gameoverlayui)" || gpid=

kill_prog () {
  sig="-${2:-15}"
  eval "set -- ${1}"
  for pid do
    if [ -n "$pid" ] && kill -0 "$pid" 2>/dev/null; then
      kill "$sig" "$pid"
    fi
  done
}

kill_prog "$gpid" 9

I have a wrapper script which I use to launch steam games and placed this in the quit() function that executes when the script (game) closes.

Ttruefakts 2025-11-08 github

Officially, Valve states that the .deb from steampowered.com or the Flatpak are the only supported versions of Steam. The packaged version on rpm-fusion is made by a 3rd party and valve has no control over what dependencies are bundled.
Please retest with the flatpak version of steam and attempt to reproduce. Or install Ubuntu LTS as the Readme on this repo suggests.
There is an open pull request to update the readme to better outline Steam's requirements. Please read, and cross reference the requirements against what operating system you're using on your workstation: 72b3eae

Presumably you compiled the client yourself on Gentoo, what steps have you taken to verify that this issue is not a result of your environment?

For the record, I cannot reproduce on Ubuntu 25.10

Nothing extracted yet.