May 2022 - Wine-bugs - list.winehq.org

[Bug 19183] New: "make test" still fails on d3d9/tests/visual.c
by wine-bugs＠winehq.org 20 May '22

20 May '22

http://bugs.winehq.org/show_bug.cgi?id=19183 Summary: "make test" still fails on d3d9/tests/visual.c Product: Wine Version: 1.1.25 Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com (This is a sequel to bug 10221; perhaps we closed that one too soon.) Running i=0 while test $i -lt 10 do ../../../tools/runtest -q -P wine -M d3d9.dll -T ../../.. -p d3d9_test.exe.so visual.c > visual-$i.log 2>&1 i=`expr $i + 1` sleep 1 done cat visual-*.log | grep "Test failed" | sort | uniq -c | sort -n produces 1 visual.c:9439: Test failed: stretchrect: Pixel 160,360 has color 0x00ff00ff, expected 0x00ff0000 1 visual.c:9441: Test failed: stretchrect: Pixel 480,360 has color 0x00ff00ff, expected 0x0000ff00 1 visual.c:9443: Test failed: stretchrect: Pixel 480,120 has color 0x00ff00ff, expected 0x000000ff 1 visual.c:9445: Test failed: stretchrect: Pixel 160,120 has color 0x00ff00ff, expected 0x00000000 2 visual.c:8978: Test failed: Offscreen failed for D3DFMT_A32B32G32R32F: expected no color blending but received it anyway. 3 visual.c:6883: Test failed: SRCALPHA on texture returned color 00000000, expected 0x00bf4000 3 visual.c:6887: Test failed: DSTALPHA on texture returned color 00000000, expected 0x000000ff 3 visual.c:8978: Test failed: Offscreen failed for D3DFMT_G32R32F: expected no color blending but received it anyway. 3 visual.c:8978: Test failed: Offscreen failed for D3DFMT_R32F: expected no color blending but received it anyway. 4 visual.c:8969: Test failed: Offscreen failed for D3DFMT_A16B16G16R16F: Got color 00000000, expected 0x181800. 4 visual.c:8978: Test failed: Offscreen failed for D3DFMT_G16R16F: expected no color blending but received it anyway. 5 visual.c:8326: Test failed: Pixel 14/18 has color 0x00000000, expected 0x0000ff00 5 visual.c:8329: Test failed: Pixel 18/14 has color 0x00000000, expected 0x000000ff 5 visual.c:8332: Test failed: Pixel 18/18 has color 0x00000000, expected 0x0000ffff 5 visual.c:8978: Test failed: Offscreen failed for D3DFMT_R16F: expected no color blending but received it anyway. 5 visual.c:9439: Test failed: stretchrect: Pixel 160,360 has color 0x00000000, expected 0x00ff0000 5 visual.c:9441: Test failed: stretchrect: Pixel 480,360 has color 0x00000000, expected 0x0000ff00 5 visual.c:9443: Test failed: stretchrect: Pixel 480,120 has color 0x00000000, expected 0x000000ff 7 visual.c:8800: Test failed: Texture 1(output color 1) has color 0x00000000, expected 0x0000ff00 7 visual.c:8802: Test failed: Texture 2(output color 2) has color 0x00000000, expected 0x000000ff lspci | grep -i vga says 00:10.0 VGA compatible controller: nVidia Corporation GeForce 7100/nForce 630i (rev a2) and this is on Jaunty x86-64 with the proprietary nvidia 180 driver. I'll attach the output of glxinfo. -- 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 13

