http://bugs.winehq.org/show_bug.cgi?id=24424
Yuri Khan yurivkhan@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |yurivkhan@gmail.com
--- Comment #5 from Yuri Khan yurivkhan@gmail.com 2010-09-20 04:08:48 CDT --- I believe I am seeing the same regression. I have performed a 'git bisect' between wine-1.3.1 (good) and wine-1.3.2 (bad), and it points to:
commit b39a8d9ea2879f079b4daa9832b1c01deb5b56a7 Author: Eric Pouech eric.pouech@orange.fr Date: Mon Aug 30 22:18:44 2010 +0200
server: Enhanced the console input object so that it doesn't require a wineconsole to be running.
Further, I partially confirm Wylda's observation:
* In wine-1.3.3, Far works. * Executing 'wineconsole Far.exe' starts several processes: wineconsole.exe Far.exe, Far.exe (as child of wineconsole.exe), services.exe, winedevice.exe MountMgr (as child of services.exe), and explorer.exe /desktop. * Quitting Far by pressing F10 and confirming the quit dialog causes Far.exe to terminate. The four remaining processes (wineconsole.exe, services.exe, winedevice.exe, explorer.exe) continue running. The console window remains open and control does not return to the parent shell from which 'wineconsole Far.exe' was started. * It is then possible to kill the wineconsole process by closing the console window, or by pressing Ctrl+C in terminal, or by issuing a kill command in a concurrent shell session. This gives back the shell prompt, and shortly after that, some debug information is printed.
0x8d2ea88:1: Fd unix_fd=24 user=0x8d2ea18 options=00000020 0x8d2ea18:1: Console screen buffer input=0x8d5fc48 0x8d30150:1: Fd unix_fd=23 user=0x8d5fc48 options=00000020 0x8d9b400:1: Event manual=1 signaled=0 name="" 0x8d5fc48:1: Console input active=0x8d2ea18 evt=(nil)
The auxiliary processes (services.exe, winedevice.exe and explorer.exe) also terminate at this point.
I do not seem to need a terminal reset.