October 2021 - Wine-bugs - list.winehq.org

[Bug 51871] New: PSScript fails with 0x80041002 (WBEM_E_NOT_FOUND) ( system property L"__Derivation" not implemented)
by WineHQ Bugzilla 22 Oct '21

22 Oct '21

https://bugs.winehq.org/show_bug.cgi?id=51871 Bug ID: 51871 Summary: PSScript fails with 0x80041002 (WBEM_E_NOT_FOUND) ( system property L"__Derivation" not implemented) Product: Wine Version: 6.19 Hardware: x86-64 URL: https://www.powershellgallery.com/packages/Traverse/0. 6/Content/Private%5CGet-WMICustom.ps1 OS: Linux Status: NEW Keywords: download, source Severity: normal Priority: P2 Component: wmi&wbemprox Assignee: wine-bugs(a)winehq.org Reporter: xerox.xerox2000x(a)gmail.com Distribution: --- Hi, I`d like to make powershell script from the URL to work in wine in Powershell 7. (Background: Powershell 7 doesn`t have Get-WMIObject and GetCIMInstance doesn`t work; if the above script works it`s simple to just write an own simple Get-WMIObject which is for example used by chocolatey to retrieve some properties from win32_operatingsystem) Output from running script in psconsole: Out-Default: The following exception occurred while retrieving the type name hierarchy: "Error code: 0x80041002". In the console: 07f0:fixme:wbemprox:get_system_propval system property L"__Derivation" not implemented Actually it turns out that returning complete stub for "__Derivation" is enough to make the script enough work for my purpose I now use hack below, and that`s enough to fix this bug for me, but I guess it`s not ok enough for inclusion in wine. So if someone could write proper stub or advise howto improve patch that would be great diff --git a/dlls/wbemprox/query.c b/dlls/wbemprox/query.c index 77ed27e105d..b253f19a6ed 100644 --- a/dlls/wbemprox/query.c +++ b/dlls/wbemprox/query.c @@ -1006,6 +1006,13 @@ static HRESULT get_system_propval( const struct view *view, UINT table_index, UI if (type) *type = CIM_STRING; return S_OK; } + if (!wcsicmp( name, L"__DERIVATION" )) + { + if (ret) + V_VT( ret ) = VT_BSTR | VT_ARRAY; + if (type) *type = CIM_STRING | VT_ARRAY; + return S_OK; + } FIXME("system property %s not implemented\n", debugstr_w(name)); return WBEM_E_NOT_FOUND; } diff --git a/dlls/wbemprox/tests/query.c b/dlls/wbemprox/tests/query.c index 69bb8e7977e..9bb8d559b06 100644 --- a/dlls/wbemprox/tests/query.c +++ b/dlls/wbemprox/tests/query.c @@ -1642,6 +1642,7 @@ static void test_Win32_VideoController( IWbemServices *services ) if (hr != S_OK) break; check_property( obj, L"__CLASS", VT_BSTR, CIM_STRING ); + check_property( obj, L"__DERIVATION", VT_BSTR | VT_ARRAY, CIM_STRING | CIM_FLAG_ARRAY); check_property( obj, L"__GENUS", VT_I4, CIM_SINT32 ); check_property( obj, L"__NAMESPACE", VT_BSTR, CIM_STRING ); check_property( obj, L"__PATH", VT_BSTR, CIM_STRING ); -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 41700] New: "Install Now" and "Customize installation" buttons are invisible in Python 3.5 installer
by wine-bugs＠winehq.org 22 Oct '21

22 Oct '21

https://bugs.winehq.org/show_bug.cgi?id=41700 Bug ID: 41700 Summary: "Install Now" and "Customize installation" buttons are invisible in Python 3.5 installer Product: Wine Version: 1.9.23 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- The "Install Now" and "Customize installation" buttons do not appear on either the regular Python 3.5 installer or the Python 3.5 web installer, not even if you hover the mouse over the buttons or press the tab key repeatedly. However, the installation continues if you click where the button should be, and the tab key appears to move focus onto and off of the buttons even though there is no visual feedback. Note that you must set the Windows version to Windows Vista or later in winecfg or the installer will only show you an error message. $ sha1sum python-3.5.2.exe 3873deb137833a724be8932e3ce659f93741c20b python-3.5.2.exe -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 11