[Bug 52874] New: win32u change prevents chromium from starting
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=52874 Bug ID: 52874 Summary: win32u change prevents chromium from starting Product: Wine Version: 7.7 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- The following commit breaks chromium: commit 0528f37fdd9b11cc95d074bb9e261d5127cb6ec3 Author: Jacek Caban <jacek(a)codeweavers.com> Date: Tue Apr 19 15:34:44 2022 +0200 win32u: Move NtUserFindWindowEx implementation from user32. Signed-off-by: Jacek Caban <jacek(a)codeweavers.com> Signed-off-by: Huw Davies <huw(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> chromium just prints a few fixmes and then hangs, using one thread fully. This only affects the sandbox, --no-sandbox is a workaround. Reverting fixes the issue. Download for testing (chrome-win.zip): https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.h… Please use this version for testing, since it's the newest version not affected by bug 52845. -- 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 9

[Bug 51783] New: The ieframe:webbrowser output is too big in Wine
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=51783 Bug ID: 51783 Summary: The ieframe:webbrowser output is too big in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ieframe Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- ieframe:webbrowser outputs ~29kB of data. This is too much and contributes in pushing the WineTest reports above the 1.5MB limit. The traces break down as follows: 0kB failures 26kB todos 3kB traces 0kB test framework (summary lines, etc.) Time to fix Wine to reduce the number of todos! -- 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 51827] New: d3dx10_34:d3dx10 crashes on all versions of Windows
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=51827 Bug ID: 51827 Summary: d3dx10_34:d3dx10 crashes on all versions of Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-d3d-util Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com d3dx10_34:d3dx10 crashes on all versions of Windows: d3dx10.c:2377: this is the last test seen before the exception 00b8:d3dx10: unhandled exception c0000005 at 000000006C50064B https://test.winehq.org/data/patterns.html#d3dx10_34:d3dx10 The crash is random but pretty frequent and happens on AMD, NVidia and QEmu GPUs from Windows 8.1 to Windows 10. The other d3dx10_*:d3dx10 tests don't crash despite using the same source. So that means d3dx10_34 is different and the test fails to take that into account. This test was introduced by the following commit: commit a15527ff29d919b34ae1f599a5319a4b9678f4e2 Author: Nikolay Sivov <nsivov(a)codeweavers.com> Date: Tue Sep 21 08:52:10 2021 +0300 d3dx10_34/tests: Enable tests. Signed-off-by: Nikolay Sivov <nsivov(a)codeweavers.com> Signed-off-by: Matteo Bruni <mbruni(a)codeweavers.com> 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 9

[Bug 28508] New: user32/monitor.ok fails rarely?
by wine-bugs＠winehq.org 20 May '22

20 May '22

http://bugs.winehq.org/show_bug.cgi?id=28508 Bug #: 28508 Summary: user32/monitor.ok fails rarely? Product: Wine Version: 1.3.29 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: user32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Classification: Unclassified Saw this once in a month of runs: ../../../tools/runtest -q -P wine -M user32.dll -T ../../.. -p user32_test.exe.so monitor.c && touch monitor.ok fixme:win:EnumDisplayDevicesW ((null),0,0x22f4d0,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),1,0x22f4d0,0x00000000), stub! monitor.c:269: Test failed: Invalid clip rect: (0 0) x (800 600) err:x11settings:X11DRV_ChangeDisplaySettingsEx No matching mode found 0x480x0 @0! (desktop) err:x11settings:X11DRV_ChangeDisplaySettingsEx No matching mode found 640x0x0 @0! (desktop) The tests were run in a virtual desktop on os: Ubuntu 11.04, 2.6.38-11-generic, pulseaudio 0.9.22-24-g67d18, Advanced Linux Sound Architecture Driver Version 1.0.23. ram: 3963 MB cpu: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz gpu: GeForce 8500 GT/PCI/SSE2 3.3.0 NVIDIA 270.41.06 -- 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 8

