April 2023 - Wine-bugs - list.winehq.org

[Bug 54776] New: SHD Hub hangs in endless loop with 0074:fixme:nsi:ipv6_forward_enumerate_all not implemented
by WineHQ Bugzilla 05 Apr '23

05 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=54776 Bug ID: 54776 Summary: SHD Hub hangs in endless loop with 0074:fixme:nsi:ipv6_forward_enumerate_all not implemented Product: Wine Version: 8.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: maiktapwagner(a)aol.com Distribution: --- Created attachment 74267 --> https://bugs.winehq.org/attachment.cgi?id=74267 Console output (wine-8.4 on Slackware64/Multilib) Download is at: http://download.shd-kps.de/kps-ftp/SHD_Hub/SHD_Hub.exe with bash-5.1$ sha256sum SHD_Hub.exe 99a83f461e8eed52b70e663250ed07b4f19077b8b1f5349dc8307c9947607f00 SHD_Hub.exe The application requires .net 4.7.2 which it is trying to install with the installation package but this fails. I prepared my prefix with "winetricks dotnet48" and corefonts which makes it possible for the application to start from the command line. However my console gets lots of messages with: 0074:fixme:nsi:ipv6_forward_enumerate_all not implemented Console output is attached. -- 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 54782] New: user32:msg - test_PeekMessage2() is sometimes missing a WM_MOUSEMOVE message on Windows
by WineHQ Bugzilla 05 Apr '23

05 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=54782 Bug ID: 54782 Summary: user32:msg - test_PeekMessage2() is sometimes missing a WM_MOUSEMOVE message on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com user32:msg - test_PeekMessage2() is sometimes missing a WM_MOUSEMOVE message on Windows: msg.c:13603: Test failed: no message available msg.c:13621: Test failed: no message available See https://test.winehq.org/data/patterns.html#user32:msg So far there are only 3 instances all on Windows 10: * 2023-03-06 on fgtb-w10pro64-rx550-64 * 2023-03-10 on fgtb-w10pro64-rx550-64 * 2023-04-04 on w1064-tsign-32 -- 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 1

[Bug 54763] New: Build-time tests fail in an autobuilder environment
by WineHQ Bugzilla 05 Apr '23

05 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=54763 Bug ID: 54763 Summary: Build-time tests fail in an autobuilder environment Product: vkd3d Version: 1.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: vkd3d Assignee: wine-bugs(a)winehq.org Reporter: smcv(a)collabora.com Distribution: --- In a typical distribution autobuilder environment, all builds will be run in a chroot or container, usually on server-class hardware or in a virtual machine. This means tests that just do computation (such as shader compilation) should still succeed, but tests that want to access a real GPU will find that either there is no VkDevice at all, or there is a VkDevice but it's only software rendering (lavapipe). It seems like vkd3d already has some partial handling for this: run_shader_tests_vulkan() skips itself if a VkDevice cannot be created. However, run_shader_tests_d3d12() still tries to run, and crashes when it can't create a Vulkan instance, for example: FAIL: tests/cast-to-half ======================== vkd3d:err:vkd3d_instance_init Failed to create Vulkan instance, vr -9. vkd3d:fixme:hresult_from_vk_result Unhandled VkResult -9. vkd3d:err:vkd3d_instance_init Failed to create Vulkan instance, vr -9. vkd3d:fixme:hresult_from_vk_result Unhandled VkResult -9. FAIL tests/cast-to-half.shader_test (exit status: 139) (Exit status 139 is a segmentation fault.) Would you consider patches that make the tests skip themselves in this situation? Or should distro packaging just not be running build-time tests at all? -- 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 54740] New: GetAdaptersInfo function is not returning mac address information correctly
by WineHQ Bugzilla 04 Apr '23

04 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=54740 Bug ID: 54740 Summary: GetAdaptersInfo function is not returning mac address information correctly Product: Wine Version: 8.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: peter.walsh(a)lamresearch.com Distribution: --- The GetAdaptersInfo function is not returning the same information on wine vs windows. I've tried this with stable wine 8 and wine 8.4 staging. We have an old program that is calling this function to get the mac address of the system for license key purposes. When run via wine the last pair of digits in the mac address are missing - and thus the software can't be registered or run. There is likely a byte offset missing, causing the last 2 bytes to be dropped? Example: System has mac address 82-5E-F4-3b-b6-66 - can see this ok via "wine ipconfig /all" However the legacy program when executed only sees address "82-5E-F4-3B-B6-". -- 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 7586] Joost 1.1.8 beta will not launch
by WineHQ Bugzilla 04 Apr '23

04 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=7586 Maik Wagner <maiktapwagner(a)aol.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maiktapwagner(a)aol.com --- Comment #29 from Maik Wagner <maiktapwagner(a)aol.com> --- Created attachment 74273 --> https://bugs.winehq.org/attachment.cgi?id=74273 Beta 1.1.8 in XP Mode (wine 8.5) Downloaded from archive.org bash-5.1$ sha1sum JoostSetup-Beta-1.1.8.exe 10d30a1632d70ed0ecf359f62a44e8f7adbe56a5 JoostSetup-Beta-1.1.8.exe In both XP and Windows 10 mode the installer wouldn't even start. -- 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 0

