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

[Bug 54172] New: ddraw:ddraw1, ddraw:ddraw2, ddraw:ddraw4, ddraw:ddraw7 - test_window_position() gets the size of the wrong screen in Wine
by WineHQ Bugzilla Jan. 13, 2023

Jan. 13, 2023

https://bugs.winehq.org/show_bug.cgi?id=54172 Bug ID: 54172 Summary: ddraw:ddraw1, ddraw:ddraw2, ddraw:ddraw4, ddraw:ddraw7 - test_window_position() gets the size of the wrong screen in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- ddraw:ddraw1, ddraw:ddraw2, ddraw:ddraw4, ddraw:ddraw7 - test_window_position() gets the size of the wrong screen in Wine: ddraw1.c:14471: Test failed: Expect window rect (0,0)-(1024,768), got (0,0)-(1024,737). ddraw2.c:15385: Test failed: Expect window rect (0,0)-(1024,768), got (0,0)-(1024,737). ddraw4.c:18435: Test failed: Expect window rect (0,0)-(1024,768), got (0,0)-(1024,737). ddraw7.c:18702: Test failed: Expect window rect (0,0)-(1024,768), got (0,0)-(1024,737). See https://test.winehq.org/data/patterns.html#ddraw:ddraw1 https://test.winehq.org/data/patterns.html#ddraw:ddraw2 https://test.winehq.org/data/patterns.html#ddraw:ddraw4 https://test.winehq.org/data/patterns.html#ddraw:ddraw7 These failures never happen on debian11b which is a single-monitor configuration. $ xrandr | grep Virtual Virtual-1 connected primary 1024x768+0+0 0mm x 0mm Virtual-2 disconnected Virtual-3 disconnected Virtual-4 disconnected It also never happens on debian11 where both monitors have the same resolution: $ xrandr | grep Virtual Virtual-1 connected primary 1024x737+0+0 0mm x 0mm Virtual-2 connected 1024x737+1024+0 0mm x 0mm Virtual-3 disconnected Virtual-4 disconnected But it is systematic on the debiant VM where the two screens have different resolutions: $ xrandr | grep Virtual Virtual-1 connected primary 1024x768+0+0 0mm x 0mm Virtual-2 connected 1024x737+1024+0 0mm x 0mm Virtual-3 disconnected Virtual-4 disconnected Note: * I did not intentionally configure the two screens to have different resolutions but I did not fight it either because it's also not that uncommon in multi-monitor configurations. * The 737 pixel height is a bit weird but there is no dock. Really! I'm not sure how the X server picked these sizes. -- 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 54151] New: xactengine3_7:xact3 crashes when no speaker is connected
by WineHQ Bugzilla Jan. 13, 2023

Jan. 13, 2023

https://bugs.winehq.org/show_bug.cgi?id=54151 Bug ID: 54151 Summary: xactengine3_7:xact3 crashes when no speaker is connected Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: xactengine Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com xactengine3_7:xact3 crashes when no speaker is connected: xact3.c:209: Test failed: Cannot initialize engine, hr 0x88960001 xact3.c:215: Test failed: got hr 0x8ac70002 xact3.c:218: Test failed: got hr 0x8ac70002 xact3.c:224: Test failed: got hr 0x8ac70002 xact3.c:227: Test failed: got hr 0x8ac70002 xact3.c:235: Test failed: Cannot register notification, hr 0x8ac70002 xact3.c:243: Test failed: Cannot register notification, hr 0x8ac70002 xact3.c:249: Test failed: Cannot register notification, hr 0x8ac70002 xact3.c:259: Test failed: Cannot create a streaming wave bank, hr 0x8ac70002 xact3.c:259: this is the last test seen before the exception 0df8:xact3: unhandled exception c0000005 at 0000000000401A4C See https://test.winehq.org/data/patterns.html#xactengine3_7:xact3 Where: 0x88960001 == XAUDIO2_E_INVALID_CALL or XAUDIO20_E_XMA_DECODER_ERROR 0x8ac70002 == MAKE_HRESULT(SEVERITY_ERROR, FACILITY_XACTENGINE, XACTENGINE_E_NOTINITIALIZED) These failures only happen on w11pro64_amd and w11pro64_nv. What these have in common is that the sound is supposed to go through the graphics card's HDMI / DisplayPort connection. However those go to a dummy plug which emulates a screen... but not speakers. This causes Windows to disable the sound volume widget since it cannot detect any form of speaker. I suspect, but that may require confirmation, that this causes xact to refuse to initialize. More notes: * My fgtb-w10pro64-rx550 VM has the same audio-through-HDMI configuration but is connected to my real screen which does have speakers. So sound is not 'disabled'. * QEmu emulates an ich9 sound card in the regular w11pro64 test configuration and Spice (the virtual KVM) provides the remote speakers. So again sound is not 'disabled' (and I always lower the default volume in the VMs so I don't get deafened by the Windows boot sound). * Before 2022-12-09 the w11pro64 VM was missing many DirectX dlls which caused this test to be entirely skipped. This is why it did not crash on these test configurations before then. -- 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 5