[Bug 51680] New: nsi:nsi test_ip_neighbour() fails on unreachable link local entry
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=51680 Bug ID: 51680 Summary: nsi:nsi test_ip_neighbour() fails on unreachable link local entry Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com nsi:nsi has a failure on cw-rx460 from Windows 1709 to 21H1: nsi.c:680: Test failed: AF_INET: 0 vs 1 https://test.winehq.org/data/patterns.html#nsi:nsi The failing test has been introduced by the commit below and failed from the start: commit c09c65f65c188a1870d279ca793c5ad1fc15440d Author: Huw Davies <huw(a)codeweavers.com> AuthorDate: Tue Aug 10 09:20:47 2021 +0100 nsiproxy: Implement IPv4 neighbour enumerate_all. Signed-off-by: Huw Davies <huw(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> Adding some traces shows that the failure happens on a link local entry: AF_INET: 5 InterfaceIndex=10 state=0/0 s_addr=169.254.169.254 I have not identified the corresponding network interface. Also, given that cw-rx460 ad cw-gtx560 are very similar I would expect both to have this issue and I don't know why that's not the case. However what is interesting is that in both cases the state is NlnsUnreachable so I suspect the is_unreachable / IsUnreachable flags are not necessarily meaningful. -- 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 52751] New: `winetricks nocrashdialog` no longer works properly with Wine 7.5(but works with 7.4)
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=52751 Bug ID: 52751 Summary: `winetricks nocrashdialog` no longer works properly with Wine 7.5(but works with 7.4) Product: Wine Version: 7.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mikrutrafal(a)protonmail.com Distribution: --- In Wine 7.4 I disabled crash dialog by `winetricks nocrashdialog` command and when app crashed, then silently it just exit. In Wine 7.5 I see that now is visible console window which exit after while Screenshoot of this window https://user-images.githubusercontent.com/41945903/160272294-dd272f8b-710d-… Steps to reproduce: - Download https://github.com/qarmin/Win32Fuzzer/releases/download/1.1.0/reproducer_64 (require at least Ubuntu 21.10 or similar) - Download https://github.com/qarmin/Win32Fuzzer/releases/download/1.1.0/win_project_6… - Run command `./reproducer win_project_64.exe linux` For now I'm unable to found exact commit with regression, due problem with compilation of Wine. Related winetricks issue - https://github.com/Winetricks/winetricks/issues/1897 -- 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 52914] New: mf:mf - The 64-bit test_h264_decoder() fails on 64-bit Debian 11 + Intel GPU
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=52914 Bug ID: 52914 Summary: mf:mf - The 64-bit test_h264_decoder() fails on 64-bit Debian 11 + Intel GPU Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: mfplat Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- The 64-bit test_h264_decoder() fails on my Debian 11 + Intel GPU machine (see fg-deb64-wow64): mf.c:6780: Test failed: SetOutputType returned 0x80004005. mf.c:6782: Test failed: Release returned 0 mf.c:6799: Test failed: got cbSize 0x3fc000 mf.c:6825: Test failed: ProcessOutput returned 0xc00d6d60 https://test.winehq.org/data/patterns.html#mf:mf configure does not mention any missing library (besides libhal) in either the 32- or the 64-bit builds. A bisect shows that the failures started with the commit below: commit 606505e5643d8df2a23a2cc074fa9b6b2ae8b05f Author: Rémi Bernon <rbernon(a)codeweavers.com> Date: Mon Mar 28 17:35:45 2022 +0200 winegstreamer: Try creating a wg_transform in the H264 decoder. Adding H264 format support in wg_format. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=45988 Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=47084 Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=49715 Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=52183 Signed-off-by: Rémi Bernon <rbernon(a)codeweavers.com> Signed-off-by: Zebediah Figura <zfigura(a)codeweavers.com> 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 4

