http://bugs.winehq.org/show_bug.cgi?id=11822
Summary: Visual Foxpro 7: Character typing in any edit box freeze application Product: Wine Version: 0.9.55. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: tony.indrali@gmail.com
Any character typing inside Microsoft Visual Foxpro 7 command window and edit box (while editing methods) leads to immediate freeze. This makes application development using Foxpro currently impossible.
http://bugs.winehq.org/show_bug.cgi?id=11822
Tony Indrali tony.indrali@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|critical |major
http://bugs.winehq.org/show_bug.cgi?id=11822
Lei Zhang thestig@google.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|major |normal
--- Comment #1 from Lei Zhang thestig@google.com 2008-03-03 12:11:56 --- Can you attach the console output?
Severity is not major.
http://bugs.winehq.org/show_bug.cgi?id=11822
--- Comment #2 from Tony Indrali tony.indrali@gmail.com 2008-03-03 19:31:00 --- Normal console output does not add new lines between before and after freeze. I need sometime to google how to set debug on or whatever and direct output to a file. Typing WINEDEBUG=ON and running wine again does not show debugging information.
http://bugs.winehq.org/show_bug.cgi?id=11822
--- Comment #3 from Tony Indrali tony.indrali@gmail.com 2008-03-03 19:42:11 --- Created an attachment (id=11098) --> (http://bugs.winehq.org/attachment.cgi?id=11098) Console output: run, not inputing anything, close
http://bugs.winehq.org/show_bug.cgi?id=11822
--- Comment #4 from Tony Indrali tony.indrali@gmail.com 2008-03-03 19:43:27 --- Created an attachment (id=11099) --> (http://bugs.winehq.org/attachment.cgi?id=11099) Console output: run, inputing something, freeze
http://bugs.winehq.org/show_bug.cgi?id=11822
--- Comment #5 from Tony Indrali tony.indrali@gmail.com 2008-03-03 19:52:48 --- (In reply to comment #2)
Normal console output does not add new lines between before and after freeze. I need sometime to google how to set debug on or whatever and direct output to a file. Typing WINEDEBUG=ON and running wine again does not show debugging information.
I take back my words. There are indeed changes to console output even without debugging mode, namely there is something abut oleacc.dll fails with error 1812. I attach 2 console outputs as comparisons, one where <a href="http://bugs.winehq.org/attachment.cgi?id=11098">I open VFP7 then close</a>, the other one where <a href="http://bugs.winehq.org/attachment.cgi?id=11099">I open, input something then freeze</a>.
http://bugs.winehq.org/show_bug.cgi?id=11822
--- Comment #6 from Tony Indrali tony.indrali@gmail.com 2008-03-04 02:36:52 --- (In reply to comment #5)
I take back my words. There are indeed changes to console output even without debugging mode, namely there is something abut oleacc.dll fails with error 1812. I attach 2 console outputs as comparisons, one where <a
Really sorry. Seems BOTH console outputs, as attached, has that oleacc.dll error. I'll get back to this matter after I have some free time.
http://bugs.winehq.org/show_bug.cgi?id=11822
Tony Indrali tony.indrali@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |minor Priority|P2 |P3 Summary|Visual Foxpro 7: Character |Foxpro 7 over VNC: Character |typing in any edit box |typing in any edit box |freeze application |freeze application
--- Comment #7 from Tony Indrali tony.indrali@gmail.com 2008-03-04 05:45:36 --- I figured the condition for replicating the bug. The freezing only happens if I run Foxpro 7 over VNC. But it doesn't happen when I still use wine 0.9.54. I have edited the title to reflect the condition.
http://bugs.winehq.org/show_bug.cgi?id=11822
Tony Indrali tony.indrali@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|minor |normal Priority|P3 |P2 Summary|Foxpro 7 over VNC: Character|All applications over VNC: |typing in any edit box |Applications freeze for any |freeze application |letters input
--- Comment #8 from Tony Indrali tony.indrali@gmail.com 2008-03-04 20:43:37 --- Checking what I suspected, I tried to type some letters while winemine windows active. Winemine freezed.
I suspect all wine's applications over VNC will freeze since 0.9.55, 0.9.56 (as of this writing). This is a regression from 0.9.54. I also change the title again to reflect this finding.
And can someone kindly enough provide me with the command line instruction for debian etch on how to provide the proper console output of debug mode? I have tried winedbg, then keep entering "cont" fail because of an error. But that same error is successfully ignored when running with plain wine instead of winedbg. I also tried in the console typing WINEDEBUG=warn+all but there is no effect. Is the log written somewhere?
http://bugs.winehq.org/show_bug.cgi?id=11822
Tony Indrali tony.indrali@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |major
--- Comment #9 from Tony Indrali tony.indrali@gmail.com 2008-03-04 20:48:55 --- Since severity major is defined as "Major loss of functionality for a wide range of applications" and this bug impacts almost all applications, albeit over VNC, I change severity to major.
http://bugs.winehq.org/show_bug.cgi?id=11822
Lei Zhang thestig@google.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Keywords| |regression
--- Comment #10 from Lei Zhang thestig@google.com 2008-03-04 21:34:07 --- Yes, I see it with Wine's built in regedit and notepad. It worked fine in Wine 0.9.40... regression test under way.
http://bugs.winehq.org/show_bug.cgi?id=11822
--- Comment #11 from Lei Zhang thestig@google.com 2008-03-04 21:52:23 --- Regression test says:
commit e14261dbb737e6177be95df6cea787401c1f7ad1 Author: Alexandre Julliard julliard@winehq.org Date: Wed Feb 6 20:37:41 2008 +0100
winex11: Use the gdi display when initializing the keyboard to avoid creating a second display connection.
http://bugs.winehq.org/show_bug.cgi?id=11822
--- Comment #12 from Tony Indrali tony.indrali@gmail.com 2008-03-10 01:41:55 --- 0.9.57 still have this problem.
http://bugs.winehq.org/show_bug.cgi?id=11822
--- Comment #13 from Lei Zhang thestig@google.com 2008-03-10 15:12:20 --- Weird, I'm on a different machine today and I'm not seeing this problem.
http://bugs.winehq.org/show_bug.cgi?id=11822
--- Comment #14 from Tony Indrali tony.indrali@gmail.com 2008-03-10 20:01:45 --- hmm.. I use xtightvnc server and viewer, with open ssh set up between server and a port in client I used. All standard package of debian etch with backport activated. Does the setting such as above may change the result?
Is your different machine using 0.9.57?
http://bugs.winehq.org/show_bug.cgi?id=11822
--- Comment #15 from Lei Zhang thestig@google.com 2008-03-10 20:03:55 --- yes, running the latest version of Wine from git. I am using realvnc with this machine. I think my other machine has tightvnc. Let me try tightvnc here and see what happens.
http://bugs.winehq.org/show_bug.cgi?id=11822
--- Comment #16 from Lei Zhang thestig@google.com 2008-03-11 15:02:03 --- Well, now it looks like I have one machine where this problem occurs and another where it doesn't.
http://bugs.winehq.org/show_bug.cgi?id=11822
--- Comment #17 from Tony Indrali tony.indrali@gmail.com 2008-03-11 20:17:16 --- This reminds me to a linux "bug" where a barcode reader can't be detected in PS/2 port unless a keyboard is attached serially..
By any chance, is the keyboard you use in one of the client is PS/2 based and the other is USB based? How about the server's keyboard?
http://bugs.winehq.org/show_bug.cgi?id=11822
--- Comment #18 from Lei Zhang thestig@google.com 2008-03-11 21:14:28 --- The broken one is ps/2, the working one is a vmware instance.
http://bugs.winehq.org/show_bug.cgi?id=11822
--- Comment #19 from Tony Indrali tony.indrali@gmail.com 2008-03-11 22:09:46 --- (In reply to comment #18)
The broken one is ps/2, the working one is a vmware instance.
Is the working one a vmware instance that is hosted in the same machine that is broken? Are you aware whether vmware emulate keyboard as a PS/2 or USB, or it depends on config file?
I'll test the USB keyboard when I can access it, which is over the weekend.
http://bugs.winehq.org/show_bug.cgi?id=11822
--- Comment #20 from Tony Indrali tony.indrali@gmail.com 2008-03-27 23:23:41 --- (In reply to comment #19)
I'll test the USB keyboard when I can access it, which is over the weekend.
It seems I don't have any USB keyboard. I'm calling others to help testing this bug using USB keyboard. I hope USB keyboard can be used as temporary workaround.
http://bugs.winehq.org/show_bug.cgi?id=11822
David Austin d.austin@computer.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |d.austin@computer.org
--- Comment #21 from David Austin d.austin@computer.org 2008-04-01 18:11:08 --- I'm also having this problem, with the Pokerstars application. Typing anything freezes wine.
I have a hard time believing that it has anything to do with PS/2 vs USB keyboards. Surely the X server should abstract that away. Besides all other (non-wine) applications work just fine.
http://bugs.winehq.org/show_bug.cgi?id=11822
--- Comment #22 from Tony Indrali tony.indrali@gmail.com 2008-04-02 09:57:04 --- 0.9.58 still has this bug.
Yeah, probably PS/2 vs. USB keyboard won't matter but I'll try when I can get my hand to a USB keyboard anyway. I just wish there is some easy workaround. This bug is a show stopper for me.. *sigh*. I guess I'll just stuck my self with older wine version.
http://bugs.winehq.org/show_bug.cgi?id=11822
--- Comment #23 from Austin English austinenglish@gmail.com 2008-04-02 21:29:06 --- Created an attachment (id=11816) --> (http://bugs.winehq.org/attachment.cgi?id=11816) patch attempt
(In reply to comment #22)
0.9.58 still has this bug.
Yeah, probably PS/2 vs. USB keyboard won't matter but I'll try when I can get my hand to a USB keyboard anyway. I just wish there is some easy workaround. This bug is a show stopper for me.. *sigh*. I guess I'll just stuck my self with older wine version.
Can you try the attached patch?
http://bugs.winehq.org/show_bug.cgi?id=11822
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #11816|0 |1 is obsolete| |
--- Comment #24 from Austin English austinenglish@gmail.com 2008-04-02 22:46:29 --- (From update of attachment 11816) Ignore this, patch is incorrect, sorry for the noise.
http://bugs.winehq.org/show_bug.cgi?id=11822
--- Comment #25 from Tony Indrali tony.indrali@gmail.com 2008-04-05 04:19:52 --- I was so happy.. :-( 0.9.59 still has this bug.
http://bugs.winehq.org/show_bug.cgi?id=11822
--- Comment #26 from Lei Zhang thestig@google.com 2008-04-15 19:25:14 --- As an workaround. you can easily get the old behavior if you call X11DRV_InitKeyboard( thread_display() ); instead of X11DRV_InitKeyboard( gdi_display ); in x11drv_main.c.
http://bugs.winehq.org/show_bug.cgi?id=11822
--- Comment #27 from Tony Indrali tony.indrali@gmail.com 2008-04-15 20:00:21 --- (In reply to comment #26)
Thanks, I'll try it after I finish learning this git thing.
http://bugs.winehq.org/show_bug.cgi?id=11822
--- Comment #28 from Tony Indrali tony.indrali@gmail.com 2008-04-23 00:30:38 --- In my previous setting that doesn't work, running wine directly (via ssh -Y tunneling) works.
The setting that doesn't work is Debian Etch with:
/etc/inetd.conf containing vnc-1024x768x16 stream tcp nowait nobody /usr/bin/Xtightvnc Xtightvnc -inetd -query localhost -fp tcp/localhost:7100 -once -geometry 1024x768 -depth 16
/etc/services containing vnc-1024x768x16 5950/tcp # VNC :50
and logging in to GDM remotely and run wine, doesn't work.
http://bugs.winehq.org/show_bug.cgi?id=11822
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED
--- Comment #29 from Alexandre Julliard julliard@winehq.org 2008-05-28 14:53:21 --- Probably yet another X11 locking bug, should be fixed by removal of XInitThreads.
http://bugs.winehq.org/show_bug.cgi?id=11822
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #30 from Alexandre Julliard julliard@winehq.org 2008-05-31 04:18:32 --- Closing bugs fixed in 1.0-rc3.