[Bug 52152] New: comctl32:edit gets unexpected heights in test_text_position_style() on Windows 10 1809+
by WineHQ Bugzilla Jan. 13, 2023

Jan. 13, 2023

https://bugs.winehq.org/show_bug.cgi?id=52152 Bug ID: 52152 Summary: comctl32:edit gets unexpected heights in test_text_position_style() on Windows 10 1809+ Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com comctl32:edit gets unexpected heights in test_text_position_style() on Windows 10 1809+: edit.c:2090: Test failed: wrong height expected 16 got 17 edit.c:2091: Test failed: wrong height expected 16 got 18 edit.c:2092: Test failed: wrong height expected 16 got 26 edit.c:2100: Test failed: wrong height expected 16 got 17 edit.c:2101: Test failed: wrong height expected 16 got 19 edit.c:2103: Test failed: wrong height expected 16 got 18 edit.c:2111: Test failed: wrong height expected 16 got 17 edit.c:2113: Test failed: wrong height expected 16 got 24 edit.c:2121: Test failed: wrong height expected 16 got 17 edit.c:2123: Test failed: wrong height expected 16 got 24 edit.c:2134: Test failed: wrong height expected 16 got 17 edit.c:2135: Test failed: wrong height expected 16 got 18 edit.c:2136: Test failed: wrong height expected 16 got 26 edit.c:2144: Test failed: wrong height expected 16 got 17 edit.c:2145: Test failed: wrong height expected 16 got 19 edit.c:2147: Test failed: wrong height expected 16 got 18 edit.c:2155: Test failed: wrong height expected 16 got 17 edit.c:2157: Test failed: wrong height expected 16 got 24 edit.c:2165: Test failed: wrong height expected 16 got 17 edit.c:2167: Test failed: wrong height expected 16 got 24 https://test.winehq.org/data/patterns.html#comctl32:edit The set of bad heights is exactly the same on all failing configurations, regardless of the Windows version, graphics card or locale. So the failure really is related to a change that happened between 1709 and 1809. -- 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 51420] New: likely regression: heavy lag to the point of brokenness running anything in wine. 158:err:ntdll:RtlpWaitForCriticalSection section 7BC61360 "dlls/ntdll/loader.c: loader_section" wait timed out in thread 0158, blocked by 0144, retrying (60 sec)
by WineHQ Bugzilla Jan. 13, 2023

Jan. 13, 2023

https://bugs.winehq.org/show_bug.cgi?id=51420 Bug ID: 51420 Summary: likely regression: heavy lag to the point of brokenness running anything in wine. 158:err:ntdll:RtlpWaitForCriticalSection section 7BC61360 "dlls/ntdll/loader.c: loader_section" wait timed out in thread 0158, blocked by 0144, retrying (60 sec) Product: Wine Version: 6.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mouse(a)dayrep.com Distribution: --- Debian bullseye using the winehq packages proprietary nvidia driver from Debian non-free Tested versions that work fine as before: 6.0.1, 6.10 Broken versions: 6.11, 6.12, staging-6.12 Running any program in wine, included or otherwise, is causing extremely poor systems performance and is very slow. As in you can see the mouse cursor move in steps and lagging behind inputs, or the file selection window of the wine uninstaller takes seconds to display the icons for folder contents and loads the one by one. This stops as soon as the wine process is killed again. Full difference in wine log between 6.10 (works fine) and 6.12 (bugged) reproduced below: 0158:err:ntdll:RtlpWaitForCriticalSection section 7BC61360 "dlls/ntdll/loader.c: loader_section" wait timed out in thread 0158, blocked by 0144, retrying (60 sec) 0168:err:ntdll:RtlpWaitForCriticalSection section 7BC61360 "dlls/ntdll/loader.c: loader_section" wait timed out in thread 0168, blocked by 0144, retrying (60 sec) 0180:err:ntdll:RtlpWaitForCriticalSection section 7BC61360 "dlls/ntdll/loader.c: loader_section" wait timed out in thread 0180, blocked by 0144, retrying (60 sec) 0188:err:ntdll:RtlpWaitForCriticalSection section 7BC61360 "dlls/ntdll/loader.c: loader_section" wait timed out in thread 0188, blocked by 0144, retrying (60 sec) 0198:err:ntdll:RtlpWaitForCriticalSection section 7BC61360 "dlls/ntdll/loader.c: loader_section" wait timed out in thread 0198, blocked by 0144, retrying (60 sec) 0208:fixme:console:default_ctrl_handler Terminating process 20 on event 0 [Also: What is an ergonomic way to downgrade to a previous winehq-devel and dependent wine package versions on Debian? Because synaptic in general and in this specific (force version) case handles amd64 packages with i386 dependencies very poorly. Basically what is the apt command line to fetch and install winehq-devel, wine-devel, wine-devel-amd64 and wine-devel-i386 all in the same older version number? like 6.9 for example.] -- 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 67

