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

[Bug 35129] New: Cloning Clyde refuses to start with built-in d3dx9_36
by wine-bugs＠winehq.org March 18, 2023

March 18, 2023

http://bugs.winehq.org/show_bug.cgi?id=35129 Bug ID: 35129 Summary: Cloning Clyde refuses to start with built-in d3dx9_36 Product: Wine Version: 1.7.8 Hardware: x86 URL: http://www.fileplanet.com/224883/220000/fileinfo/Cloni ng-Clyde-Client-%28Trial%29 OS: Linux Status: NEW Keywords: download Severity: minor Priority: P2 Component: directx-d3dx9 Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: wine-bugs(a)winehq.org Classification: Unclassified Created attachment 46859 --> http://bugs.winehq.org/attachment.cgi?id=46859 terminal output (+d3dx traces) The game won't start with the built-in d3dx9_36, it flashes a black window for a brief moment then it quits without an error message. +d3dx debug channel added only 4 lines to the terminal output as can be seen at the end of the attached log file. Please install ie8 via winetricks when testing with the demo version as the launcher doesn't work with Wine's IE. 'winetricks d3dx9_36' is a workaround. Fedora 19 Nvidia binary drivers 325.15 wine-1.7.8-88-gfb75292 -- 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 12

[Bug 54035] New: Tom Clancy's Rainbow Six: Vegas 2 fails to launch
by WineHQ Bugzilla March 18, 2023

March 18, 2023

https://bugs.winehq.org/show_bug.cgi?id=54035 Bug ID: 54035 Summary: Tom Clancy's Rainbow Six: Vegas 2 fails to launch Product: vkd3d Version: 1.5 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: vkd3d Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- 05b8:err:d3d_shader:shader_spirv_scan_shader Failed to scan shader, ret -3. 05b8:fixme:d3d_shader:shader_spirv_scan_shader Shader log: 05b8:fixme:d3d_shader:shader_spirv_scan_shader <anonymous>: E0002: Invalid DXBC magic. 05b8:fixme:d3d_shader:shader_spirv_scan_shader 054c:fixme:d3dcompiler:D3DCompile2 Ignoring flags 0x1000. 054c:err:d3dcompiler:D3DCompile2 Failed to compile shader, vkd3d result -4. 054c:err:d3dcompiler:D3DCompile2 Shader log: 054c:err:d3dcompiler:D3DCompile2 <anonymous>:1:537: E5005: Function "tex2D" is not defined. 054c:err:d3dcompiler:D3DCompile2 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 3

[Bug 52409] New: Regression: battle.net does not open when multiple monitors are connected.
by WineHQ Bugzilla March 18, 2023

March 18, 2023

https://bugs.winehq.org/show_bug.cgi?id=52409 Bug ID: 52409 Summary: Regression: battle.net does not open when multiple monitors are connected. Product: Wine Version: 7.0-rc6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: GloriousEggroll(a)gmail.com Regression SHA1: 45dcaf02fcd9e929b406854b4b78371bc3886031 Distribution: --- If more than one monitor is enabled on the system battle.net fails to open. If I disable all but one monitor it then allows battle.net to load. last known working version was 6.22, broke in 6.23. Bisected to first bad commit 45dcaf02fcd9e929b406854b4b78371bc3886031 -- 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 52083] New: Some test_TimerResolution() tests fail randomly in ntdll:time
by WineHQ Bugzilla March 18, 2023

March 18, 2023

https://bugs.winehq.org/show_bug.cgi?id=52083 Bug ID: 52083 Summary: Some test_TimerResolution() tests fail randomly in ntdll:time Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Some test_TimerResolution() tests fail randomly in ntdll:time: time.c:293: Test failed: expected requested timer resolution 156250, got 10006 time.c:298: Test failed: expected requested timer resolution 20000, got 10006 time.c:310: Test failed: expected new timer resolution 20000, got 10006 time.c:318: timer resolution: 5000(max) <= 5003(cur) <= 20000(prev) <= 156250(min) time.c:322: Test failed: expected new timer resolution 20000, got 5003 time.c:322: Test failed: NtQueryTimerResolution() expected timer resolution 5003, got 20000 time.c:328: Test failed: expected requested timer resolution 5003, got 75011 https://test.winehq.org/data/patterns.html#ntdll:time The number of failures varies and six seems to be a maximum. This appears to only impact Windows 10 1709+ but impacts both the TestBot VMs and real test machines (cw-gtx560 and cw-rx460). Based on the current failure pattern it looks like the failures started on 2021-09-30. That is, there was no failure for any of the 252 builds from 2021-09-21 to 2021-09-29 and there has been at least one failure for every build since. Yet the failure is reproducible with the commit that introduced the tests (6015fee5b218), and also with the one that fixed some of the issues a few days later (b2c89b1a41fa): commit 6015fee5b21870ddd57477843354173d2e7f9696 Author: François Gouget <fgouget(a)codeweavers.com> AuthorDate: Thu Jul 29 17:24:15 2021 +0200 ntdll/tests: Add some Nt{Query,Set}TimerResolution() tests. Signed-off-by: Francois Gouget <fgouget(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 48676] New: CD not detetected in Exact Audio Copy since wine 4.21 anymore
by WineHQ Bugzilla March 18, 2023

