search

ValveSoftware / gamescope

SteamOS session compositing window manager
Other
3.01k stars 198 forks source link

gamescopereaper does not kill child winedevice #1482

Open R1kaB3rN opened 4 weeks ago

R1kaB3rN commented 4 weeks ago

Description

After forcefully closing the X connection for an application that is run through wine, it's observed gamescope fails to kill the winedevice subprocess. As a result, users need to manually kill the process for both the app window and the gamescope instance to close. Moreover, applications that depend on gamescope functionality need to implement custom logic to handle killing the winedevice.

Expectation

Gamescope properly kills all children when the X connection closes.

Steps to reproduce

  1. Install gamescope that supports gamescopereaper
  2. Install wine
  3. Open a terminal emulator
  4. Run gamescope -- winecfg
  5. Click the OK button or send ctrl+c from terminal window
  6. Observe that the app window is still visible
  7. Run ps -e | grep winedevice to observe that winedevice has not been killed

Gamescope version: 3.14.29-1 Distribution: Arch Linux Desktop: sway Window system: wayland

DocMAX commented 1 week ago

Same here... winedevice.exe remains after wine app closes. This only happens with gamescope. image Is it possible to disable gamescopereaper?

EDIT: Here is a workaround. Disable winedevice with WINEDLLOVERRIDES="winedevice.exe=d"