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

[Bug 52198] New: MotoGP 2: Controller menu doesn't open when button for controller menu is pressed
by WineHQ Bugzilla 26 Dec '21

26 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=52198 Bug ID: 52198 Summary: MotoGP 2: Controller menu doesn't open when button for controller menu is pressed Product: Wine Version: 6.23 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-dinput Assignee: wine-bugs(a)winehq.org Reporter: tobias.boesch(a)googlemail.com Distribution: Debian Created attachment 71251 --> https://bugs.winehq.org/attachment.cgi?id=71251 Logs of starting MotoGP 2 demo and klicking the controller configuration button Hello Wine dev team, I tried launching MotoGP 2 and found out that - after the game is installed and - started via launcher.exe and - the launcher appears - klicking the "Configure controllers" button "doesn't work" which means there is no window opening. I expect that a window opens where one can associate controller buttons to game functions. This works on a recent Windows 10. I was able to log messages from wine and added them as attachment. Note: Though the test for this bug report was made with the wine development version, I also tested it with my Debian default version 5.09 and with that version that menu opens. The demo version can be found at: https://www.fileplanet.com/archive/p-18296/MotoGP-2-PC-Demo Some people made this game work in older wine versions by overriding dinput8.dll. See: https://appdb.winehq.org/objectManager.php?sClass=version&iId=5418&iTesting… I tried that in another test and was not successful. I run Debian 11. -- 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 16

[Bug 52260] New: Gothic 3: flickering, low-res textures with built-in msvcrt.dll
by WineHQ Bugzilla 26 Dec '21

26 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=52260 Bug ID: 52260 Summary: Gothic 3: flickering, low-res textures with built-in msvcrt.dll Product: Wine Version: 6.15 Hardware: x86-64 URL: https://archive.org/download/DemosGothic3/Demos%20-%20 Gothic%203.exe OS: Linux Status: NEW Keywords: download, regression Severity: normal Priority: P2 Component: msvcrt Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: piotr.caban(a)gmail.com Regression SHA1: f1ef14dc177b23c908e4dd2d47846cb673e3feac Distribution: ArchLinux In many places in the game Gothic 3 textures are flashing in and out and they look like low-resolution textures that are smudged. Most of the buildings have this glitch. The problem doesn't occur with native msvcrt.dll. The bug appeared in Wine 6.15. What made regression testing difficult was that the offending commit also caused several applications, including Gothic 3, to crash on start. Therefore I couldn't perform the regression test in the usual way. The last good commit where the game starts properly and the bug is *not* present: f53b2095f36f1753b9a50d4dcb2eeab6c8c796cd The next commit broke the game: f1ef14dc177b23c908e4dd2d47846cb673e3feac msvcrt: Introduce _setfp helper to access floating point status and control words. The breakage was fixed later by 62d2693701c1756264fdf975578cb7f6abd5c1b1 msvcrt: Fix x87 FPU status register assignment detection. After git checkout f1ef14dc177b23c908e4dd2d47846cb673e3feac and the fix applied, the bug is present. Demos - Gothic 3.exe (1.1G) md5: 18a1a1b96bed7207944f185f160a689b (demo needs native d3dx9_29.dll) wine-7.0-rc2-41-gd03984709d8 -- 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 48032] New: Errors when installing games in Origin (regression)
by WineHQ Bugzilla 26 Dec '21

26 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=48032 Bug ID: 48032 Summary: Errors when installing games in Origin (regression) Product: Wine Version: 4.18 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sashok.olen(a)gmail.com Distribution: --- During game installations, Origin will almost always print "An unexpected error has occurred. Please try again in a few moments. Error: 327682:11" and not flag the game as successfully installed. Through bisect I've found that this is a regression which was caused by commit e4ca5dbec056c977bffce31bd7901aaec884f199 (server: Add new pipe servers to the end of the servers list). Reverting that commit against wine-4.3 also fixed the issue (can't revert it against 4.19 as git revert doesn't let me). I've made a log with +server debug channel. It was too big for bugzilla so I had to upload it to my Google Drive: https://drive.google.com/open?id=1doEVWo1qW1ppP_VemoCu8xhFkWXEsn0z (oh, and ignore errors about wine not finding some .exes - i disabled them myself for certain reasons). Let me know if anything else is needed. -- 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 20

[Bug 51159] New: test_NLSVersion() fails on Windows 10 >= 2004 in kernel32:locale
by WineHQ Bugzilla 26 Dec '21