March 18, 2023

https://bugs.winehq.org/show_bug.cgi?id=48676 Bug ID: 48676 Summary: CD not detetected in Exact Audio Copy since wine 4.21 anymore Product: Wine Version: 4.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mountmgr.sys Assignee: wine-bugs(a)winehq.org Reporter: bastian.dev(a)gmail.com Distribution: --- When I insert a audio cd in the drive, Exact Audio Copy (v 1.3) doesn't detect it. It just doesn't show anything. 4.20 was the last version it worked with. I've also tried wine 4.21 and 5.0. -- 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 54317] New: Change to exec_wineloader made wine not start at all
by WineHQ Bugzilla March 18, 2023

March 18, 2023

https://bugs.winehq.org/show_bug.cgi?id=54317 Bug ID: 54317 Summary: Change to exec_wineloader made wine not start at all Product: Wine Version: 8.0-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: hibbsncc1701(a)gmail.com Distribution: --- Attempting to start wine with a pre-existing prefix results in a failure to load ntdll / kernel32. With messages like "wine: could not load kernel32.dll, status c0000135" and 002c:err:module:load_wow64_ntdll failed to load L"\\??\\C:\\windows\\system32\\ntdll.dll" error 4000000e wine: Unhandled page fault on execute access to 00000000 at address 00000000 (thread 002c), starting debugger... being printed in the console. Wine then attempts to start winedbg only to get stuck in a forkbomb. Where winedbg won't start, triggering an exception, which will cause another attempt to start winedbg. At a rate of about 4-5 attempts a second. Attempting to ctrl-c it doesn't work, and requires manually terminating all of wine's processes. (Of which are numerous as wine will also attempt to start conhost.exe for each winedbg it attempts to load. None of which will terminate on their own.) Attempting to start wine with a fresh prefix results in an incomplete prefix directory. (Only the dosdevices / windows directories, and registry hives are present in the prefix. Of those windows is empty save for the syswow64 and system32 directories of which both are completely empty.) Attempting to start that prefix again causes the same winedbg behavior as above. Performing a bisect revealed: $ git bisect bad d45de318748639cfd1e80a976b39f5e19213990f is the first bad commit commit d45de318748639cfd1e80a976b39f5e19213990f Author: Alexandre Julliard <julliard(a)winehq.org> Date: Tue Nov 22 12:08:19 2022 +0100 ntdll: Always set WINELOADER variable to the current loader name. dlls/ntdll/unix/env.c | 3 +++ dlls/ntdll/unix/loader.c | 48 +++++++++++++++++++++--------------------------- 2 files changed, 24 insertions(+), 27 deletions(-) Reverting d45de318748639cfd1e80a976b39f5e19213990f fixed the issue on my system. -- 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 45328] New: Unusable GUI for ElsterFormular 19.5
by wine-bugs＠winehq.org March 18, 2023

March 18, 2023

https://bugs.winehq.org/show_bug.cgi?id=45328 Bug ID: 45328 Summary: Unusable GUI for ElsterFormular 19.5 Product: Wine Version: 3.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: Markus.Elfring(a)web.de Distribution: --- It would be nice if I could use the application “ElsterFormular 19.5 (2018-06-14)” together with the software “Wine 3.10-820.1” finally. https://www.elster.de/eportal/infoseite/elsterformular https://appdb.winehq.org/objectManager.php?sClass=application&iId=1925 elfring(a)Sonne:~> wine C:\\windows\\command\\start.exe /Unix /home/elfring/.wine/dosdevices/c:/users/elfring/Start\ Menu/Programs/ElsterFormular/ElsterFormular.lnk 0009:fixme:exec:SHELL_execute flags ignored: 0x00000100 0009:fixme:exec:SHELL_execute flags ignored: 0x00004100 elfring(a)Sonne:~> 0036:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0036:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0036:fixme:msvcrt:type_info_name_internal_method type_info_node parameter ignored … Its graphical user interface does not respond to mouse clicks so far. -- 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 5

[Bug 41102] New: Alan Wake' s American Nightmare crashes at launch randomly with 'm->state == STATE_PASSIVE'
by wine-bugs＠winehq.org March 18, 2023

March 18, 2023

