http://bugs.winehq.org/show_bug.cgi?id=18543
Summary: Text input form and pulldown menu stop functioning in wine 1.1.x release Product: Wine Version: 1.1.18 Platform: PC OS/Version: FreeBSD Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: gjin@ubicom.com
The application is a MS WINDOW configuration tool, which uses a number of widgets, like checkbox, text input filed (form), pulldown menu, etc. The last working version I used is wine-0.9.61 with FreeBSD 6.3-R/6.4-R. All those widgets work well.
Since FreeBSD 7.x is no longer to compile wine-0.9.61, so I built from wine-1.1.x to 1.1.18 in past a couple of months, the most things work well except the "text input field (form)" and the "pulldown menu" stop working.
In a working case, when clicking on the text input field, it will concaved in and waiting for input. In wine-1.1.x, concaving will not happen and it is not accept any typing. In working wine-0.9.61, the pulldown menu will concave in and show a upside down triangle button for choosing a pulldown items. In wine-1.1.x, this will not happen either -- see attached GIF image for non working case.
http://bugs.winehq.org/show_bug.cgi?id=18543
--- Comment #1 from Austin English austinenglish@gmail.com 2009-05-20 15:32:04 --- Is there a download available?
What is the earliest compiling version of wine on FreeBSD 7? Can you test there? How about a regression test? http://wiki.winehq.org/RegressionTesting
http://bugs.winehq.org/show_bug.cgi?id=18543
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Text input form and |Text input form and |pulldown menu stop |pulldown menu stop |functioning in wine 1.1.x |functioning |release | Severity|major |normal
--- Comment #2 from Vitaliy Margolen vitaliy@kievinfo.com 2009-05-20 21:26:20 --- Not major - http://bugs.winehq.org/page.cgi?id=fields.html#bug_severity
Try with latest wine-1.1.21 version.
http://bugs.winehq.org/show_bug.cgi?id=18543
--- Comment #3 from gjin@ubicom.com 2009-05-23 14:37:44 --- Tried 1.1.21.1 under FreeBSD 7.1-Release and 7.2-Release. Those functions seem to work a little bit but in a very difficult way.
Under FreeBSD 7.2-Release, Without hald running, those functions seem not working. With hald running, clicking on existing text areas seems not activate those functions. Clicking on the text fields will see flash light, which means there is activity, so I keep trying to click. Clicking on the text files somewhere at least 10 times may activate input field sometimes. Typically slightly to the right of the text input field. Moving mouse around far right the pulldown menu and keep clicking may show the pulldown button (it is hidden, but supposed alway to show up) with the upper side down triangle.
Under FreeBSD 7.1-Release, build wine-1.1.21.1 with/without HAL support are the same. Pulldown menu does not function at all (no flashing light when clicking). The text input acts the same as in FreeBSD 7.2-R.
One thing noticed in activating the text input field. If multiple of Text Input fields are next to each other, then clicking on one and moving mouse to the other filed and click again (must be fast enough), then this may activate the input field.
It seems these functionality issues may be related to Xorg releases. FreeBSD 7.1-R uses xorg-7.3_2 and FreeBSD 7.2-R uses xorg-7.4_1.
http://bugs.winehq.org/show_bug.cgi?id=18543
--- Comment #4 from Austin English austinenglish@gmail.com 2010-03-11 17:21:23 --- This is your friendly reminder that there has been no bug activity for 8 months. Is this still an issue in current (1.1.40 or newer) wine?
http://bugs.winehq.org/show_bug.cgi?id=18543
--- Comment #5 from gjin@ubicom.com 2010-03-29 14:47:57 --- The same problem presents on Ubuntu Linux 9.x as well. I will try the latest wine on FreeBSD 7.3 and post the result in a few weeks.
http://bugs.winehq.org/show_bug.cgi?id=18543
--- Comment #6 from gjin@ubicom.com 2010-03-31 17:07:46 --- Tested on 1.1.39 and problem still presents, but little bit less serious because the working around described below can make things to work.
Multiple click will bring down the pull-down menu. For text field, multiple click does not work well, but clicking on a neighbor field then quickly move toward target text field and then click on the text field will activate the text field.
http://bugs.winehq.org/show_bug.cgi?id=18543
--- Comment #7 from gjin@ubicom.com 2010-07-14 20:50:42 --- Created an attachment (id=29609) --> (http://bugs.winehq.org/attachment.cgi?id=29609) wine 1.1.3 crash log
http://bugs.winehq.org/show_bug.cgi?id=18543
--- Comment #8 from gjin@ubicom.com 2010-07-14 20:52:08 --- Created an attachment (id=29610) --> (http://bugs.winehq.org/attachment.cgi?id=29610) compiling error in working wine, and it may be related to this issue
http://bugs.winehq.org/show_bug.cgi?id=18543
--- Comment #9 from gjin@ubicom.com 2010-07-14 20:53:34 --- The latest 1.2-rc7 still have the same problem. I have bisected the problem, and the latest working version is 1.1.2, and the broken version is 1.1.4.
1.1.3 crashes (see attached log -- wine1.1.3-exec-error) so there is hard to tell if it is already broken, but it looks like a point the broken starts.
One sign may related to this broken is that All working versions (including 1.1.3) all have a compiling error in freetype.c (see attached error log -- wine-compiling-error-onWorking-vresion). By undef FT_MULFIX_INLINED in freetype2/freetype/freetype.h, wine will be built and run successfully.
+ #undef FT_MULFIX_INLINED 3621 #ifdef FT_MULFIX_INLINED 3622 #define FT_MulFix( a, b ) FT_MULFIX_INLINED( a, b ) 3623 #else 3624 FT_EXPORT( FT_Long ) 3625 FT_MulFix( FT_Long a, 3626 FT_Long b ); 3627 #endif /usr/local/include/freetype2/freetype/freetype.h: unmodified, readonly: line 3621 of 3879 [93%]
Hopefully, this will help to nail down the problem.
http://bugs.winehq.org/show_bug.cgi?id=18543
--- Comment #10 from Dmitry Timoshkov dmitry@codeweavers.com 2010-07-15 01:15:40 --- FreeType compilation error has nothing to do with this bug. You may apply http://www.winehq.org/pipermail/wine-patches/2008-September/060764.html to workaround it while performing the regression testing.
http://bugs.winehq.org/show_bug.cgi?id=18543
--- Comment #11 from gjin@ubicom.com 2010-07-16 17:31:08 --- Created an attachment (id=29638) --> (http://bugs.winehq.org/attachment.cgi?id=29638) change between 1.1.2 and 1.1.4 to cause the problem
http://bugs.winehq.org/show_bug.cgi?id=18543
--- Comment #12 from gjin@ubicom.com 2010-07-16 17:31:50 --- The problem has been identified and reversing following change will fix the problem (file is also attached):
--- dlls/comctl32/listview.c 2010-07-16 15:13:59.000000000 -0700 +++ dlls/comctl32/listview.c-1.1.4 2008-09-05 08:28:27.000000000 -0700 @@ -8588,10 +8588,7 @@ if (!notify(infoPtr, NM_RELEASEDCAPTURE)) return 0;
if (!infoPtr->bFocus) - { bReceivedFocus = TRUE; - SetFocus(infoPtr->hwndSelf); - }
/* set left button down flag and record the click position */ infoPtr->bLButtonDown = TRUE; @@ -8721,6 +8718,9 @@ LISTVIEW_DelayedEditItem); }
+ if (!infoPtr->bFocus) + SetFocus(infoPtr->hwndSelf); + return 0; }
http://bugs.winehq.org/show_bug.cgi?id=18543
--- Comment #13 from gjin@ubicom.com 2010-07-16 18:46:08 --- In 1.2 release, the failed change no longer exists (since 1.1.7).
The current problem is more obvious --
Press down button DOES NOT activate the text/menu field, nor release the button.
Press down button, move the mouse, then release button WILL activate the text/menu field. However, activation depends on where the mouse moved to. If clicked on line 1 and moved mouse to line x, then line x is activated, which is incorrect.
http://bugs.winehq.org/show_bug.cgi?id=18543
--- Comment #14 from gjin@ubicom.com 2010-07-16 19:42:13 --- Created an attachment (id=29640) --> (http://bugs.winehq.org/attachment.cgi?id=29640) patch to fix this problem in latest release-1.2
Attached patch fixes this problem.
http://bugs.winehq.org/show_bug.cgi?id=18543
Dan Kegel dank@kegel.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch CC| |dank@kegel.com
--- Comment #15 from Dan Kegel dank@kegel.com 2011-06-14 18:42:11 CDT --- Is this still an issue in latest git?
If so, you can speed things up by writing a wine test case to verify that your fix is correct.
http://bugs.winehq.org/show_bug.cgi?id=18543
--- Comment #16 from jin gjin@ubicom.com 2012-05-03 19:40:29 CDT --- Tested on the latest 1.4.1 and the problem is the same. Applying the same patch will fix the problem. This requires human interaction by clicking mouse on input field (box), so how would you suggest to write a test case? Did you mean write a description or an automated scripting? I do not know if the later is doable.
http://bugs.winehq.org/show_bug.cgi?id=18543
--- Comment #17 from Austin English austinenglish@gmail.com --- This is your friendly reminder that there has been no bug activity for 2 years. Is this still an issue in current (1.7.18 or newer) wine?
http://bugs.winehq.org/show_bug.cgi?id=18543
--- Comment #18 from jin gjin@ubicom.com --- I am not able to use the latest wine, thus no way to verify this problem till I can get wine built and run on 64-bit FreeBSD machine properly. My last working build was on a 32-bit i386 (FreeBSD 8.x) with wine 1.4 release. The build process is following. Does anyone have idea on what could cause this run time error?
FreeBSD-8.4.amd64 % git clone git://source.winehq.org/git/wine.git FreeBSD-8.4.amd64 %./configure --enable-win64 % make && make install FreeBSD-8.4.amd64 % wine64 --version wine-1.7.18-92-gb01fc1a FreeBSD-8.4.amd64 % % wine64 ubi32-prof-093.exe wine: failed to map the shared user data: c0000018
old build% wine --version wine-1.4
http://bugs.winehq.org/show_bug.cgi?id=18543
--- Comment #19 from Austin English austinenglish@gmail.com --- (In reply to jin from comment #18)
I am not able to use the latest wine, thus no way to verify this problem till I can get wine built and run on 64-bit FreeBSD machine properly. My last working build was on a 32-bit i386 (FreeBSD 8.x) with wine 1.4 release. The build process is following. Does anyone have idea on what could cause this run time error?
FreeBSD-8.4.amd64 % git clone git://source.winehq.org/git/wine.git FreeBSD-8.4.amd64 %./configure --enable-win64 % make && make install FreeBSD-8.4.amd64 % wine64 --version wine-1.7.18-92-gb01fc1a FreeBSD-8.4.amd64 % % wine64 ubi32-prof-093.exe wine: failed to map the shared user data: c0000018
old build% wine --version wine-1.4
Wine64 does not work on FreeBSD, only Linux currently. You'll need to build wine as a 32-bit application.
http://bugs.winehq.org/show_bug.cgi?id=18543
--- Comment #20 from jin gjin@ubicom.com --- Pulled the latest wine source 1.7.19 released yesterday and build on 32-bit FreeBSD. The problem is the same, and the patch to fix is also the same as 1.4.
*** dlls/comctl32/listview.c.orig Fri May 16 12:06:48 2014 --- dlls/comctl32/listview.c Sat May 17 13:42:36 2014 *************** *** 10162,10167 **** --- 10162,10170 ---- lvHitTestInfo.pt.x = x; lvHitTestInfo.pt.y = y;
+ if (!infoPtr->bFocus) + SetFocus(infoPtr->hwndSelf); + nItem = LISTVIEW_HitTest(infoPtr, &lvHitTestInfo, TRUE, TRUE); TRACE("at %s, nItem=%d\n", wine_dbgstr_point(&pt), nItem); if ((nItem >= 0) && (nItem < infoPtr->nItemCount)) *************** *** 10235,10243 **** } else { - if (!infoPtr->bFocus) - SetFocus(infoPtr->hwndSelf); - /* remove all selections */ if (!(wKey & MK_CONTROL) && !(wKey & MK_SHIFT)) LISTVIEW_DeselectAll(infoPtr); --- 10238,10243 ---- *************** *** 10316,10324 **** LISTVIEW_DelayedEditItem); }
- if (!infoPtr->bFocus) - SetFocus(infoPtr->hwndSelf); - return 0; }
--- 10316,10321 ----
https://bugs.winehq.org/show_bug.cgi?id=18543
--- Comment #21 from Austin English austinenglish@gmail.com --- Could you please attach a +listview,+tid trace?
https://bugs.winehq.org/show_bug.cgi?id=18543
--- Comment #22 from jin gjin@ubicom.com --- (In reply to Austin English from comment #21)
Could you please attach a +listview,+tid trace?
Can you be more specific on how to do it?
https://bugs.winehq.org/show_bug.cgi?id=18543
--- Comment #23 from Austin English austinenglish@gmail.com --- (In reply to jin from comment #22)
(In reply to Austin English from comment #21)
Could you please attach a +listview,+tid trace?
Can you be more specific on how to do it?
http://wiki.winehq.org/FAQ#head-16da35b6327024d6ea576e3678488b16862d0f5e
WINEDEBUG=+listview,+tid wine ...
if you need further help, please use the forums.
https://bugs.winehq.org/show_bug.cgi?id=18543
--- Comment #24 from Austin English austinenglish@gmail.com --- This is your friendly reminder that there has been no bug activity for over a year. Is this still an issue in current (1.7.51 or newer) wine?
https://bugs.winehq.org/show_bug.cgi?id=18543
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |ABANDONED Status|UNCONFIRMED |RESOLVED
--- Comment #25 from Ken Sharp imwellcushtymelike@gmail.com --- Nothing since 2014.
https://bugs.winehq.org/show_bug.cgi?id=18543
André H. nerv@dawncrow.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED CC| |nerv@dawncrow.de
--- Comment #26 from André H. nerv@dawncrow.de --- closing abandoned