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

[Bug 41135] New: No Man's Sky: Game does crash/hang on starting
by wine-bugs＠winehq.org 28 Mar '21

28 Mar '21

https://bugs.winehq.org/show_bug.cgi?id=41135 Bug ID: 41135 Summary: No Man's Sky: Game does crash/hang on starting Product: Wine Version: 1.9.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sworddragon2(a)aol.com Distribution: --- Created attachment 55339 --> https://bugs.winehq.org/attachment.cgi?id=55339 Terminal output (Windows 7) After solving the other issue where an upgrade of libcups2 caused Wine to heavily break I'm encountering now the next issues on starting No Man's Sky. With a clean wine profile and the Windows version set to Windows 7 (as the system requirement for this game is Windows 7-10) on starting the game nothing happens and the game has a CPU usage of ~55% on one core and the wineserver has a CPU usage of ~60% on one core. If I'm setting the Windows version to Windows XP the game does start but crashes after the first screen is shown. For both cases is the terminal output in the attachments. -- 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 27

[Bug 50649] New: winecfg crashes with desktop emulation
by WineHQ Bugzilla 27 Mar '21

27 Mar '21

https://bugs.winehq.org/show_bug.cgi?id=50649 Bug ID: 50649 Summary: winecfg crashes with desktop emulation Product: Wine Version: 6.0-rc6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: gmascellani(a)codeweavers.com Distribution: --- STEPS TO REPRODUCE: * Start with a new prefix * Launch winecfg and enable desktop emulation (leave the standard resolution 800x600) * Launch winecfg again; the desktop window appears and disappears after a split second; winecfg window never appears This happens with both i386 and amd64 builds (did not try a WoW64 build). I am using an up-to-date Debian unstable machine, on a laptop with an Intel iGPU and an NVIDIA Quadro P2000 dGPU. Disabling NVIDIA Vulkan drivers doesn't change anything. The crash happens inside get_gpu_properties_from_vulkan, in dlls/winex11.drv/xrandr.c. This function creates a Vulkan instance, enumerates Vulkan devices and their properties and then destroys the instance. This happens a few times during a single "wine winecfg" execution. In one of these executions the driver segfaults in vkDestroyInstance. The other calls to vkDestroyInstance are fine. If the call to vkDestroyInstance in X11DRV_vkDestroyInstance is commented out, then the crash doesn't happen any more and winecfg works correctly. I can't see any Vulkan usage problem and Vulkan validator doesn't detect anything except a couple of issues that are easy to solve and do not fix the problem. The specific failing instruction is in libvulkan_lvp.so. Addr2line says it is in function util_queue_destroy in file src/util/u_queue.c:97 (in the mesa package), but that line does not correspond to that function in the source code, so addr2line is probably confused and I don't know if anything it says can be believed. Also, this is just the inner frame: I couldn't get a backtrace from the vkDestroyInstance call to the segfaulting instruction. I can get a core dump, but gdb cannot recognize the stack in it, so I get no useful information (not easily at least: I could manually inspect the stack and reconstruct the backtrace, but that's tedious and I haven't tried yet). -- 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

[Bug 25528] New: HLSL shader not translated correctly (uniform variables)
by wine-bugs＠winehq.org 27 Mar '21

27 Mar '21

