https://bugs.winehq.org/show_bug.cgi?id=55260
--- Comment #3 from Otto b1779506@trbvn.com --- (In reply to Ken Sharp from comment #2)
Stop logging everything under Wine Staging unless you have confirmed that it doesn't occur in vanilla Wine.
Does this occur in vanilla Wine?
Are you using a non-default $WINEPREFIX?
I'm not able to detect the process ID because bash doesn't have any child process
What does this mean? Have you set up security to stop terminals seeing each other's processes?
I'm using a clean wineprefix ~/.wine/
These are the packages installed in ubuntu 23.04 (I'm using the official wine from the repos): $ apt list --installed | grep wine WARNING: apt does not have a stable CLI interface. Use with caution in scripts. fonts-wine/lunar,lunar,lunar,lunar,lunar,lunar,now 8.0~repack-4 all [installed] libkwineffects14/lunar,lunar,lunar,now 4:5.27.4-0ubuntu1 amd64 [installed,automatic] libwine-development/lunar,lunar,lunar,now 7.20~repack-1 amd64 [installed,automatic] libwine/lunar,lunar,lunar,now 8.0~repack-4 amd64 [installed,automatic] libwine/lunar,lunar,lunar,now 8.0~repack-4 i386 [installed,automatic] wine-staging-amd64/lunar,now 8.12~lunar-1 amd64 [installed,automatic] wine-staging-i386/lunar,now 8.12~lunar-1 i386 [installed,automatic] wine-staging/lunar,now 8.12~lunar-1 amd64 [installed,automatic] wine32/lunar,lunar,lunar,now 8.0~repack-4 i386 [installed] wine64/lunar,lunar,lunar,now 8.0~repack-4 amd64 [installed] winehq-staging/lunar,now 8.12~lunar-1 amd64 [installed] winetricks/lunar,lunar,lunar,lunar,lunar,lunar,now 20220411-1 all [installed]
I did not change any security configuration, the thing is, the installer terminates and then another process is launched in the background, so it goes like this:
1st-Run the Client _installer_: wine Setup_CONNECTIONClientx64_23.00.00.10.exe
while the installer is running, there's a bash child process for the installer: pstree -p 12343 bash(12343)───start.exe(12407)
Then it turns out the installer finishes (you can click the Finished button), and the bash does not has anymore any child process, but more debug keeps coming to gnome-terminal, since the client is automatically launched in the background (Bentley.Connect.Client.exe), and for some reason, it's attached to it. After several minutes, the process is released from gnome-terminal and it's possible to run more commands there.
If you want me, i can make a screen recording to demonstrate the issue.