January 2022 - Wine-Bugs - list.winehq.org

[Bug 51376] New: Wine causes PC to lock or crash wine when loading more than 1 VST addon into WaveLab 6
by WineHQ Bugzilla May 20, 2022

May 20, 2022

https://bugs.winehq.org/show_bug.cgi?id=51376 Bug ID: 51376 Summary: Wine causes PC to lock or crash wine when loading more than 1 VST addon into WaveLab 6 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: --- Created attachment 70232 --> https://bugs.winehq.org/attachment.cgi?id=70232 backtrace I have a number of VST add-ons I use with Wavelab, they come from a number of different software houses and work differently, for example some require vcrun libraries to work while others do not. In the main, I can load any single add-on and it works as expected but as soon as I add/open a second add-on my PC will either crash wine or it will lock up altogether requiring a hard restart. This was not an issue in wine 5.0. Backtrace is attached. Possibly a duplicate of bug 51259 or is quite similar. -- 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 51283] New: d3d8:device breaks evr:evr on w7u-2qxl
by WineHQ Bugzilla May 20, 2022

May 20, 2022

https://bugs.winehq.org/show_bug.cgi?id=51283 Bug ID: 51283 Summary: d3d8:device breaks evr:evr on w7u-2qxl Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The WineTest reports show that evr:evr crashes on w7u-2qxl: https://test.winehq.org/data/patterns.html#evr:evr evr.c:1335: Test failed: Unexpected hr 0x80070057. evr.c:1335: this is the last test seen before the exception 07ac:evr: unhandled exception c0000005 at 0040CBD0 evr:evr:07ac done (-1073741819) in 0s Test failed: crash (c0000005) However when run on its own it succeeds consistently. It turns out that it is d3d8:device that causes evr:evr to crash. More specifically it is test_multi_adapter() that interferes with evr:evr. Also if d3d8:device succeeds then evr:evr crashes but if d3d8:device fails as shown below then evr:evr succeeds as can be seen by comparing the pattern below with the evr:evr one. https://test.winehq.org/data/patterns.html#d3d8:device device.c:4205: Test failed: Got a different mode. device.c:4208: Test failed: Got a different mode. -- 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 50462] New: Ulead Photo Explorer 8.5 Installed but failed on startup
by WineHQ Bugzilla May 20, 2022

May 20, 2022

https://bugs.winehq.org/show_bug.cgi?id=50462 Bug ID: 50462 Summary: Ulead Photo Explorer 8.5 Installed but failed on startup Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: wesley(a)merlin-eng.com Distribution: --- Created attachment 69087 --> https://bugs.winehq.org/attachment.cgi?id=69087 This is from the error window that came up when the program failed The program (Ulead Photo Explorer 8.5) appeared to install correctly. This program is designed to browse image files IE: .jpg. It installs with Ulead Photo Impact 10. I did not try to associate any files with either program (this should not be necessary). On startup Ulead Photo Explorer 8.5 failed, giving the attached back trace file. Photo Impact 10 installed at the same time and worked fine. -- 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 45959] New: Editpad Lite 7 GUI not rendered correctly
by wine-bugs＠winehq.org May 20, 2022

May 20, 2022

https://bugs.winehq.org/show_bug.cgi?id=45959 Bug ID: 45959 Summary: Editpad Lite 7 GUI not rendered correctly Product: Wine Version: 3.17 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: --- Created attachment 62506 --> https://bugs.winehq.org/attachment.cgi?id=62506 Screenshot of GUI The command menu line (top line) is not rendered correctly, please see the attachment. It should display buttons with the following descriptions: File, Edit, Search, Go, Block, Extra, Convert, Options, View, Help. By mousing over and clicking and resizing the window they will eventually be rendered correctly. The installer can be downloaded at https://www.editpadlite.com/download.html Problem exists in both 32 and 64 bit prefixes and different Windows versions. My system: Kubuntu 18.04.01 -- 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 4

[Bug 14841] New: ntdll: file.ok fails in OpenSolaris but not Linux
by wine-bugs＠winehq.org May 20, 2022

May 20, 2022

http://bugs.winehq.org/show_bug.cgi?id=14841 Summary: ntdll: file.ok fails in OpenSolaris but not Linux Product: Wine Version: 1.1.2 Platform: PC OS/Version: Solaris Status: NEW Keywords: testcase Severity: enhancement Priority: P2 Component: ntdll AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Created an attachment (id=15384) --> (http://bugs.winehq.org/attachment.cgi?id=15384) +file in git, bzip2 -9'ed austin(a)opensolaris:~/wine-git/dlls/ntdll/tests$ make testclean ; rm -rf ~/.wine ; make file.ok rm -f atom.ok change.ok env.ok error.ok exception.ok generated.ok info.ok large_int.ok file.ok om.ok path.ok port.ok reg.ok rtl.ok rtlbitmap.ok rtlstr.ok string.ok time.ok ../../../tools/runtest -q -P wine -M ntdll.dll -T ../../.. -p ntdll_test.exe.so file.c && touch file.ok wine: created the configuration directory '/export/home/austin/.wine' err:iphlpapi:getNumWithOneHeader Unable to open '/proc/net/route' to count entries! err:iphlpapi:getRouteTable unimplemented! file.c:169: Test failed: wrong status deadbabe file.c:170: Test failed: wrong info 3735928559 file.c:194: Test failed: wrong status deadbabe file.c:195: Test failed: wrong info 3735928559 file.c:196: Test failed: read handle is signaled file.c:284: Test failed: wrong status deadbabe file.c:285: Test failed: wrong info 3735928559 file.c:286: Test failed: event is signaled make: *** [file.ok] Error 8 +file attached -- 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 11

[Bug 51827] New: d3dx10_34:d3dx10 crashes on all versions of Windows
by WineHQ Bugzilla May 20, 2022

May 20, 2022

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 51783] New: The ieframe:webbrowser output is too big in Wine
by WineHQ Bugzilla May 20, 2022

May 20, 2022

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 19183] New: "make test" still fails on d3d9/tests/visual.c
by wine-bugs＠winehq.org May 20, 2022

May 20, 2022

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 51680] New: nsi:nsi test_ip_neighbour() fails on unreachable link local entry
by WineHQ Bugzilla May 20, 2022

May 20, 2022

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 51612] New: Stellaris launcher (Paradox) does not launch
by WineHQ Bugzilla May 20, 2022

May 20, 2022

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