26 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51159 Bug ID: 51159 Summary: test_NLSVersion() fails on Windows 10 >= 2004 in kernel32:locale Product: Wine Version: 6.8 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- test_NLSVersion() fails on Windows 10 >= 2004 in kernel32:locale: locale.c:6900: Test failed: IsValidNLSVersion succeeded This is the test where dwNLSVersion is decreased compared to its initial version: info.dwNLSVersion -= 0x200; ret = pIsValidNLSVersion( COMPARE_STRING, L"en-US", &info ); ok( !ret, "IsValidNLSVersion succeeded\n" ); Traces show that Windows 8.1 to Windows 10 1809 have NLSVersion=6020f, while Windows 10 >= 2004 has NLSVersion=60305. Maybe the test fails because the older Windows accept anything in the 602xx range and 60206 (60305+1-0x100) falls in that range? What was the point of that test? This test was introduced by the commit below: commit 84cca2baae23c6afa0c8070f5009fdcfa218e039 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Fri Mar 20 14:43:45 2020 +0100 kernelbase: Implement IsValidNLSVersion(). Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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 3

[Bug 52073] New: The builtin libxml2/libxslt libraries break msxml3:domdoc in wow64 mode
by WineHQ Bugzilla 26 Dec '21

26 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=52073 Bug ID: 52073 Summary: The builtin libxml2/libxslt libraries break msxml3:domdoc in wow64 mode Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: msxml3 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- The builtin libxml2 / libxslt libraries break msxml3:domdoc in wow64 mode. More specifically msxml3:domdoc started crashing on 2021-10-20: domdoc.c:7004: Test marked todo: expected refcount 2, got 1 Unhandled exception: page fault on read access to 0x00000000ffffffff in 64-bit code (0x00000000013682a8). [...] Backtrace: =>0 0x00000000013682a8 xmlXPathNodeCollectAndTest+0x28(ctxt=<is not available>, op=<is not available>, first=<is not available>, last=<is not available>, toBool=<is not available>) [Z:\home\winetest\winetest\src\libs\xml2\xpath.c:12028] in msxml3 (0x0000000001388348) 1 0x0000000001369d51 xmlXPathNodeCollectAndTest+0x1ad0(ctxt=<is not available>, op=<is not available>, first=<is not available>, last=<is not available>, toBool=<is not available>) [Z:\home\winetest\winetest\src\libs\xml2\xpath.c:13113] in msxml3 (0x0000000001388348) 2 0x000000000136a024 xmlXPathNodeCollectAndTest+0x1da3(ctxt=<is not available>, op=<is not available>, first=<is not available>, last=<is not available>, toBool=<is not available>) [Z:\home\winetest\winetest\src\libs\xml2\xpath.c:13361] in msxml3 (0x0000000001388348) 3 0x000000000136b559 xmlXPathRunEval+0xc8(ctxt=<is not available>, toBool=<is not available>) [Z:\home\winetest\winetest\src\libs\xml2\xpath.c:13954] in msxml3 (0x0000000001388348) 4 0x000000000136b775 xmlXPathCompiledEvalInternal+0xc4(comp=<is not available>, ctxt=<is not available>, resObjPtr=<is not available>, toBool=<is not available>) [Z:\home\winetest\winetest\src\libs\xml2\xpath.c:14337] in msxml3 (0x0000000001388348) 5 0x000000000136bb3a xmlXPathCompiledEval+0x19(comp=<is not available>, ctx=<is not available>) [Z:\home\winetest\winetest\src\libs\xml2\xpath.c:14383] in msxml3 (0x0000000000fae760) 6 0x0000000001298edc xsltProcessOneNode+0x18b(ctxt=<is not available>, contextNode=<is not available>, withParams=<is not available>) [Z:\home\winetest\winetest\src\libs\xslt\libxslt\transform.c:385] in msxml3 (0x0000000000fae760) 7 0x0000000001296517 xsltCopyText+0x706(ctxt=<is not available>, target=<is not available>, cur=<is not available>, interned=<is not available>) [Z:\home\winetest\winetest\src\libs\xslt\libxslt\transform.c:2798] in msxml3 (0x0000000000fadc90) 8 0x0000000001298638 xsltLocalVariablePush+0x267(ctxt=<is not available>, variable=<is not available>, level=<is not available>) [Z:\home\winetest\winetest\src\libs\xslt\libxslt\transform.c:2388] in msxml3 (0x0000000000fa3c70) 9 0x0000000001298da2 xsltProcessOneNode+0x51(ctxt=0000000000FC2DC0, contextNode=0000000000FAE760, withParams=0000000000000000) [Z:\home\winetest\winetest\src\libs\xslt\libxslt\transform.c:3145] in msxml3 (0x0000000000000000) 10 0x000000000129b28f xsltApplyStylesheetInternal+0x3ce(style=0000000000FA2030, doc=0000000000FAE760, params=<is not available>, output=<is not available>, profile=<is not available>, userCtxt=<is not available>) [Z:\home\winetest\winetest\src\libs\xslt\libxslt\transform.c:6089] in msxml3 (0x0000000000000000) 11 0x000000000129b95e xsltApplyStylesheet+0x1d(style=<is not available>, doc=<is not available>, params=<is not available>) [Z:\home\winetest\winetest\src\libs\xslt\libxslt\transform.c:6285] in msxml3 (0x00000000006bf978) 12 0x000000000125c2a7 node_transform_node_params+0xb6(This=0000000000043960, stylesheet=<is not available>, p=<is not available>, stream=0000000000000000, params=0000000000000000) [Z:\home\winetest\winetest\src\dlls\msxml3\node.c:1518] in msxml3 (0x00000000006bf978) 13 0x000000000125c845 unknode_transformNode+0x34(iface=<is not available>, domNode=<is not available>, p=<is not available>) [Z:\home\winetest\winetest\src\dlls\msxml3\node.c:1541] in msxml3 (0x00000000000384a8) 14 0x000000000123085a domdoc_transformNode+0x29(iface=<is not available>, node=0000000000045540, p=00000000006BF978) [Z:\home\winetest\winetest\src\dlls\msxml3\domdoc.c:1479] in msxml3 (0x00000000000384a8) 15 0x000000000040c180 in msxml3_test (+0xc17f) (0x00000000000384a8) [...] https://test.winehq.org/data/patterns.html#msxml3:domdoc A bisect shows that the crash started happening with the commit below: commit bca1b7f2faeb0798f4af420c15ff5a1b1f7b40af Author: Alexandre Julliard <julliard(a)winehq.org> Date: Wed Oct 20 11:39:06 2021 +0200 mxsml3: Use the bundled libxml2 and libxslt and build with msvcrt. Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> The previous two commits are imports of the libxslt and libxml2 code respectively and don't compile. And msxml3:domdoc does not crash with the previous commit (9a335d89d0cc). -- 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 52222] New: WINEDLLOVERRIDES="DINPUT8.dll=n,b" no longer works since 4f1095a, worked in V6.23.
by WineHQ Bugzilla 26 Dec '21

