http://bugs.winehq.org/show_bug.cgi?id=25703
Summary: VMWare infrastructure client Product: Wine Version: 1.3.10 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: jan.ryen@gmail.com
Created an attachment (id=32745) --> (http://bugs.winehq.org/attachment.cgi?id=32745) error view
VMWare infrastructure client (VMware-viclient.exe - 57001780 bytes) installs fine, but when excecuting the installed program i recieve an error in VpxClient.exe
http://bugs.winehq.org/show_bug.cgi?id=25703
--- Comment #1 from jan.ryen@gmail.com 2011-01-06 07:56:41 CST --- Created an attachment (id=32746) --> (http://bugs.winehq.org/attachment.cgi?id=32746) error view2
http://bugs.winehq.org/show_bug.cgi?id=25703
jan.ryen@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- URL| |http://www.4shared.com/file | |/ivb5SCle/VMware-viclient.h | |tml CC| |jan.ryen@gmail.com
--- Comment #2 from jan.ryen@gmail.com 2011-01-06 08:05:48 CST --- Se URL for URL to download installation file for application in question.
http://bugs.winehq.org/show_bug.cgi?id=25703
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- URL|http://www.4shared.com/file | |/ivb5SCle/VMware-viclient.h | |tml |
--- Comment #3 from Austin English austinenglish@gmail.com 2011-01-06 13:07:34 CST --- Terminal output?
Please don't post links to pirated software. If a public download is available, post that instead.
Though this probably wants some very low level stuff, and will be difficult to get working in Wine. You're better off using the native Linux version...
http://bugs.winehq.org/show_bug.cgi?id=25703
jan.ryen@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #32745|0 |1 is obsolete| | Attachment #32746|0 |1 is obsolete| |
--- Comment #4 from jan.ryen@gmail.com 2011-01-06 14:23:18 CST --- Created an attachment (id=32749) --> (http://bugs.winehq.org/attachment.cgi?id=32749) xsession errors file
http://bugs.winehq.org/show_bug.cgi?id=25703
--- Comment #5 from jan.ryen@gmail.com 2011-01-06 14:24:25 CST --- Viclient is GPL software and part of ESXi. ESXi is a hypervisor from vmware that's lisenced as free software under some conditions. The link was not to pirated software, however if u need to obtain the original it can be downloaded from vmwares site under the section for ESXi server. There is no linux native version or port available. The package is a windows installer package and the version i'm using is now deprecated however i still use it for compatibility reasons.
I attached a text file containing xsession errors. It seems to describe the error at hand. first error starts at "wine: Unhandled exception 0xe0434f4d at address 0x7b835102 (thread 0040), starting debugger..."
http://bugs.winehq.org/show_bug.cgi?id=25703
knan-wine@anduin.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |knan-wine@anduin.net
--- Comment #6 from knan-wine@anduin.net 2011-01-29 17:17:05 CST --- Looks like it wants .NET System.Windows.Forms. Try installing the latest Mono via winetricks.
http://bugs.winehq.org/show_bug.cgi?id=25703
--- Comment #7 from butraxz@gmail.com 2013-08-05 12:35:24 CDT --- This ticket has not been updated for over 900 days. 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.
Is this still an issue with 1.7.0 or higher ?
https://bugs.winehq.org/show_bug.cgi?id=25703
Wylda wylda@volny.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |wylda@volny.cz
--- Comment #8 from Wylda wylda@volny.cz --- Created attachment 49749 --> https://bugs.winehq.org/attachment.cgi?id=49749 wine-1.7.28 console log
Still present in wine-1.7.28.
I tested VMware-viclient-all-4.0.0-934018.exe. Console log attached.
MD5SUM: 5174083df2fef7d4aed3b1c3a64294d0 SHA1SUM: 8576d28b58fa2ef8ae4d99f8e1645f25292d9537
https://bugs.winehq.org/show_bug.cgi?id=25703
Wylda wylda@volny.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #32749|0 |1 is obsolete| |
https://bugs.winehq.org/show_bug.cgi?id=25703
Wylda wylda@volny.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |dotnet, download Status|UNCONFIRMED |NEW URL| |https://my.vmware.com/web/v | |mware/details?productId=136 | |&downloadGroup=VC40U4B Ever confirmed|0 |1
--- Comment #9 from Wylda wylda@volny.cz --- Confirming and filling some fields.
https://bugs.winehq.org/show_bug.cgi?id=25703
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords|dotnet | CC| |focht@gmx.net Component|-unknown |mscoree Summary|VMWare infrastructure |VMWare infrastructure |client |client 4.0 fails with | |Wine-Mono
--- Comment #10 from Anastasius Focht focht@gmx.net --- Hello folks,
that's a Wine-Mono problem, not .NET Framework. Removing 'dotnet' keyword.
--- snip --- [ERROR] FATAL UNHANDLED EXCEPTION: System.NotSupportedException: Operation is not supported. at VpxClient.SecuredTextBox.get_Text () [0x00000] in <filename unknown>:0 at System.Windows.Forms.TextBoxBase.CaretMoved (System.Object sender, System.EventArgs e) [0x00000] in <filename unknown>:0 at System.Windows.Forms.TextBoxBase.ScrollToCaret () [0x00000] in <filename unknown>:0 at System.Windows.Forms.TextBoxBase.CreateHandle () [0x00000] in <filename unknown>:0 at System.Windows.Forms.Control.CreateControl () [0x00000] in <filename unknown>:0 at (wrapper remoting-invoke-with-check) System.Windows.Forms.Control:CreateControl () at System.Windows.Forms.Control.CreateControl () [0x00000] in <filename unknown>:0 at System.Windows.Forms.Control.SetVisibleCore (Boolean value) [0x00000] in <filename unknown>:0 at System.Windows.Forms.Form.SetVisibleCore (Boolean value) [0x00000] in <filename unknown>:0 at System.Windows.Forms.Control.set_Visible (Boolean value) [0x00000] in <filename unknown>:0 at System.Windows.Forms.Control.Show () [0x00000] in <filename unknown>:0 at (wrapper remoting-invoke-with-check) System.Windows.Forms.Control:Show () at VpxClient.Program.Main (System.String[] commandline) [0x00000] in <filename unknown>:0 --- snip ---
Regards
https://bugs.winehq.org/show_bug.cgi?id=25703
Vincent Povirk madewokherd@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- URL|https://my.vmware.com/web/v |https://kb.vmware.com/s/art |mware/details?productId=136 |icle/2089791 |&downloadGroup=VC40U4B |
https://bugs.winehq.org/show_bug.cgi?id=25703
--- Comment #11 from Vincent Povirk madewokherd@gmail.com --- Tried with dotnet core winforms (wine-mono master branch) and got a similar exception, with an entirely different path to get there:
[00000009:] EXCEPTION handling: System.NotSupportedException: Specified method is not supported.
"Launcher UI" tid=00000009 this=01DB0120 , thread handle : 00583F68, state : not waiting at VpxClient.SecuredTextBox.get_Text () [0x00017] in <e97f4f3658ae4be5a90197e35ebc7c8a>:0 at System.Windows.Forms.TextBox.WndProc (System.Windows.Forms.Message&) [0x0009e] in <6a676adda4bb4b01a42b7ddcebf1aba2>:0 at System.Windows.Forms.Control/ControlNativeWindow.OnMessage (System.Windows.Forms.Message&) [0x00001] in <6a676adda4bb4b01a42b7ddcebf1aba2>:0 at System.Windows.Forms.Control/ControlNativeWindow.WndProc (System.Windows.Forms.Message&) [0x000b3] in <6a676adda4bb4b01a42b7ddcebf1aba2>:0 at System.Windows.Forms.NativeWindow.Callback (intptr,int,intptr,intptr) [0x00030] in <6a676adda4bb4b01a42b7ddcebf1aba2>:0 at (wrapper native-to-managed) System.Windows.Forms.NativeWindow.Callback (intptr,int,intptr,intptr) <0x00067> at <unknown> <0xffffffff> at (wrapper managed-to-native) System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW (System.Windows.Forms.NativeMethods/MSG&) <0x00012> at System.Windows.Forms.Application/ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop (intptr,int,int) [0x001d7] in <6a676adda4bb4b01a42b7ddcebf1aba2>:0 at System.Windows.Forms.Application/ThreadContext.RunMessageLoopInner (int,System.Windows.Forms.ApplicationContext) [0x00282] in <6a676adda4bb4b01a42b7ddcebf1aba2>:0 at System.Windows.Forms.Application/ThreadContext.RunMessageLoop (int,System.Windows.Forms.ApplicationContext) [0x0001a] in <6a676adda4bb4b01a42b7ddcebf1aba2>:0 at (wrapper remoting-invoke-with-check) System.Windows.Forms.Application/ThreadContext.RunMessageLoop (int,System.Windows.Forms.ApplicationContext) [0x00033] in <6a676adda4bb4b01a42b7ddcebf1aba2>:0 at System.Windows.Forms.Application.Run (System.Windows.Forms.Form) [0x0000d] in <6a676adda4bb4b01a42b7ddcebf1aba2>:0 at VpxClient.Program.Main (string[]) [0x000c1] in <e97f4f3658ae4be5a90197e35ebc7c8a>:0 at (wrapper runtime-invoke) <Module>.runtime_invoke_void_object (object,intptr,intptr,intptr) [0x00027] in <e97f4f3658ae4be5a90197e35ebc7c8a>:0
Examining this get_Text method, it seems it throws NotSupportedException if Control.RecreatingHandle is false.
OK, so why does TextBox.WndProc call get_Text? Because of this code: 896 if ((m.Msg == Interop.WindowMessages.WM_PAINT || m.Msg == Interop.WindowMessages.WM_KILLFOCUS) && 897 !this.GetStyle(ControlStyles.UserPaint) && 898 string.IsNullOrEmpty(this.Text) && 899 !this.Focused)
But this is the implementation of winforms used by native .NET, isn't it? So it must work there somehow, right?
Apparently not, it seems this was a recent addition:
commit a31aa1d4232dbc54dd8b763128c3b06104f5e9af Author: Stefan Stefanov stefanov-stefan@users.noreply.github.com Date: Tue Jan 22 20:54:18 2019 +0200
Added PlaceholderText functionality (#238)
If we check whether placeholder text has been set BEFORE checking this.Text, it works. That seems wrong, because somehow WM_PAINT can work without calling get_Text, but it does demonstrate that this is a bug in dotnet core winforms.
https://bugs.winehq.org/show_bug.cgi?id=25703
--- Comment #12 from Vincent Povirk madewokherd@gmail.com --- I can see why WM_PAINT works. It's handled by the builtin edit control which keeps track of text separately.
So the expectation is that the TextBox control only accesses Text once, while creating the handle. It'll be interesting to see what upstream thinks about this.
https://bugs.winehq.org/show_bug.cgi?id=25703
Vincent Povirk madewokherd@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |madewokherd@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=25703
--- Comment #13 from Vincent Povirk madewokherd@gmail.com --- Upstream issue filed: https://github.com/dotnet/winforms/issues/1109
https://bugs.winehq.org/show_bug.cgi?id=25703
--- Comment #14 from Vincent Povirk madewokherd@gmail.com --- Pushed a work-around to wine-mono for now.
https://bugs.winehq.org/show_bug.cgi?id=25703
--- Comment #15 from Vincent Povirk madewokherd@gmail.com --- Should be fixed by https://source.winehq.org/git/wine.git/commit/faa7564d375a6d4672da0bfe35f367...
Upstream winforms has also merged a fix (different from my work-around).