[Bug 51301] New: Right click inside Roblox Client window causes the cursor to freeze
by WineHQ Bugzilla Jan. 13, 2023

Jan. 13, 2023

https://bugs.winehq.org/show_bug.cgi?id=51301 Bug ID: 51301 Summary: Right click inside Roblox Client window causes the cursor to freeze Product: Wine Version: 6.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gnuwho.gnuwho(a)gmail.com Distribution: --- Platform: Arch Linux (GNOME) x86-64 In the Roblox Client (working as of Wine 6.11), if you join a game and press and hold right click (done in order to move the camera around), the cursor freezes in place and cannot get unstuck. As far as I know, this affects all users that try to run the Roblox Player using Wine 6.11 or later. Note: Roblox was installed using the Grapejuice wrapper (https://gitlab.com/brinkervii/grapejuice) -- 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 24

[Bug 48553] New: Catia (CAD software) refuse to run installation on newest wine (<=4.18)
by WineHQ Bugzilla Jan. 13, 2023

Jan. 13, 2023

https://bugs.winehq.org/show_bug.cgi?id=48553 Bug ID: 48553 Summary: Catia (CAD software) refuse to run installation on newest wine (<=4.18) Product: Wine Version: 4.18 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tomo.hornacek(a)gmail.com Distribution: --- Created attachment 66366 --> https://bugs.winehq.org/attachment.cgi?id=66366 This is output of wine to console on my system. After running setup.exe of catia V5r19 or V5r20. Wine display "setup: Problem with VC8 Runtime. Please try to restart your computer or contact customer service" On wine 4.17 and lower installation's runs just 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 11

[Bug 53583] New: the Reimplemented FindNLSStringEx has bug
by WineHQ Bugzilla Jan. 13, 2023

Jan. 13, 2023

https://bugs.winehq.org/show_bug.cgi?id=53583 Bug ID: 53583 Summary: the Reimplemented FindNLSStringEx has bug Product: Wine Version: 7.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: 398063392(a)qq.com Distribution: --- Created attachment 72966 --> https://bugs.winehq.org/attachment.cgi?id=72966 the code project #include "stdafx.h" #include <windows.h> #include <assert.h> int _tmain(int argc, _TCHAR* argv[]) { DWORD flags = NORM_LINGUISTIC_CASING|FIND_STARTSWITH; int nResult = FindNLSStringEx(L"en-US",flags,L"x-oss-security-token",0xe,L"x-oss-",0x6,0,0,0,0); printf("FindNLSStringEx Result = %d \r\n", nResult); assert(nResult == 0); return 0; } the code in Windows print: "FindNLSStringEx Result = 0" but in Wine print: "FindNLSStringEx Result = -1 Assertion failed: nResult == 0, file .\FindNLSStringEx.cpp, line 13 " FindNLSStringEx is very important for C#, because it is the basis of the String class, StartsWith, EndsWith, IndexOf all rely on it to achieve. So hopefully you guys can test it rigorously, thanks a lot. In addition, I found a lot of bugs and fixed them myself, how can I submit these PRs? -- 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 10

[Bug 52749] New: winetricks dotnet35sp1: printfilterpipelinesvc.exe crashes in background
by WineHQ Bugzilla Jan. 13, 2023

Jan. 13, 2023