[Bug 42137] New: DirectInput needs to join both Xbox shoulder triggers into a single axis (aka half-axis problem)
by wine-bugs＠winehq.org 22 Oct '21

22 Oct '21

https://bugs.winehq.org/show_bug.cgi?id=42137 Bug ID: 42137 Summary: DirectInput needs to join both Xbox shoulder triggers into a single axis (aka half-axis problem) Product: Wine Version: 1.6.1 Hardware: x86 OS: Linux Status: NEW Keywords: hardware Severity: normal Priority: P2 Component: directx-dinput Assignee: wine-bugs(a)winehq.org Reporter: 00cpxxx(a)gmail.com CC: aric(a)codeweavers.com Distribution: --- When MS introduced the Xbox controller into dinput it had the idea of joining both Xbox controller shoulder triggers into a single axis. So the left trigger ranges to the negative side while the right trigger to the positive side of the same axis. Wine currently exposes the triggers are separate axes Z and rZ, this affects some games negatively because the not-pressed default values for the triggers is the lowest possible, for example if the axis ranges from -100 to +100 Wine exposes -100 to the application. The effect is that the application thinks the axis is always pressed and weird things happen, eg auto selecting Z/rZ as every button when configuring a joystick or wrongly selecting Z/rZ as rX/rY making FPS players always look up or down. I don't know if this happens only for Xbox controllers but I believe so. I'll have the chance to test with a real PS3 controller soon. If that is MS only, we need to find a way to distinguish the joysticks (VID/PID?) and merge the axes to mimic MS behavior. At the same time and in opposite direction the XInput API does not employ this hack, since XInput was made for Xbox only controllers it will properly report the values for the axes separately. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 15

[Bug 36796] New: Mozilla Firefox 13.0 crashes on startup if run in Windows Vista+ mode (D3D10CreateEffectFromMemory needs more complete Direct3D 10 DXBC parser)
by wine-bugs＠winehq.org 22 Oct '21

22 Oct '21