[Bug 54727] New: LDAP Explorer (LEX) throws an exception when attempting to connect over SSL
by WineHQ Bugzilla 04 Apr '23

04 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=54727 Bug ID: 54727 Summary: LDAP Explorer (LEX) throws an exception when attempting to connect over SSL Product: Wine Version: 8.4 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: wldap32 Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Created attachment 74233 --> https://bugs.winehq.org/attachment.cgi?id=74233 WINEDEBUG=+wldap32 Steps to reproduce: 1. Run `winetricks dotnet452` 2. Run `wine LEX.msi` 3. Run `docker run --detach --env LDAP_TLS_VERIFY_CLIENT=never -p636:636 osixia/openldap` 4. Run `wine 'C:\Program Files (x86)\CerroTorre\LEX\LEX.exe'` 5. Wait for the splash screen to close, or move the "LDAP Connections" window out from under it 6. On the "Advanced" tab, check "Ignore server certificate errors" 7. On the "Server" tab, enter "localhost" for the server and check "SSL connect" (the port will automatically change from 389 to 636) 8. On the "Server" tab, click "Fetch" At this point, an "Unhandled exception" dialog appears that says "The feature is not supported." Furthermore, the program crashes if you click the Quit button on the dialog, but since the dialog shouldn't appear in the first place, it's understandable that it doesn't function correctly. The relevant part of the terminal output is: 0024:fixme:wldap32:ldap_set_optionW Unsupported option: 0x0a 0x0a is LDAP_OPT_SSL, which is not yet implemented in Wine. $ sha256sum LEX.msi 68810d827de3f90c0223fcb18a66dde49aee189789b37dd4cdeebe013fa402be -- 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 44156] New: Mini Ninjas demo - colored area under the player and NPCs with builtin d3dx9_34
by wine-bugs＠winehq.org 03 Apr '23

03 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=44156 Bug ID: 44156 Summary: Mini Ninjas demo - colored area under the player and NPCs with builtin d3dx9_34 Product: Wine Version: 3.0-rc1 Hardware: x86-64 URL: http://www.fileplanet.com/203860/200000/fileinfo/Mini- Ninjas-Demo OS: Linux Status: NEW Keywords: download Severity: minor Priority: P2 Component: directx-d3dx9 Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- Created attachment 59917 --> https://bugs.winehq.org/attachment.cgi?id=59917 screenshot How it looks with builtin d3dx9_34 -- 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 34242] New: Dolphin Emulator: Error compiling pixel shader
by wine-bugs＠winehq.org 03 Apr '23

03 Apr '23

http://bugs.winehq.org/show_bug.cgi?id=34242 Bug #: 34242 Summary: Dolphin Emulator: Error compiling pixel shader Product: Wine Version: 1.7.0 Platform: x86 OS/Version: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: 00cpxxx(a)gmail.com Classification: Unclassified Created attachment 45563 --> http://bugs.winehq.org/attachment.cgi?id=45563 screenshot The emulator Dolphin shows an error when trying to play a home brew game. Steps to reproduce: Download Dolphin 3.0 https://dolphin-emu.org/download/?ref=btn Download Newo Asteroids http://wiibrew.org/wiki/Newo_Asteroids (download link in the right table) Using the emulator open the BOOT.DOL file from the root folder of the game. The result is the attachment followed by a crash. "winetricks d3dcompiler_43" workarounds the 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 15

[Bug 41310] New: World in Conflict can' t get past loading screen in tutorial
by wine-bugs＠winehq.org 03 Apr '23

03 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=41310 Bug ID: 41310 Summary: World in Conflict can't get past loading screen in tutorial Product: Wine Version: 1.9.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: alex3kov(a)zoho.com Distribution: --- Created attachment 55640 --> https://bugs.winehq.org/attachment.cgi?id=55640 Log with WINEDEBUG=+d3d9 1.0.1.1 version of the game from gog.com. After Alt-Tabbing or switching to another desktop workspace I can't get back into the game. Starting missions gets stuck in the same way. According to setup manual here https://appdb.winehq.org/objectManager.php?sClass=version&iId=20703 I've set d3d10 to "Disabled", replaced dxdiagn with native and set it to "Native" in winecfg - so the game uses DX9. Log with WINEDEBUG=+d3d9 is attached. It turned out to be 10Mb, so I gzipped it. These lines look suspicious: fixme:d3d:debug_d3dformat Unrecognized 0x434f5441 (as fourcc: ATOC) WINED3DFORMAT! fixme:d3d:debug_d3dformat Unrecognized 0x41415353 (as fourcc: SSAA) WINED3DFORMAT! I can provide more logs, test patches etc. -- 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 25

[Bug 54083] New: Call of Juarez: Bound in Blood shows a black screen
by WineHQ Bugzilla 03 Apr '23

03 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=54083 Bug ID: 54083 Summary: Call of Juarez: Bound in Blood shows a black screen Product: vkd3d Version: 1.5 Hardware: x86-64 OS: Linux Status: NEW Severity: minor Priority: P2 Component: hlsl Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- Created attachment 73626 --> https://bugs.winehq.org/attachment.cgi?id=73626 log Workaround is setting d3dcompiler_47 - native,builtin vkd3d-1.5-93-g1b11b576 -- 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