https://bugs.winehq.org/show_bug.cgi?id=41102 Bug ID: 41102 Summary: Alan Wake's American Nightmare crashes at launch randomly with 'm->state == STATE_PASSIVE' Product: Wine Version: 1.9.16 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: winepulse.drv Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com CC: aeikum(a)codeweavers.com Distribution: --- Crashes very randomly, so hard to reproduce. Assertion 'm->state == STATE_PASSIVE' failed at pulse/mainloop.c:787, function pa_mainloop_prepare(). Aborting. wine: Assertion failed at address 0xf779ad49 (thread 0028), starting debugger... Unhandled exception: assertion failed in 32-bit code (0xf779ad49). Backtrace: =>0 0xf779ad49 __kernel_vsyscall+0x9() in [vdso].so (0x7c1bd2e8) 1 0xf73d95c9 gsignal+0x38() in libc.so.6 (0x7c1bd2e8) 2 0xf73daca7 abort+0x156() in libc.so.6 (0x7c1bd2e8) 3 0x7a9e9e47 pa_mainloop_prepare+0x286() in libpulse.so.0 (0x7c1bd2e8) 4 0x7a9ea923 pa_mainloop_iterate+0x32() in libpulse.so.0 (0x04a0dc98) 5 0x7aa512b3 pulse_test_connect+0x182() [/wine/dlls/winepulse.drv/mmdevdrv.c:566] in winepulse (0x04a0dc98) 6 0x7aa58590 AUDDRV_GetPriority+0x2f() [/wine/dlls/winepulse.drv/mmdevdrv.c:947] in winepulse (0x04a0dcc8) 7 0x7b8199bf init_driver+0x25e() [/wine/dlls/mmdevapi/main.c:103] in mmdevapi (0x04a0e1c8) 8 0x7b81a21c DllGetClassObject+0x3b(rclsid=<couldn't compute location>, riid=<couldn't compute location>, ppv=<couldn't compute location>) [/wine/dlls/mmdevapi/main.c:282] in mmdevapi (0x04a0e1f8) 9 0x7e95fc1c apartment_getclassobject+0x11b(apt=<is not available>, dllpath=<is not available>, apartment_threaded=<is not available>, rclsid=<is not available>, riid=<is not available>, ppv=<is not available>) [/wine/dlls/ole32/compobj.c:1372] in ole32 (0x04a0e268) 10 0x7e962bd5 get_inproc_class_object+0x114(apt=<is not available>, regdata=<is not available>, rclsid=<is not available>, riid=<is not available>, hostifnecessary=<is not available>, ppv=<is not available>) [/wine/dlls/ole32/compobj.c:2930] in ole32 (0x04a0e4c8) 11 0x7e965565 CoGetClassObject+0x50f(rclsid=<is not available>, dwClsContext=<is not available>, pServerInfo=<is not available>, iid=<is not available>, ppv=<is not available>) [/wine/dlls/ole32/compobj.c:3068] in ole32 (0x04a0e578) 12 0x7e966be1 CoCreateInstanceEx+0x1db(rclsid=<is not available>, pUnkOuter=<is not available>, dwClsContext=<is not available>, pServerInfo=<is not available>, cmq=<is not available>, pResults=<is not available>) [/wine/dlls/ole32/compobj.c:3305] in ole32 (0x04a0e5f8) 13 0x7e9670dd CoCreateInstance+0x67(rclsid=<is not available>, pUnkOuter=<is not available>, dwClsContext=<is not available>, iid=<is not available>, ppv=<is not available>) [/wine/dlls/ole32/compobj.c:3201] in ole32 (0x04a0e668) 14 0x01e8347b in fmodex (+0x347a) (0x04a0e694) 15 0x01f07e45 in fmodex (+0x87e44) (0x04a0e6bc) 16 0x01f07f7a in fmodex (+0x87f79) (0x04a0e6d4) 17 0x01f080b8 in fmodex (+0x880b7) (0x04a0e70c) 18 0x01ea2e74 in fmodex (+0x22e73) (0x04a0e728) 19 0x01e569b4 in snd_w32_f (+0x69b3) (0x04a0e900) 20 0x01e573fa in snd_w32_f (+0x73f9) (0x04a0e928) 21 0x01e57a9c in snd_w32_f (+0x7a9b) (0x04a0e948) 22 0x0042f4e4 in alan_wakes_american_nightmare (+0x2f4e3) (0x04a0e990) 23 0x0042fb0b in alan_wakes_american_nightmare (+0x2fb0a) (0x04a0e9c4) 24 0x006eded0 in alan_wakes_american_nightmare (+0x2edecf) (0x04a0e9f4) 25 0x00d99f02 in rl_w32_f (+0x59f01) (0x04a0ea08) 26 0x7bc7d8ac call_thread_func_wrapper+0xb() in ntdll (0x04a0ea18) 27 0x7bc80669 call_thread_func+0xa8(entry=0xd42b8a, arg=0x399d2a0, frame=0x4a0eb18) [/wine/dlls/ntdll/signal_i386.c:2759] in ntdll (0x04a0eaf8) 28 0x7bc7d88a call_thread_entry_point+0x11() in ntdll (0x04a0eb18) 29 0x7bc88073 start_thread+0xa2(info=0x7ffd0fb8) [/wine/dlls/ntdll/thread.c:453] in ntdll (0x04a0f368) PulseAudio 8.0 -- 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 6