http://bugs.winehq.org/show_bug.cgi?id=25528 Summary: HLSL shader not translated correctly (uniform variables) Product: Wine Version: 1.3.5 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: knight666+wine(a)gmail.com Created an attachment (id=32501) --> (http://bugs.winehq.org/attachment.cgi?id=32501) Program run in a normal way I was trying to run the game "Sexy Beach Zero" (hmmyes) and it runs great. But when you load any of the 3D scenes, the body model isn't bound correctly to her and is stationary at (0, 0, 0) in the scene. I checked the log and found a lot of these: err:d3d_shader:set_glsl_shader_program >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from Find glsl program uniform locations @ glsl_shader.c / 4435 err:d3d_shader:set_glsl_shader_program >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glUseProgramObjectARB(programId) @ glsl_shader.c / 4449 err:d3d_shader:hardcode_local_constants >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from Hardcoding local constants @ glsl_shader.c / 3955 err:d3d_shader:shader_glsl_select >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glUseProgramObjectARB @ glsl_shader.c / 4618 trace:d3d_constants:shader_glsl_load_constantsI Loading local constants 0: 2, 0, 0, 0 err:d3d_shader:shader_glsl_load_constantsI >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glUniform4ivARB @ glsl_shader.c / 598 err:d3d_shader:shader_glsl_load_constants >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glUniform4fvARB @ glsl_shader.c / 769 (After this it repeats the last 4 lines) Perfectly willing to chip my teeth on this bug, I downloaded the latest Wine git to check the source. I ran the game again with the following command: WINEDEBUG=trace+d3d_constants wine "Sexy Beach Zero English.exe" &> ~/sbz2.log The log now returns this: fixme:d3d_shader:print_glsl_info_log Error received from GLSL shader #10: fixme:d3d_shader:print_glsl_info_log Vertex info fixme:d3d_shader:print_glsl_info_log ----------- fixme:d3d_shader:print_glsl_info_log 0(35) : warning C1068: array index out of bounds Repeat the array index out of bounds warning plenty of times. Going deeper, I ran the game like this: WINEDEBUG=trace+d3d_shader wine "Sexy Beach Zero English.exe" &> ~/sbz.log Part of the offending HLSL shader: def *c822* = 1.000000, 3.000000, 0.000000, 0.000000 def c823 = 0.500000, 0.000000, 0.000000, 0.000000 def c824 = -1.000000, -2.000000, -3.000000, -4.000000 defi i0 = 5, 0, 0, 0 frc r0, v2 slt r1, -r0, r0 add r2, -r0, v2 slt r0, v2, -v2 mad r0, r0, r1, r2 mul r0, r0, *c822*.y Emphasis marked with *'s. uniform vec4 *VC[256]*; // snip void main() { R0.xyzw = (fract(attrib2.xyzw)); R1.xyzw = (vec4(lessThan(-R0.xyzw, R0.xyzw))); R2.xyzw = (-R0.xyzw + attrib2.xyzw); R0.xyzw = (vec4(lessThan(attrib2.xyzw, -attrib2.xyzw))); R0.xyzw = ((R0.xyzw * R1.xyzw) + R2.xyzw); R0.xyzw = (R0.xyzw * *VC[822]*.yyyy); This is where the "array index out of bounds" warning comes from. The shader translator should have converted "c822" to a uniform, but instead put it in an array. I got hopelessly lost in the Wine source, I couldn't find the error myself, unfortunately. :( Hopefully this helps someone more knowledgeable with these things! -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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 24

[Bug 42145] New: Guild Wars 2 crashes on some configurations
by wine-bugs＠winehq.org 27 Mar '21

27 Mar '21

https://bugs.winehq.org/show_bug.cgi?id=42145 Bug ID: 42145 Summary: Guild Wars 2 crashes on some configurations Product: Wine Version: 2.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: me(a)aaronopfer.com Distribution: --- Created attachment 56713 --> https://bugs.winehq.org/attachment.cgi?id=56713 GW2-generated crash log Guild Wars 2 crashes on my laptop psuedorandomly while playing the game. I managed to create a reproduceable version of the crash: all I have to do is toggle the visibility of my helmet slot in my Hero's Equipment panel (a feature designed for those who don't want ugly helmets covering their character's faces) and the game will reliably crash. I am using 64bit wine. I reproduced the crash initially in 2.0.0-rc3-staging, then in 2.0.0-rc3, and then again in 1.7.35. I haven't tested any other versions. The crash does NOT occur on my desktop despite similar wine versions and configurations. The main difference between the laptop and the desktop is that the desktop uses the proprietary nvidia blob on a GTX 780, and the laptop uses integrated intel HD 5500 graphics. The laptop and desktop are running the debian 4.8.0 kernel. As an aside, another laptop I have running debian is using a nvidia mobile GPU (don't remember the model) via bumblebee and it also has no problems with crashing in GW2. I have some modest debugging skills: poking around in a debugger shows that the crash occurs in what appears to be blitting code (the Gw2-64.exe binary makes string references to "ImgBlt.cpp" in the area). The fault instruction is a rep movsb. During normal operation the rep movsb's operands are in low memory ranges (mask 0xFFFFFFFF), but when it crashes one operand is (0x0222000000000000) which is not valid memory and causes a crash. I do not have a Windows machine so I do not know if Windows has the same crash; I presume not. I have attached the Arenanet.log file which contains some information about what went wrong. It may contain multiple crashes; I'm not very familiar with these GW2-specific crashlogs so I'm not sure. These are made by GW2's built-in crash logger. If anyone wants another crash log format you'll have to tell me how to disable GW2's built-in one. If anyone wants me to do any specific debug actions or logs I'll be happy to try them. -- 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 3

