Closing command line Wine application causes all other Wine sessions to freeze

[KamilaBorowska]

If you have a graphical Wine applications open, closing a text application will cause Wine applications to freeze.

For instance, you can run winecfg, followed by cmd, and then exit cmd by typing exit, and then winecfg will freeze.

[fastrizwaan]

flatpak kill org.winehq.Wine would help to close all instances.

[xalt7x]

Sounds similar to bottlesdevs/Bottles#2759

[foresto]

Reproducible with two instances of winecfg:

1. From terminal A, flatpak run --command=winecfg org.winehq.Wine
2. From terminal B, flatpak run --command=winecfg org.winehq.Wine
3. Close the second instance of winecfg

Both terminal A and B have now returned to their shell prompts. The first winecfg window is still present, but is now frozen.

[charlesthobe]

Might also be related to this: bottlesdevs/Bottles#2372
albeit sudo flatpak override --allow=per-app-dev-shm org.winehq.Wine doesn't fix it.

[charlesthobe]

Thing is if you run flatpak run --command=sh org.winehq.Wine then run winecfg & and then wine notepad & etc, the bug doesn't happen, so I think the bug has something to do with creating multiple bwrap instances.

[charlesthobe]

The process space of one instance doesn't get exposed to another, this is most likely what causes the issue because of problems with IPC.
IDK if it's possible to create an intermediary executable that detects if an instance of the application is already running to launch the new command inside that instance, but if it's possible then it's probably the solution.
flatpak/flatpak#1963