[Bug 50869] New: Regressions caused by new start.exe behaviour in Wine 6.5 (stdout redirect, killing inferior, wine start /unix)

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=50869

Bug ID: 50869
           Summary: Regressions caused by new start.exe behaviour in Wine
                    6.5 (stdout redirect, killing inferior, wine start
                    /unix)
           Product: Wine
           Version: 6.5
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: programs
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

I noticed a few regressions and new weird behaviours after updating to Wine 6.5
with regards to launching applications now that everything gets launched
through
start.exe:

1. When launching Winelib applications all STDOUT output gets lost. I tested
   this with a simple C++ file compiled with wineg++ that tries to print some
   text using both `printf()` and `std::cout`. Printing to STDERR using
   `std::cerr` still works fine.
2. 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. In Wine 6.5 this now kills the start.exe process, but it leaves
   the 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.
3. (duplicate of bug 50867, but I still wanted to mention it here for
   completeness' sake) Launching binaries with Wine from the GUI by clicking on
   them (using the bundled wine.desktop) no longer works. This uses
   `wine start /unix`, which was already reported to no longer work as of Wine
   6.5 in the other issue because `ShellExecuteEx` cannot find the file.
4. And lastly, as discovered by @stefand, `wine https://google.com%60 now
launches
   the regular system browser. This is probably not really a bug as much as a
   consequence of the start.exe change, but I just wanted to mention it.

Please let me know if I should split this up into separate tickets.