http://bugs.winehq.org/show_bug.cgi?id=17093
Summary: console not being connected to stdin/stdout correctly Product: Wine Version: unspecified Platform: Other OS/Version: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: lkcl@lkcl.net
under certain circumstances, it's possible for stdin and stdout to become connected, instead of to a command prompt window (e.g. wineconsole cmd.exe) to the linux command xterm that started the command prompt window.
downloading the standard python 2.5.2 executable and running it i confirmed that this situation occurs when msvcrt is set to native _or_ to builtin (but i haven't confirmed with msvcr71 native, which is what python 2.5.2 exe is built with).
the msi for python2.5.2 can be downloaded here: http://www.python.org/ftp/python/2.5.2/python-2.5.2.msi
and the .exe and the dll can be extracted - you will need both python.exe _and_ python25.dll - using cabextract, you _don't_ need to actually install it.
anything on the command line (e.g. python.exe -c 'print "hello"') or python -v -i *change* the way that the code operates and *does* work.
also, redirection works e.g. echo 'print "hello"' | ./python.exe
... but not interactive operation (without explicitly saying so using the -i option).
http://bugs.winehq.org/show_bug.cgi?id=17093
--- Comment #1 from Andrew Nguyen arethusa26@gmail.com 2009-07-30 13:15:07 --- Does the issue persist in 1.1.26? My limited testing seemed to indicate that this was not a problem, but I'm not sure I performed the testing correctly.
http://bugs.winehq.org/show_bug.cgi?id=17093
--- Comment #2 from Austin English austinenglish@gmail.com 2010-09-07 14:22:34 CDT --- I have a feeling that Eric's recent console work may have fixed this. Can you retest in git and/or give clear steps of how to reproduce the problem?
http://bugs.winehq.org/show_bug.cgi?id=17093
--- Comment #3 from Luke Kenneth Casson Leighton lkcl@lkcl.net 2010-09-08 03:38:37 CDT --- (In reply to comment #2)
I have a feeling that Eric's recent console work may have fixed this. Can you retest in git and/or give clear steps of how to reproduce the problem?
unfortunately it's quite a bit of work to cut out the relevant buggy portions of python, so you'd need to just install python 2.5.2 under wine (which does work!) and then fire up "wine python.exe" from an xterm ( making sure that it's fired up in a new command.com window )
what will happen is that the "python >>>" prompt will appear *ON THE XTERM OUTPUT*
when you run python under standard win32, what happens is that you simply do not see the "python >>>" prompt until you press return a couple of times.
this is a bug which has been fixed for python 2.6 and so it is the fact that it is a known bug in python 2.5 which is hitting a known bug in win32 _and_ wine that is causing the problem.
l.
http://bugs.winehq.org/show_bug.cgi?id=17093
--- Comment #4 from Austin English austinenglish@gmail.com 2010-09-08 12:35:45 CDT --- (In reply to comment #3)
(In reply to comment #2)
I have a feeling that Eric's recent console work may have fixed this. Can you retest in git and/or give clear steps of how to reproduce the problem?
unfortunately it's quite a bit of work to cut out the relevant buggy portions of python, so you'd need to just install python 2.5.2 under wine (which does work!) and then fire up "wine python.exe" from an xterm ( making sure that it's fired up in a new command.com window )
what will happen is that the "python >>>" prompt will appear *ON THE XTERM OUTPUT*
when you run python under standard win32, what happens is that you simply do not see the "python >>>" prompt until you press return a couple of times.
this is a bug which has been fixed for python 2.6 and so it is the fact that it is a known bug in python 2.5 which is hitting a known bug in win32 _and_ wine that is causing the problem.
l.
In wine-1.3.2-77-gec382f4, if I run: $ wine python.exe the '>>>' prompt shows up on the xterm, and I can interact with it there. If I run $ wine start python.exe the '>>>' prompt shows up in its own command.com window, and NOT on the xterm. I can interact with it there. The '>>>' shows up immediately, and does not require pressing return for it to appear.
I'm not sure if it's fixed or not, based on your description.
http://bugs.winehq.org/show_bug.cgi?id=17093
--- Comment #5 from Luke Kenneth Casson Leighton lkcl@lkcl.net 2010-09-08 13:10:42 CDT --- (In reply to comment #4)
In wine-1.3.2-77-gec382f4, if I run: $ wine python.exe the '>>>' prompt shows up on the xterm, and I can interact with it there. If I run $ wine start python.exe the '>>>' prompt shows up in its own command.com window, and NOT on the xterm. I can interact with it there. The '>>>' shows up immediately, and does not require pressing return for it to appear.
ok, then... actually... that's a bug! :)
I'm not sure if it's fixed or not, based on your description.
... no, it isn't :) the "fix" has resulted in "fixing" something that should not have been "fixed".
to get true bug-compatibility with win32, ironically you actually _need_ that initial prompt to _not_ appear... but for the data to not end up coming out on the xterm, either.
but... mmmm... if you had to choose between one and the other, the present situation is infinitely preferable, but strictly speaking it's still a bug (by definition of "complete and total win32 interoperability") but just a different one from the one originally reported :)
l.
http://bugs.winehq.org/show_bug.cgi?id=17093
butraxz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |butraxz@gmail.com
--- Comment #6 from butraxz@gmail.com 2012-05-20 11:06:07 CDT --- This bug has not been updated for two years. The last comment says the problem has changed. Shouldnt this be closed and a new one be opened, if the issue is still valid on 1.5.4 or higher ?
http://bugs.winehq.org/show_bug.cgi?id=17093
--- Comment #7 from butraxz@gmail.com 2013-09-15 08:02:13 CDT --- This ticket has not been updated for long time. Development recommends to check the status on your bug every release or two and let to be known if the bug is still present. If not, mark it fixed. If you are no longer able to put effort to this ticket, you can abandon it.
Is this still an issue with 1.7.2 or higher ?
http://bugs.winehq.org/show_bug.cgi?id=17093
--- Comment #8 from butraxz@gmail.com 2013-12-07 03:06:39 CST --- No answer to update request. Please close as abandoned. If you are able to reproduce with 1.7.8 or higher, feel free to reopen.
https://bugs.winehq.org/show_bug.cgi?id=17093
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |ABANDONED
--- Comment #9 from Austin English austinenglish@gmail.com --- (In reply to butraxz from comment #8)
No answer to update request. Please close as abandoned. If you are able to reproduce with 1.7.8 or higher, feel free to reopen.
Abandoned.
https://bugs.winehq.org/show_bug.cgi?id=17093
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #10 from Austin English austinenglish@gmail.com --- Closing.
-
wine-bugs＠winehq.org