[Bug 33375] New: Cannot test dlls with dashes in their name
by wine-bugs＠winehq.org 26 Mar '21

26 Mar '21

http://bugs.winehq.org/show_bug.cgi?id=33375 Bug #: 33375 Summary: Cannot test dlls with dashes in their name Product: Wine Version: 1.5.19 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: build-env AssignedTo: wine-bugs(a)winehq.org ReportedBy: fgouget(a)codeweavers.com Classification: Unclassified Created attachment 44165 --> http://bugs.winehq.org/attachment.cgi?id=44165 Patch to reproduce this bug No conformance test can be written for dlls that have a dash in their name. These will first run into a build error: echo "api-ms-win-security-base-l1-1-0_test.exe TESTRES \"api-ms-win-security-base-l1-1-0_test-stripped.exe.so\"" | LD_LIBRARY_PATH="../../../libs/wine:$LD_LIBRARY_PATH" ../../../tools/wrc/wrc --nostdinc --po-dir=../../../po -m32 -I. -I. -I../../../include -I../../../include -DWINE_STRICT_PROTOTYPES -DWINE_NO_NAMELESS_EXTENSION -DWIDL_C_INLINE_WRAPPERS -o ../../../programs/winetest/api-ms-win-security-base-l1-1-0_test.res :1:5: Error: syntax error What surprises me is that the dot on the 'TESTRES' left-hand causes no problem while the dashes do. I tried quoting that string but it did not help. The next problem is that if the TESTRES left-hand is modified to work around that issue, then winetest.exe will not be able to find the corresponding dll anymore and will thus skip the test. Filtering the list of tests to run based on the command line will likely be broken too. I'm attaching a patch to reproduce this issue. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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 6

[Bug 45567] New: League of Legends 8.12+ fails to start a game ( anticheat engine, validation of WoW64 syscall dispatcher)
by wine-bugs＠winehq.org 26 Mar '21

26 Mar '21

https://bugs.winehq.org/show_bug.cgi?id=45567 Bug ID: 45567 Summary: League of Legends 8.12+ fails to start a game (anticheat engine, validation of WoW64 syscall dispatcher) Product: Wine Version: 3.13 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com Distribution: --- Diagnosed by Andrew Wesie; partially split off from bug 45327. The game inspects the %cs register to determine if it is running under WoW64. Since Linux 32-bit code segment is the same as the WoW64 32-bit code segment, 0x23, the anti-cheat will expect to be in a WoW64 environment regardless of whether the prefix is 32- or 64-bit. Consequently the game will try to use the Wow64Transition export if it is available, or otherwise request the module name of the address contained at the WOW32Reserved TEB field (i.e. %fs:0xc0), and verifies that the latter matches wow64cpu.dll. This can be solved either by moving the syscall dispatcher to wow64cpu.dll, or by implementing Wow64Transition. -- 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 8

[Bug 37983] New: Jedi Knight: Dark Forces II (GOG.com version) - music doesn't work
by wine-bugs＠winehq.org 26 Mar '21

26 Mar '21

