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

[Bug 54802] New: lol crashing steam deck
by WineHQ Bugzilla April 8, 2023

April 8, 2023

https://bugs.winehq.org/show_bug.cgi?id=54802 Bug ID: 54802 Summary: lol crashing steam deck Product: Wine Version: 8.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: atienza.marklawrence15(a)gmail.com Distribution: --- wine cannot support league of legnds main game window. it always crashes see attached dump file. im playing on linux steam deck. i was able to play before bht when I reformatted and reinstalled lol, it is not working now. -- 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 53965] New: Writing a new line after writing a full end element(WriteFullEndElement)
by WineHQ Bugzilla April 7, 2023

April 7, 2023

https://bugs.winehq.org/show_bug.cgi?id=53965 Bug ID: 53965 Summary: Writing a new line after writing a full end element(WriteFullEndElement) Product: Wine Version: 7.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: xmllite Assignee: wine-bugs(a)winehq.org Reporter: k.kahurani(a)gmail.com Distribution: --- Created attachment 73553 --> https://bugs.winehq.org/attachment.cgi?id=73553 Test case It doesn't look possible to write a whitespace character after writing a full end element with WriteFullEndElement. It looks to me like this should be possible just like it is possible with WriteEndElement. I have also noticed that native xmllite sometimes breaks(not sure whether this is a feature or a bug) but at times native xmllite doesn't write new lines after writing the elements. I'm not sure how exactly this happens but the possible work-around in this is to manually write new lines(with WriteWhitespace) which means this issue could easily break working code. I'm not sure how to fix this right away so I am submitting a bug. As can be seen in the attached diff, wine doesn't pass the test but native does. -- 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 54798] New: The zoom meeting font cannot be displayed normally in the Chinese language environment
by WineHQ Bugzilla April 7, 2023

April 7, 2023

https://bugs.winehq.org/show_bug.cgi?id=54798 Bug ID: 54798 Summary: The zoom meeting font cannot be displayed normally in the Chinese language environment Product: Wine Version: 8.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: 399989567(a)qq.com Distribution: --- After downloading and running zoom, all fonts cannot be displayed normally -- 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 54790] New: quartz:systemclock - test_advise() sometimes gets an unexpected even in Wine (GitLab CI)
by WineHQ Bugzilla April 6, 2023

April 6, 2023

https://bugs.winehq.org/show_bug.cgi?id=54790 Bug ID: 54790 Summary: quartz:systemclock - test_advise() sometimes gets an unexpected even in Wine (GitLab CI) Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: quartz Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- quartz:systemclock - test_advise() sometimes gets an unexpected even in Wine: systemclock.c:242: Test failed: Event should not be signaled. This mostly happens on the GitLab CI but it did happen once in the nightly WineTest runs: * 2022-11-15 on test-linux-32 for MR!1370 * 2022-12-14 on fg-deb64-t32 * 2022-12-19 on test-linux-32 for MR!1846 * 2023-03-28 on test-linux-32 for MR!2483 * 2023-04-05 on test-linux-32 for MR!2588 The GitLab CI and fg-* test configurations are the most likely to be busy with other tasks while the tests are running so it is likely a timing issue caused by having too much load on the system running the test. It should be noted that this never happened on Windows though, particularly not on the fgtb-w10pro64 VM which has the same host as the fg-* test configurations. So this seems to be a Wine 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 3

[Bug 54789] New: IK Product Manager: Hangs when downloading product
by WineHQ Bugzilla April 5, 2023

April 5, 2023

https://bugs.winehq.org/show_bug.cgi?id=54789 Bug ID: 54789 Summary: IK Product Manager: Hangs when downloading product Product: Wine Version: 8.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gearoidburke(a)outlook.com Distribution: --- Created attachment 74283 --> https://bugs.winehq.org/attachment.cgi?id=74283 Output of wine running the application IK Product Manger (https://www.ikmultimedia.com/products/productmanager/) (Version 1.05) should be able to download and install VST plugins from IK Multimedia, however upon clicking the install button for any plugin, the application will hang and become unresponsive. I know this is superficially similar to my previous bug report on the same application basically the same problem (https://bugs.winehq.org/show_bug.cgi?id=50643) however, the particular bug I was reporting then seems to have been fixed as the log file I have attached does not contain the same error anymore. I created a fresh prefix (64-bit) for this and am running Wine 8.5 (Staging). I'm on Arch Linux 64-bit and my kernel version is Linux 6.2.8-2. My hardware is as follows: Thinkpad X13 Yoga, Intel Core i5-10310U with Intel integrated graphics. -- 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 54776] New: SHD Hub hangs in endless loop with 0074:fixme:nsi:ipv6_forward_enumerate_all not implemented
by WineHQ Bugzilla April 5, 2023

April 5, 2023

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 April 5, 2023

April 5, 2023

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 April 5, 2023

April 5, 2023

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 April 4, 2023

April 4, 2023

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 April 4, 2023

April 4, 2023

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