https://bugs.winehq.org/show_bug.cgi?id=36796 Bug ID: 36796 Summary: Mozilla Firefox 13.0 crashes on startup if run in Windows Vista+ mode (D3D10CreateEffectFromMemory needs more complete Direct3D 10 DXBC parser) Product: Wine Version: 1.7.20 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3dx10 Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Hello folks, Henri suggested that Mozilla Firefox in Vista+ mode might be a good candidate to help implementing missing/incomplete DX10/D2D API (https://bugs.winehq.org/show_bug.cgi?id=30966#c5) Running the browser results in crash: --- snip --- $ pwd /home/focht/.wine/drive_c/Program Files/Mozilla Firefox $ wine ./firefox.exe ... fixme:win:EnumDisplayDevicesW ((null),0,0x33c030,0x00000000), stub! fixme:d3d10:D3D10CreateDevice1 Ignoring feature level D3D10_FEATURE_LEVEL_10_0. fixme:dxgi:dxgi_device_init Ignoring adapter type. fixme:win:EnumDisplayDevicesW ((null),0,0x33c030,0x00000000), stub! fixme:d3d10:D3D10CreateDevice1 Ignoring feature level D3D10_FEATURE_LEVEL_10_1. fixme:dxgi:dxgi_device_init Ignoring adapter type. fixme:d2d:d2d_factory_init Ignoring factory type and options. fixme:d3d10:D3D10CreateEffectFromMemory data 0x15d07b0, data_size 4833, flags 0, device 0x143cb0, effect_pool (nil), effect 0x428b710 stub! fixme:d3d10:skip_dword_unknown Skipping 4 unknown DWORDs (DXBC header): fixme:d3d10:skip_dword_unknown 0x5af68935 fixme:d3d10:skip_dword_unknown 0x3e88ff30 fixme:d3d10:skip_dword_unknown 0x96a39662 fixme:d3d10:skip_dword_unknown 0x35cbba93 fixme:d3d10:skip_dword_unknown Skipping 1 unknown DWORDs (DXBC header): fixme:d3d10:skip_dword_unknown 0x00000001 fixme:d3d10:parse_fx10 Unknown 0: 0 fixme:d3d10:parse_fx10 Unknown 1: 0 fixme:d3d10:skip_dword_unknown Skipping 1 unknown DWORDs (local buffer): fixme:d3d10:skip_dword_unknown 0xffffffff fixme:d3d10:skip_dword_unknown Skipping 1 unknown DWORDs (variable): fixme:d3d10:skip_dword_unknown 0x00000000 fixme:d3d10:skip_dword_unknown Skipping 1 unknown DWORDs (variable): fixme:d3d10:skip_dword_unknown 0x00000000 fixme:d3d10:skip_dword_unknown Skipping 1 unknown DWORDs (variable): fixme:d3d10:skip_dword_unknown 0x00000000 fixme:d3d10:skip_dword_unknown Skipping 1 unknown DWORDs (local variable): fixme:d3d10:skip_dword_unknown 0xffffffff fixme:d3d10:skip_dword_unknown Skipping 1 unknown DWORDs (local variable): fixme:d3d10:skip_dword_unknown 0xffffffff ... fixme:d3d10:parse_fx10_state_group Failed to find property info for property 0x37. err:d3d10:parse_fx10_local_variable Failed to read property list. err:d3d10:D3D10CreateEffectFromMemory Failed to parse effect fixme:dbghelp:elf_search_auxv can't find symbol in module err:seh:raise_exception Exception frame is not in stack limits => unable to dispatch exception. --- snip --- $ sha1sum Firefox\ Setup\ 13.0.exe 9002a5ae41ef54edf378506ae80c934b7e8df7dc Firefox Setup 13.0.exe $ du -sh Firefox\ Setup\ 13.0.exe 16M Firefox Setup 13.0.exe $ wine --version wine-1.7.20-122-gd2d62cf Regards -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 12

[Bug 51385] New: DTS Encoder Suite won't start in Wine 6.0.1
by WineHQ Bugzilla 22 Oct '21

22 Oct '21

https://bugs.winehq.org/show_bug.cgi?id=51385 Bug ID: 51385 Summary: DTS Encoder Suite won't start in Wine 6.0.1 Product: Wine Version: 6.0.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: shagooserver(a)gmail.com Distribution: --- Upon running DTS encoder the following message is returned: Unable to access jarfile DTSEncoder.jar Some further investigation involving starting other pieces of the program first produced this message when attempting to start DTSEncoder.jar: Error: 3 - socket server failed to start Jobqueue exit runCtrlThread I am using the Timebomb fix (where the program just fails after 1/1/21 or thereabouts) using a new/modified DtsJobQueue.exe file and has been working perfectly all this year under wine version 5 stable. I am using Java jre-6u45-windows-i586.exe Host system is Kubuntu 21.04. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 51707] New: Rise of the Tomb Raider stops the process before entering the main menu
by WineHQ Bugzilla 22 Oct '21

22 Oct '21

https://bugs.winehq.org/show_bug.cgi?id=51707 Bug ID: 51707 Summary: Rise of the Tomb Raider stops the process before entering the main menu Product: Wine Version: 6.10 Hardware: x86-64 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com CC: hverbeet(a)gmail.com Regression SHA1: 126f0e6ed3119fdeb71b87ac7e3ab22a589dbd0e Distribution: --- Reverting helps. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 51846] New: Standard library call fopen(..., "wx") not recognized - causes destruction of data
by WineHQ Bugzilla 22 Oct '21

22 Oct '21