https://bugs.winehq.org/show_bug.cgi?id=37983 Bug ID: 37983 Summary: Jedi Knight: Dark Forces II (GOG.com version) - music doesn't work Product: Wine Version: 1.7.35 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rixa(a)cs.tut.fi Distribution: --- The game originally used to have background music on CD audio tracks. The recent GOG.com release includes those tracks in .ogg format, along with what seems to be some sort of a hack to play them through a custom winmm.dll in the game directory. The music does not play. For the included winmm.dll to do anything, an override of "winmm (native,builtin)" seems like a logical step. Indeed, it was reported on the GOG.com forums that this gets the music working on Crossover, and I used the trial version to verify that this is indeed the case. But if I do the same on Wine, the game doesn't start anymore. It just dies with: err:seh:raise_exception Exception frame is not in stack limits => unable to dispatch exception. I tried to trace it down to other overrides that crossover sets by default, but it would still work even if I removed them all. It would even keep working if I replaced the entire drive_c there with the one from my wineprefix where it doesn't work, so it probably does not have to do with any of the pre-installed software, nor an installation broken for whatever reason. Using wine on the prefix installed in crossover didn't work any better either. In addition to a clean unpatched wine 1.7.35 that I compiled myself, I tried multiple versions of wine from PlayOnLinux but none of them started the game with the override in place; each died with the same message. Without the override the game is still very playable, just has no background music. Xubuntu 14.10, nvidia 331.113. -- 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 29

[Bug 45032] New: WineTest does not run the vcomp tests
by wine-bugs＠winehq.org 26 Mar '21

26 Mar '21

https://bugs.winehq.org/show_bug.cgi?id=45032 Bug ID: 45032 Summary: WineTest does not run the vcomp tests Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: vcomp Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- So WineTest is not running the vcomp tests. What happens is this: * It parses the vcomp_test.exe filename and concludes that this tests the vcomp dll. * It does a LoadLibraryExA("vcomp.dll", NULL, LOAD_LIBRARY_AS_DATAFILE) which fails (as expected) and concludes that the dll is missing: vcomp=dll is missing * Since the dll is missing WineTest skips the vcomp tests. According to Dan Kegel (see bug 31609) this is a manifest / activation context issue and he sent a patch for it [1]. However the patch was for the TestBot [2], not WineTest, and as far as I can tell it's not working. Furthermore WineTest already has activation context code that seems equivalent to Dan Kegel's patch. Note that not all VMs have vcomp.dll. Based on the current results the 32 bit dll is present on the TestBot's w2000pro, wxppro, w2003std, wvistau64*, w2008s64, w8, w864 VMs and the 64 bit one is present on wvistau64, w2008s64 and w864. Note that some online resources seem to imply that vcomp.dll is present in the Visual C++ 2005 redistributable (and VC++ 2005 was indeed installed on all the VMs that have vcomp.dll except w2008s64 (though maybe it was installed and it was not written down)). Some VMs seem to have other versions such as vcomp90.dll but not vcomp.dll. [1] https://bugs.winehq.org/show_bug.cgi?id=31609 https://www.winehq.org/pipermail/wine-patches/2012-September/117631.html [2] Paradoxically the TestBot has no problem running the vcomp tests now that they dynamically load the vcomp dll. That's because the TestBot makes no assumption based on the executable filename since one can upload test binaries that don't follow any naming scheme. So now that the test dynamically loads vcomp.dll the TestBot cannot check for it. -- 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 50721] New: IDA Pro 7.5: Lumina can't contact server, complains about Schannel security attributes
by WineHQ Bugzilla 26 Mar '21

26 Mar '21