[Bug 54341] New: dotnet-dump data collection or some other backtrace for dotnet applications?
by WineHQ Bugzilla March 18, 2023

March 18, 2023

https://bugs.winehq.org/show_bug.cgi?id=54341 Bug ID: 54341 Summary: dotnet-dump data collection or some other backtrace for dotnet applications? Product: Wine Version: 7.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mjevans1983(a)gmail.com Distribution: --- Created attachment 73910 --> https://bugs.winehq.org/attachment.cgi?id=73910 winedbg.exe dump during the livelock I'm trying to figure out why a game (Cosmoteer again) freezes when multi-threading is enabled. The current work around is to run it in 'single core' ( --cores 1 ) mode, but obviously the performance is quite inferior for an application intended to run on multiple cores. On my system when it's briefly working it uses between 300 and 500% of a core (so 3-5 physical cores on a 4c8t system). I need to collect more data to isolate if it's an issue with the game or with wine, and I don't even know where to begin looking for Wine data since I can't get a backtrace from any tools. gdb doesn't know about applications that run through wine. winedbg doesn't appear to understand dotnet managed applications (attachment) I tried to run dotnet-dump but the tool installed in Linux doesn't locate any applications that it can interact with, while the 64-bit (matches the program) version of the tool inside wine appears to want a full dotnet install. https://github.com/dotnet/diagnostics/blob/main/documentation/single-file-t… So much for a single file tool ~.~ Is there some way I could collect more data without help from the program's creator? I've already suggested they please trap SIGTERM, SIGINT, SIGQUIT, and SIGHUP but I don't even know if that will work for an application using wine. https://steamcommunity.com/app/799600/discussions/1/3762228045904230736/ -- 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 7

[Bug 52538] New: Regression: Yamaha Expansion Manager crashes
by WineHQ Bugzilla March 18, 2023

March 18, 2023

https://bugs.winehq.org/show_bug.cgi?id=52538 Bug ID: 52538 Summary: Regression: Yamaha Expansion Manager crashes Product: Wine Version: 7.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: joseskvolpe(a)gmail.com Distribution: --- I found out this application has got a regression on a older regression Based on the test results history, it has got a platinum rating in Wine 6.0, but the application crashes on the start-up on Wine 7.1 so it's rating is now Garbage. I tested it on a self-compiled Wine 6.0.2, the application works well on a WoW64 prefix all-trial, but crashes on a 32-Bits prefix. I've downloaded newer Wine binaries from Arch's packages archive (https://archive.archlinux.org/packages/w/wine/) and tested the application multiple-times, it works until Wine 6.9, older versions works but crashes sometimes, so i've to try it 5 times to be sure it's not working. The application won't work on Wine 6.9 no matter how much time you try it. But i'm afraid i couldn't find the bad commit, there's something very weird on this issue, let me explain. That was my methodology for regression testing it: 1 - Erase the wineprefix 2 - Make the bisection (bisect start, bisect skip, bisect good or bisect bad) 3 - WoW64 Wine compile (wine-64 build, then wine-32 build) 4 - Create a new WoW64 wineprefix 5 - Try application multiple times, if it succeeds then it's bisect good, if it crashes after trying it over 5 times, then it's bisect bad However, the application could always succeed after compiling Wine before the 5th try, until the last bisection. I tried again bisecting Wine 6.9 and Wine 6.10. The application were crashing on both Wine 6.9 and Wine 6.10 from Arch's binary archive, but it could succeed if i compile them. I'd the same issue, although the application could indeed crash sometimes (wich also occurs on older Wine versions), it were always succeeding before the 5th try, so i couldn't find what was the commit that caused the regression. ¿Maybe is that a issue from who's compiling Wine for Arch? ¿Should i compile Wine 7.1 and try the application? I planned to become a maintainer for the application only to add a proper description and then leave, but now i'll stay maintaining this application for a while until we can figure it out. ¿Can you devs reproduce the crash on other distributions? Download: https://tw.yamaha.com/zh/support/updates/yem_win_v260.html SHA1: b6255d5371679554b72f29a00008578438a1bfe6 Procedure: 1 - Run "Expansion Manager.exe" -- 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 23