26 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=52222 Bug ID: 52222 Summary: WINEDLLOVERRIDES="DINPUT8.dll=n,b" no longer works since 4f1095a, worked in V6.23. Product: Wine Version: 7.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winmm&mci Assignee: wine-bugs(a)winehq.org Reporter: billfleming11(a)gmail.com Distribution: --- Zebediah pointed out where this new bug was and I confirmed the regression with a minor code modification. See his comments here for the program I first saw the regression against. https://bugs.winehq.org/show_bug.cgi?id=51409#c7 In Wine 3.X, 4.X, 5.X, 6.X we have been able to supply modified DLLs (for example that some games require to load a translation or a mod to fix bugs, etc) in the game's directory and override the built-in DLL to load the modification hook into the application. From 4f1095a on-wards dinput8 became an IMPORT requirement of winmm makefile leading to the following error in wine, before it even really attempts to load the application. LdrInitializeThunk "WINMM.dll" failed to initialize, aborting I can modify wine 7.0-rc1 to allow the dll to load again, making the game playable other than any lingering video playback issues it has. In dlls/winmm/Makefile.in I modified the IMPORTS line to remove dinput8. In dlls/winmm/joystick.c I commented out the contents of the void joystick_load( HINSTANCE instance ) function. (lines 157 to 159 as of 7.0-rc1). Then after rebuilding wine the application will launch again using WINEDLLOVERRIDES="DINPUT8.dll=n,b" Note that this regression will affect a large number of video games as it is almost universal to "hook" into a game using DINPUT8.dll specifically, as apposed to other possible DLLs. If anyone really wants to look at a log file I put one here in the old report. https://bugs.winehq.org/attachment.cgi?id=71302 Note that at least in this one game my xbox 1 controller still works with xow after removing those lines, but someone who knows what they are doing should propose a new patch relating to joysticks. -- 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 14

[Bug 48776] New: GoToMeeting Opener crashes
by WineHQ Bugzilla 26 Dec '21

26 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=48776 Bug ID: 48776 Summary: GoToMeeting Opener crashes Product: Wine Version: 5.4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wininet Assignee: wine-bugs(a)winehq.org Reporter: bernhardu(a)mailbox.org Distribution: --- Tried to get a goto meeting running just with an older Firefox and Wine. Unfortunately the "GoToMeeting Opener.exe" crashes short after start, when showing around 10% progress. I could follow the crash to an allocation of 0x100000 bytes, to which some data get asynchronously downloaded, written to a file, and then freed. But after that, below a INTERNET_WorkerThreadFunc, a memcpy tries to access the previously freed memory. Further looking might lead to a SetEvent that get triggered by the INTERNET_STATUS_RECEIVING_RESPONSE callback, but I am not sure if this is related or supposed the way it runs now. A windows Firefox offers for following link a download: https://global.gotomeeting.com/join/100000000 (meeting id changed - the download is the same except 176 bytes, but shows the same issue.) -- 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 51862] New: dlls/ntdll/unix/system.c: In function ‘init_cpu_info’
by WineHQ Bugzilla 26 Dec '21