https://bugs.winehq.org/show_bug.cgi?id=52749 Bug ID: 52749 Summary: winetricks dotnet35sp1: printfilterpipelinesvc.exe crashes in background Product: Wine Version: 6.18 Hardware: x86-64 OS: Linux Status: NEW Keywords: dotnet, download, regression Severity: normal Priority: P2 Component: spooler Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com CC: jacek(a)codeweavers.com Regression SHA1: 68feb134af0538d7fc589c2ddb6403de9cea1055 Distribution: --- Created attachment 72119 --> https://bugs.winehq.org/attachment.cgi?id=72119 backtrace Regression introduced by: 68feb134af0538d7fc589c2ddb6403de9cea1055 is the first bad commit commit 68feb134af0538d7fc589c2ddb6403de9cea1055 Author: Jacek Caban <jacek(a)codeweavers.com> Date: Mon Sep 13 13:50:08 2021 +0200 winspool: Use configuration file for DocumentPropertiesW. 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> (note: may require a printer to be configured, didn't try disabling it/cups). After this commit, dotnet35sp1 (possibly more, this is the first place I noticed) have a crash in the background, in printfilterpipelinesvc.exe. It doesn't print to the console, even if the crash dialog is disabled. Viewing via dialog shows it, though: Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x00000000). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b EIP:00000000 ESP:0021fb5c EBP:0021fbb8 EFLAGS:00010206( R- -- I - -P- ) EAX:00000000 EBX:01001ebc ECX:0021f8f0 EDX:00260f30 ESI:00000000 EDI:00000000 Stack dump: 0x0021fb5c: 663cc95f 00000000 01001ebc 00000000 0x0021fb6c: 00000000 00000000 00000004 0021fbb8 0x0021fb7c: 7bc27c0a 80000001 0021fba0 00000074 0x0021fb8c: 663df3fa 00250000 00000000 00000000 0x0021fb9c: 00260f30 00000000 014b61e0 0021fbd0 0x0021fbac: 0021fca8 00000074 0021fc0c 0021fc28 Backtrace: =>0 0x00000000 (0x0021fbb8) 1 0x663d5274 AddPrinterW+0x714(pName=<internal error>, Level=<internal error>, pPrinter=<internal error>) [Z:\home\austin\wine-git\dlls\winspool.drv\info.c:517] in winspool (0x0021fc28) 2 0x0101c6f9 in printfilterpipelinesvc (+0x1c6f9) (0x0021fd6c) 3 0x0101dd9f in printfilterpipelinesvc (+0x1dd9f) (0x0021fda0) 4 0x0101c4ad in printfilterpipelinesvc (+0x1c4ad) (0x0021fdc8) 5 0x0101c51d in printfilterpipelinesvc (+0x1c51d) (0x0021fde4) 6 0x0101c5df in printfilterpipelinesvc (+0x1c5df) (0x0021fe08) 7 0x0101e998 in printfilterpipelinesvc (+0x1e998) (0x0021ff30) 8 0x7b62d2a0 WriteTapemark+0x100(device=7FFD1000, type=<is not available>, count=<is not available>, immediate=<is not available>) [Z:\home\austin\wine-git\dlls\kernel32\tape.c:317] in ker nel32 (0x0021ff48) 9 0x7bc58147 RtlWakeConditionVariable+0x57(variable=7B62D290) [Z:\home\austin\wine-git\dlls\ntdll\sync.c:757] in ntdll (0x0021ff5c) 10 0x7bc58800 RtlCreateUserThread(entry=0101E813, arg=7FFD1000) [Z:\home\austin\wine-git\dlls\ntdll\thread.c:261] in ntdll (0x0021ffec) 0x00000000: -- no code accessible -- The issue persists in wine-7.5. -- 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 52557] New: GetNetworkParams loops forever on musl
by WineHQ Bugzilla Jan. 13, 2023

Jan. 13, 2023

https://bugs.winehq.org/show_bug.cgi?id=52557 Bug ID: 52557 Summary: GetNetworkParams loops forever on musl Product: Wine Version: 7.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: iphlpapi Assignee: wine-bugs(a)winehq.org Reporter: me(a)atiltedtree.dev Distribution: --- On musl, res_getservers does not exist and dnsapi/resolv_get_serverlist will fall back to res_state.nsaddr_list. But musl also does not set res_state.nsaddr_list causing dnsapi/resolv_get_serverlist to always return DNS_ERROR_NO_DNS_SERVERS. iphlpapi/get_dns_server_list will call DnsQueryConfig( DnsConfigDnsServerList, ...), which calls dnsapi/resolv_get_serverlist, until it does not return an error, but on musl it will always return an error causing iphlpapi/get_dns_server_list to loop infinitely. This means that any application that calls iphlpapi.GetNetworkParams or iphlpapi.GetPerAdapterInfo will loop infinitely, if wine was built on musl. -- 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 27244] New: Wiggles: Indeo
by wine-bugs＠winehq.org Jan. 13, 2023

Jan. 13, 2023

http://bugs.winehq.org/show_bug.cgi?id=27244 Summary: Wiggles: Indeo Product: Wine Version: 1.3.19 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: lukasz.wojnilowicz(a)gmail.com Created an attachment (id=34827) --> (http://bugs.winehq.org/attachment.cgi?id=34827) Terminal output on Wine 1.3.19 Steps to reproduce: 1) remove ~/.wine 2) winetricks gecko icodecs 3) install Wiggles 4) patch Wiggles with Wiggles_Patch_1_0_844.exe 4) wine Wiggles.exe Behaviour: I get only audio from intro video. Expected behaviour: I should get audio and video from intro video. Additional info: I can play video in Smplayer. Here I give info about video: Resolution: 640 x 360 Format: IV32 Bitrate: 4373 kbps FPS: 24.000 Decoder: ffindeo3 Size: 96,2 MB -- 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 23