https://bugs.winehq.org/show_bug.cgi?id=51846 Bug ID: 51846 Summary: Standard library call fopen(..., "wx") not recognized - causes destruction of data Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcrt Assignee: wine-bugs(a)winehq.org Reporter: ted(a)lyncon.se Distribution: --- Created attachment 70740 --> https://bugs.winehq.org/attachment.cgi?id=70740 open_excl.cpp wine-6.16 (Staging) When running a program that uses the standard (since C11 and C++17) fopen() mode "wx" to guarantee that opening a file for writing fails if it already exists, I noticed that wine can't handle that mode. Instead, it prints "0104:err:msvcrt:msvcrt_get_flags incorrect mode flag: x" and successfully opens the file - even if it already exists - which destroys the content of the existing file. I'm attaching the source code to a small C++17 program that works as expected when compiled with Visual Studio 2019 (/std:c++17) and running it on Windows 10 natively. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 21

[Bug 51902] New: Project CARS 2 keyboard keys aren't responsive
by WineHQ Bugzilla 22 Oct '21

22 Oct '21

https://bugs.winehq.org/show_bug.cgi?id=51902 Bug ID: 51902 Summary: Project CARS 2 keyboard keys aren't responsive Product: Wine Version: 6.19 Hardware: x86-64 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: directx-dinput Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com CC: rbernon(a)codeweavers.com Regression SHA1: 71ecc179aab7ad103e06b52ea76ae1f1e25b3d3b Distribution: --- Reverting helps. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 41317] New: WOLF RPG Editor (Game.exe): Arrow keys don' t work properly when gamepad is connected
by wine-bugs＠winehq.org 22 Oct '21

22 Oct '21

https://bugs.winehq.org/show_bug.cgi?id=41317 Bug ID: 41317 Summary: WOLF RPG Editor (Game.exe): Arrow keys don't work properly when gamepad is connected Product: Wine Version: 1.9.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-dinput Assignee: wine-bugs(a)winehq.org Reporter: kakurasan(a)gmail.com Regression SHA1: c126b21a34be008534e4fbd2a0f8bb8ea08c6c2b Distribution: --- Created attachment 55651 --> https://bugs.winehq.org/attachment.cgi?id=55651 Input test program which uses DX Library (source) When gamepad is connected, the cursor or character moves automatically and arrow keys doesn't work properly. Workaround: Disable all gamepads using joy.cpl, or use native dinput.dll Note: WOLF RPG Editor uses a DirectX wrapper library called "DX Library" (open source). Downloads (Japanese): * WOLF RPG Editor: http://www.silversecond.com/WolfRPGEditor/Download.html * DX Library: http://dxlib.o.oo7.jp/ ----- Result of regression testing ----- c126b21a34be008534e4fbd2a0f8bb8ea08c6c2b is the first bad commit commit c126b21a34be008534e4fbd2a0f8bb8ea08c6c2b Author: Andrew Nguyen <anguyen(a)codeweavers.com> Date: Tue Jul 5 07:19:17 2011 -0500 dinput: Extract the DirectInput instance creation and initialization in DirectInputCreateEx to separate functions. :040000 040000 f904caf8d290195557d1c2733d12288d8b4f9cf4 02e3e0e5a1ad1ee2fbb02e91bb09f093766c0e0e M dlls -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 23

[Bug 51797] New: Input lag with controller in Wine 6.18
by WineHQ Bugzilla 22 Oct '21

22 Oct '21

https://bugs.winehq.org/show_bug.cgi?id=51797 Bug ID: 51797 Summary: Input lag with controller in Wine 6.18 Product: Wine Version: 6.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lemonzest(a)gmail.com Distribution: --- Hiya I am noticing quiet noticeable controller input lag with Wine 6.18 I have tried many games (Foregone/Dead Cells/Shantae Half Genie Hero/Mighty Switch Force Collection/Tales of Zestiria) and they all behave the same. Analog controls are responsive but face buttons and directional pad are lagged or missed, I'm talking like 1-2 seconds! I have tried wine control joy.cpl and the tests are fine, analog fast and buttons/dpad are instant, it is only in games where I am experiencing this lagged input. I am using a PDP Afterglow Wired Xbox One Controller and prior to this was fast and responsive (tho was a hiccup with Wine 6.17) Thank you for your help -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 7