https://bugs.winehq.org/show_bug.cgi?id=50869
--- Comment #4 from Robbert van der Helm mail@robbertvanderhelm.nl --- I've created a separate issue for (1) (bug 50879), and I've added a comment to bug 50867 for (3). (4) is probably not a bug but more of an unintional consequence of this change, right? Or would `wine 'https://google.com%27%60 cause `iexplore` or something to pop up? Anyways, this is (2) repeated once more (since I can't change the description of this bug):
When spawning a Wine child process from another application, you can no longer kill that child process by raising SIGINT or SIGKILL for the pid of the child process you spawned using (v)fork and exec. In Wine 6.5 this now kills the start.exe process, but it leaves the actual inferior process running in the background. To reproduce this, run `wine notepad&` in `fish` (bash seems to kill the child process by itself), use `ps -aux | grep notepad` or `jobs` to find the pid of the process just named `notepad`, and then run `kill -SIGKINT <pid>` (or with SIGKILL). Even though the process launched using `wine notepad&` has exited, Notepad is still running in the background.