[Bug 52821] New: Missing support of C++20 Semaphores in built-in Wine C++ runtime
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=52821 Bug ID: 52821 Summary: Missing support of C++20 Semaphores in built-in Wine C++ runtime Product: Wine Version: 7.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcp Assignee: wine-bugs(a)winehq.org Reporter: kle(a)bluewin.ch Distribution: --- Hi all Right at the beginning it should be noted that the following error may have been already described. There seems to exist currently no support of C++20 Semaphores in Wines built-in C++ library. I noticed this limitation with two applications. The following "msvcp140_atomic_wait.dll" related error message is shown when this issue occurs. Both apps crash right after. CXBX-R Xbox emulator (starting with build 374ba5e): wine: Call from 7B011586 to unimplemented function msvcp140_atomic_wait.dll.__std_atomic_wait_direct, aborting wine: Call from 7B011586 to unimplemented function msvcp140_atomic_wait.dll.__std_atomic_notify_one_direct, aborting PCSX-Redux PSX emulator (all newer builds since 4317): wine: Call from 0000000000272B9E to unimplemented function msvcp140_atomic_wait.dll.__std_atomic_wait_direct, aborting wine: Unimplemented function msvcp140_atomic_wait.dll.__std_atomic_wait_direct called at address 0000000000272B9E (thread 010c), starting debugger... wine: Call from 0000000000272B9E to unimplemented function msvcp140_atomic_wait.dll.__std_atomic_notify_one_direct, aborting Both applications worked before the "std::binary_semaphore" C++20 type was introduced. It is confirmed for Wine 7.0 that it can handle this situation when vcrun2019 (native MS Visual C++ 2019) is installed via winetricks. But for whatever reason this stopped to work in later Wine 7.x devel versions. A further workaround was to put a native "msvcp140_atomic_wait.dll" into the program folder. I can confirm that this helped at least for a while in conjunction with the PCSX-Redux emulator. But also here this tweak stopped to work in later Wine 7.x devel versions. More information can be found at the CXBX-R GitHub issue page: https://github.com/Cxbx-Reloaded/Cxbx-Reloaded/issues/2347 -- 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 11

[Bug 51612] New: Stellaris launcher (Paradox) does not launch
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=51612 Bug ID: 51612 Summary: Stellaris launcher (Paradox) does not launch Product: Wine Version: 6.15 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: --- The game Stellaris installs and works using the stellaris.exe file but the launcher (dowser.exe) fails to launch. I am using Kubuntu 21.04 and this is a fresh installation as it does work on a 2nd PC I have, also Kubuntu 21.04. The only difference of note between the machines is this machine has an AMD 5800X CPU. The terminal returns (duplicated lines removed): scott(a)scottubuntu:~/.winestella1/drive_c/GOG Games/Stellaris$ WINEPREFIX=~/.winestella1 wine dowser.exe 002c:fixme:winediag:LdrInitializeThunk wine-staging 6.15 is a testing version containing experimental patches. 002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when filing bug reports on winehq.org. 0034:fixme:font:get_name_record_codepage encoding 29 not handled, platform 1. 006c:fixme:font:get_name_record_codepage encoding 29 not handled, platform 1. 006c:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1. 0034:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1. 007c:fixme:font:get_name_record_codepage encoding 29 not handled, platform 1. 007c:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1. 0090:fixme:font:get_name_record_codepage encoding 29 not handled, platform 1. 0090:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1. 002c:fixme:font:get_name_record_codepage encoding 29 not handled, platform 1. 002c:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1. 00f8:fixme:font:get_name_record_codepage encoding 29 not handled, platform 1. 00f8:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1. 0024:fixme:font:get_name_record_codepage encoding 29 not handled, platform 1. 0024:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1. 0100:fixme:font:get_name_record_codepage encoding 29 not handled, platform 1. 0100:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1. 0100:fixme:process:SetProcessPriorityBoost (FFFFFFFFFFFFFFFF,1): stub 0118:fixme:font:get_name_record_codepage encoding 29 not handled, platform 1. 0118:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1. 0120:fixme:font:get_name_record_codepage encoding 29 not handled, platform 1. 0120:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1. 0128:fixme:font:get_name_record_codepage encoding 29 not handled, platform 1. 0128:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1. scott(a)scottubuntu:~/.winestella1/drive_c/GOG Games/Stellaris$ wine: Unhandled page fault on write access to 0000000000000000 at address 00007F756DC2CF91 (thread 0070), starting debugger... 0070:err:seh:start_debugger Couldn't start debugger L"winedbg --auto 96 72" (1115) Read the Wine Developers Guide on how to set up winedbg or another debugger I attach the output of this system request. -- 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