https://bugs.winehq.org/show_bug.cgi?id=50721 Bug ID: 50721 Summary: IDA Pro 7.5: Lumina can't contact server, complains about Schannel security attributes Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: secur32 Assignee: wine-bugs(a)winehq.org Reporter: thotypous(a)gmail.com Distribution: --- Using Wine Staging, IDA Pro fails to contact the Lumina server when trying to do any operation that depends on it (e.g. Lumina menu -> Pull All Metadata). The IDA's output window shows "lumina: Schannel does not support the requested security attributes" By tracing secur32, it turns out that InitializeSecurityContextA is being called with fContextReq flags ISC_REQ_EXTENDED_ERROR and ISC_REQ_MANUAL_CRED_VALIDATION, which are not handled by Wine: 00f4:trace:secur32:InitializeSecurityContextA 0x3436e40 0x3436e50 (null) 0x0008c110 0 0 0x529b58 0 (nil) 0x529af8 0x3436e9c (nil) Now regarding each flag: 1. ISC_REQ_EXTENDED_ERROR: according to MSDN, this flag means "When errors occur, the remote party will be notified." However, modern TLS does not have any mechanism to notify the remote party about errors. Thus it seems unlikely that this flag causes any difference in behavior, at least when the remote party is not running Microsoft's TLS implementation. When researching about the flag, I found https://mskb.pkisolutions.com/kb/975858, which states Windows 7 used to ignore this flag, but since it caused issues with some applications, they changed schannel to return ISC_RET_EXTENDED_ERROR (via pfContextAttr) when the flag is set. The KB does not describe any other change deployed by the upgrade. This fact further supports the hypothesis that the flag does not change the behavior of the protocol. In short, up-to-date Windows 7 seems to just return ISC_RET_EXTENDED_ERROR when ISC_REQ_EXTENDED_ERROR is set, but otherwise ignores it. 2. ISC_REQ_MANUAL_CRED_VALIDATION: according to MSDN, this flag means "By default, Schannel validates the server certificate by calling the WinVerifyTrust function; however, if you have disabled this feature using the ISC_REQ_MANUAL_CRED_VALIDATION flag, you must validate the certificate provided by the server that is attempting to establish its identity." However, Wine currently does not carry automatic server certificate validation at all. The OSX implementation always calls "SSLSetEnableCertVerify(s->context, FALSE)" to disable it explicitly. The GnuTLS implementation never calls "gnutls_session_set_verify_cert", which would be required to enable server certificate validation. Strictly speaking, the current implementation of Schannel in Wine is insecure, but fixing it would require more extensive changes to the code and could cause regression bugs with other applications. Thus, I argue it should be dealt with by another bug entry and fixed by another patch. Therefore, the attached patch restricts itself to return ISC_RET_MANUAL_CRED_VALIDATION when ISC_REQ_MANUAL_CRED_VALIDATION is set, and to better document the current situation in the code. -- 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 5

[Bug 34906] New: [regres] Zoo Tycoon: closed on start in 1.7.6
by wine-bugs＠winehq.org 26 Mar '21

26 Mar '21

http://bugs.winehq.org/show_bug.cgi?id=34906 Bug #: 34906 Summary: [regres] Zoo Tycoon: closed on start in 1.7.6 Product: Wine Version: 1.7.6 Platform: x86 OS/Version: FreeBSD Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: fiziologus(a)gmail.com Classification: Unclassified closed without crash after begin music. in console: fixme:imm:ImmReleaseContext (0x2006a, 0x14f250): stub fixme:imm:ImmGetOpenStatus (0x14f250): semi-stub fixme:win:EnumDisplayDevicesW ((null),0,0x32ed38,0x00000000), stub! fixme:x11drv:X11DRV_desktop_SetCurrentMode Cannot change screen BPP from 32 to 16 err:quartz:GetClassMediaFile Media class not found err:quartz:GetClassMediaFile Media class not found err:quartz:GetClassMediaFile Media class not found err:quartz:GetClassMediaFile Media class not found fixme:d3d_surface:wined3d_surface_flip Ignoring flags 0x1. fixme:d3d:wined3d_device_set_render_target Surface 0x1ae5c0 doesn't have render target usage. err:ddraw:d3d_device_init Failed to set render target, hr 0x8876086c. result regression test (1.6-good, 1.7.6-bad) 3fb53e21fb2cccf249ed65a4641eac21422f6609 is the first bad commit commit 3fb53e21fb2cccf249ed65a4641eac21422f6609 Author: Henri Verbeet <hverbeet(a)codeweavers.com> Date: Tue Sep 17 09:22:37 2013 +0200 ddraw: Don't set render target / depth stencil usage on sysmem surfaces. Setting render target usage on a P8 surface for example would fail surface creation, while such surfaces can't be used for actual rendering anyway. Tests confirm that surface creation is supposed to succeed for P8 surfaces with both DDSCAPS_SYSTEMMEMORY and DDSCAPS_3DDEVICE set. :040000 040000 578fd201cb41a75b478b47c58c7a0a1a9b6a5209 38c723fb112690d758c0868debec68b3b61c4510 M dlls -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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 30