26 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51862 Bug ID: 51862 Summary: dlls/ntdll/unix/system.c: In function ‘init_cpu_info’ Product: Wine Version: 6.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: version2013(a)protonmail.com Distribution: --- Created attachment 70774 --> https://bugs.winehq.org/attachment.cgi?id=70774 log.txt in distro: # uname --kernel-release 3.14.56 # gcc --version 4.8.4 # ldd --version 2.19 config line: configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-x --libdir=/usr/lib32 CFLAGS="-O2 -march=i686 -mtune=i686" Compiling wine-6.18 and wine-6.19, fails with: /dlls/ntdll/unix/system.c: In function ‘init_cpu_info’: /dlls/ntdll/unix/system.c:250:5: error: inconsistent operand constraints in an ‘asm’ -- 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 20

[Bug 52180] New: Significant performance regression in The Sims 2
by WineHQ Bugzilla 26 Dec '21

26 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=52180 Bug ID: 52180 Summary: Significant performance regression in The Sims 2 Product: Wine Version: 6.23 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: sashok.olen(a)gmail.com CC: huw(a)codeweavers.com, jacek(a)codeweavers.com Regression SHA1: c4b258eff75d54fdc0eb9b1843db5f77318f836c Distribution: --- Hi, between Wine 6.22 and Wine 6.23, The Sims 2 suffered a significant performance decrease. Through bisect, I've discovered multiple changes that contributed to this. Here is the progress of performance degradation between 6.22 and 6.23 version, tested on a machine with AMD Ryzen 3800X by loading into the "Pleasant" family in the "Pleasantville" neighborhood and focusing on one of the household members and zooming the camera out all the way out during clear weather. The graphical backend used during tests was DXVK due to Wined3d not working with the game (only wine-staging does, and even that has a lot of graphical issues and is a lot slower). And while Sims 2 doesn't have a built-in benchmark tool, I've found that the value differences have been quite consistent and reliably reproduced. wine-6.22 - 47-44 fps commit d7133c97d91a0dbc746a4c9711831f45704c8b43 - 9-1 fps commit 318673405c6296342ef49177de26440f69a4b0be - 44-39 fps commit c4b258eff75d54fdc0eb9b1843db5f77318f836c - 36-30 fps wine-6.23 - 36-30 fps I was not sure which commit to specify as the offender so I specified c4b258eff75d54fdc0eb9b1843db5f77318f836c as one. It should be noted that the game suffered a similar performance regression in the past (see https://bugs.winehq.org/show_bug.cgi?id=51047) which might be related or give a clue as to what the issue is. And while it's not really relevant, it should be noted that the game is generally very CPU-bound and runs quite a lot slower with wine+DXVK than Windows10+DXVK, roughly 2-3 times slower. In case it might be useful, here's an apitrace of the game: https://drive.google.com/file/d/158QpcQ98n2h2xCSkpvPFpiwqYkydIRqk/view?usp=… -- 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 52214] New: Elite Dangerous - Network error, only with WLAN adapter / Not just since 7.0rc1 / Launcher not affected / Ethernet works
by WineHQ Bugzilla 26 Dec '21

26 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=52214 Bug ID: 52214 Summary: Elite Dangerous - Network error, only with WLAN adapter / Not just since 7.0rc1 / Launcher not affected / Ethernet works Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: supreme-ntm(a)web.de Distribution: --- Created attachment 71277 --> https://bugs.winehq.org/attachment.cgi?id=71277 WINEDEBUG=+seh,+winhttp,+winsock,+wininet The ED Launcher, which also requires an internet connection, works ok with my wlan adapter. But when pressing 'Launch' to start ED, I receive an error message from the game stating, that the network could not be initialised. The error does not occur when I use an ethernet connection! This happens not just since the 7.0rc1 version. This bug appeared sometime in the latest months, but can't remember the exact wine version... maybe it was 6.18. Tested wine-staging and wine-devel (7.0rc1) - both are affected. In wine-stable (6.0.2) the problem does not exist - wlan still works there. Attached you find the Winedebug log (flags: +seh,+winhttp,+winsock,+wininet) This bug happens after line 41368 (after pressing the 'Launch' button) - the lines before stem from the (working) launcher. -- 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 22