December 2021 - wine-bugs

[Bug 52061] New: dinput HID joystick sends unnecessary effect update reports.
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=52061 Bug ID: 52061 Summary: dinput HID joystick sends unnecessary effect update reports. Product: Wine Version: 6.21 Hardware: x86-64 OS: Linux Status: NEW Severity: enhancement Priority: P2 Component: directx-dinput Assignee: wine-bugs(a)winehq.org Reporter: rbernon(a)codeweavers.com Distribution: --- Split from https://bugs.winehq.org/show_bug.cgi?id=51873, native implementation only sends effect parameter update reports for the effect parameter blocks that have been modified. Current implementation sends all parameter blocks updates every time an effect is modified. This causes unnecessary traffic and possibly unexpected behavior. -- 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 51996] New: aarch64: NtGetContextThread/NtSetContextThread on another thread ignores FPU state due to buggy SIGUSR1 handler
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51996 Bug ID: 51996 Summary: aarch64: NtGetContextThread/NtSetContextThread on another thread ignores FPU state due to buggy SIGUSR1 handler Product: Wine Version: 6.21 Hardware: aarch64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: jinoh.kang.kr(a)gmail.com Regression SHA1: 07f37f21377e930aefeb1fef3ab9c3cf9daee84f Distribution: --- Created attachment 70987 --> https://bugs.winehq.org/attachment.cgi?id=70987 Test program reproducing the behaviour Compiled with -O2, the attached test program's output should be: value = 2.0 When the actual output is: value = -1.0 This is due to NtGetContextThread/NtSetContextThread not being able to save/restore FP registers, since save_context()/restore_context() ignores them. The bug can be traced back to commit 07f37f21377 (ntdll: Add support for saving/restoring FPU state on ARM64., 2019-08-13), which implements save_fpu()/restore_fpu() but does not make use of them in save_context()/restore_context(). -- 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 51993] New: Ashlar Vellum/DrawingBoard 1.00 redraws incorrectly tooltip bar
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51993 Bug ID: 51993 Summary: Ashlar Vellum/DrawingBoard 1.00 redraws incorrectly tooltip bar Product: Wine Version: 6.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: rpisl(a)seznam.cz Distribution: --- Created attachment 70984 --> https://bugs.winehq.org/attachment.cgi?id=70984 Screenshot Ashlar Vellum/DrawingBoard 1.00 redraws incorrectly tooltip bar. This is a regression that started with cc7e7002ef8f92f47fe047d598dce057fcc2885b which caused the bar to disappear completely. From c129d13cbd49417078878573bd5f34a0f8f7410e the program started crashing on startup and that is then fixed with 5c8ac458bb72518a1c6f2ed05c783cee6c4a3b82. Since this commit, the tooltip bar is visible again but it seems that the background is not cleared properly. Version 1.01 is avalable from https://vetusware.com/download/Ashlar%20Vellum%201.01%20for%20Windows (needs registration) but this version crashes on start. I'll open a separate bug report. -- 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 51989] New: pen-related tests (gdiplus:graphics and gdiplus:graphicspath) fail on latest Windows 10
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51989 Bug ID: 51989 Summary: pen-related tests (gdiplus:graphics and gdiplus:graphicspath) fail on latest Windows 10 Product: Wine Version: 6.17 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: gdiplus Assignee: wine-bugs(a)winehq.org Reporter: madewokherd(a)gmail.com Distribution: --- We had some new test failures appear in Windows 10 on November 2. https://test.winehq.org/data/20f1a677b664b3d0d3dc038ffb9ab4f4e4aa6274/win21… https://test.winehq.org/data/20f1a677b664b3d0d3dc038ffb9ab4f4e4aa6274/win21… It appears that Pen objects with a width of 0.0 and a unit of UnitPixel now draw with 1.0 width. Previously, they did not draw. Pen objects with UnitWorld would always draw with a minimum width of 1.0, so possibly this brings other units' behavior in line with UnitWorld. The C# and C++ wrappers only allow creating Pen objects with UnitWorld, other units can only be used through the C API. We also had the following Mono tests start failing around the same time: MonoTests.System.Drawing.PenTest:Constructor_Brush_Float_Negative MonoTests.System.Drawing.PenTest:Constructor_Brush_Float_Zero MonoTests.System.Drawing.PenTest:Constructor_Color_Float_Negative MonoTests.System.Drawing.PenTest:Constructor_Color_Float_Zero MonoTests.System.Drawing.PenTest:Width In these cases, the test creates a UnitWorld Pen with width < 1.0 and expects to get the same width back. Instead, current native gdiplus reports a width of 1.0. I'm not sure whether we should update to this new behavior. It seems likely to cause a regression if it applies to other units (a half-pixel Pen doesn't make much sense, but half-inch Pen 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 12

[Bug 47843] New: [Rockstar Game Launcher]Unable to download a game completly
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=47843 Bug ID: 47843 Summary: [Rockstar Game Launcher]Unable to download a game completly Product: Wine Version: 4.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: bcrypt Assignee: wine-bugs(a)winehq.org Reporter: berillions(a)gmail.com Distribution: --- Created attachment 65348 --> https://bugs.winehq.org/attachment.cgi?id=65348 Download stop after a while Hello, The new Rockstar Games Launcher can start to download a game but after a while, the downloading stop without reasons. In fact, the data value does not increase while the speed download change and is not at zero (see the screenshot) It seems that no more data are downloaded. Each time i close and launch the launcher, the download starts from zero. In the output log, there are some lines about bcrypt algorythm not implemented : "002a:fixme:bcrypt:BCryptOpenAlgorithmProvider algorithm L"DH" not supported" Or others lines like this (i don't know if it's important) : 0035:fixme:bcrypt:BCryptGenRandom ignoring selected algorithm I add the +bcrypt log too. -- 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 16

[Bug 46017] New: Layers of Fear areas are almost entirely black rendered
by wine-bugs＠winehq.org 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=46017 Bug ID: 46017 Summary: Layers of Fear areas are almost entirely black rendered Product: Wine Version: 3.18 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- Created attachment 62591 --> https://bugs.winehq.org/attachment.cgi?id=62591 screenshot Main hall. err:d3d:wined3d_debug_callback 0x937c010: "GL_INVALID_FRAMEBUFFER_OPERATION error generated. Operation is not valid because a bound framebuffer is not framebuffer complete.". fixme:d3d:context_check_fbo_status FBO status GL_FRAMEBUFFER_INCOMPLETE_LAYER_TARGETS (0x8da8). fixme:d3d:context_dump_fbo_attachment GL_DEPTH_ATTACHMENT: 2d texture 1116, 128x128, 0 samples, format 0x81a5. fixme:d3d:context_dump_fbo_attachment GL_STENCIL_ATTACHMENT: NONE. fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT0: 2d-array texture 1112, 128x128, 0 samples, format 0x822e. fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT1: NONE. fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT2: NONE. fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT3: NONE. fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT4: NONE. fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT5: NONE. fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT6: NONE. fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT7: NONE. wine-3.18-114-g417e94f199 -- 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 52067] New: ntdll MEM_DECOMMIT change breaks d3d10_1:d3d10_1, d3d8:device, d3d8:visual, d3d9:device, d3d9:visual, ddraw:ddraw1, ddraw:dsurface and dxgi:dxgi
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=52067 Bug ID: 52067 Summary: ntdll MEM_DECOMMIT change breaks d3d10_1:d3d10_1, d3d8:device, d3d8:visual, d3d9:device, d3d9:visual, ddraw:ddraw1, ddraw:dsurface and dxgi:dxgi Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- d3d10_1:d3d10_1, d3d8:device, d3d8:visual, d3d9:device, d3d9:visual, ddraw:ddraw1, ddraw:dsurface and dxgi:dxgi started crashing on 2021-11-19 on all Linux platforms (QEmu, cw-gtx560, cw-rx460, fg-deb64). For instance in d3d10_1:d3d10_1: Unhandled exception: page fault on read access to 0x013b002c in 32-bit code (0x7e6fe984). [...] Backtrace: =>0 0x7e6fe984 heap_free+0x3(mem=<internal error>) [Z:\home\winetest\winetest\src\include\wine\heap.h:46] in wined3d (0x0105fe48) 1 0x7e6fe984 wined3d_resource_free_sysmem+0x14(resource=0045D3C0) [Z:\home\winetest\winetest\src\dlls\wined3d\resource.c:369] in wined3d (0x0105fe48) 2 0x7e737e1e wined3d_texture_evict_sysmem+0xba(texture=<internal error>) [Z:\home\winetest\winetest\src\dlls\wined3d\texture.c:688] in wined3d (0x0105fe88) https://test.winehq.org/data/patterns.html#d3d10_1:d3d10_1 And in ddraw:dsurface: Unhandled exception: assertion failed in 32-bit code (0xf7fc3559). [...] Backtrace: =>0 0xf7fc3559 __kernel_vsyscall+0x9() in [vdso].so (0x0031e7ec) 1 0xf7d8fe02 gettext+0x73f2() in libc.so.6 (0x0031e7ec) 2 0xf7d78306 GLIBC_2+0x1d306() in libc.so.6 (0xf7f40000) 3 0xf7d781d1 GLIBC_2+0x1d1d1() in libc.so.6 (0xf7f40c80) 4 0xf7d87e29 __assert_fail+0x39() in libc.so.6 (0x7e3ef0f0) 5 0x7dfa6c69 XSetArcMode+0x1cef9() in libx11.so.6 (0x7e3ef0f0) 6 0x7def75fc XRenderCompositeString16+0x14ec() in libxrender.so.1 (0x7e3ef0f0) 7 0x7e16a483 get_xrender_picture+0x43(dev=005BF998, clip_rgn=00000000, clip_rect=0031F73C) [Z:\home\winetest\winetest\src\dlls\winex11.drv\xrender.c:492] in winex11 (0x0031eb98) 8 0x7e16caed xrender_put_image+0x1ad(src_pict=0x1000071, mask_pict=0, clip=<is not available>, dst_format=7E3F28C0, physdev=005BF998, drawable=0, src=0031F6E8, dst=0031F71C, use_repeat=0, src_pixmap=<has been optimized away by compiler>) [Z:\home\winetest\winetest\src\dlls\winex11.drv\xrender.c:1702] in winex11 (0x0031ebd8) 9 0x7e16ce31 xrenderdrv_PutImage+0x331(dev=<couldn't compute location>, clip=<couldn't compute location>, info=<couldn't compute location>, bits=<couldn't compute location>, src=<couldn't compute location>, dst=<couldn't compute location>, rop=<couldn't compute location>) [Z:\home\winetest\winetest\src\dlls\winex11.drv\xrender.c:1840] in winex11 (0x0031ec78) 10 0x7e9541d1 nulldrv_StretchBlt+0x141(dst_dev=<couldn't compute location>, dst=<couldn't compute location>, src_dev=<couldn't compute location>, src=<couldn't compute location>, rop=<couldn't compute location>) [Z:\home\winetest\winetest\src\dlls\win32u\bitblt.c:295] in win32u.so (0x0031f558) https://test.winehq.org/data/patterns.html#ddraw:dsurface See also the corresponding failure patterns for more complete backtraces and also for the crashes in the other tests. A bisect shows that the crashes started with the commit below. With luck that means a single patch will fix all 8 tests; otherwise this commit may just have revealed preexisting issues and there is now 8 separate bugs to fix (and then this bug should be split): commit 7d2a7b94aad8a776a2ee3031a18bb3b53d5925cd Author: Alexandre Julliard <julliard(a)winehq.org> Date: Fri Nov 19 11:04:30 2021 +0100 ntdll: Fix handling of zero size with MEM_DECOMMIT. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=52023 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 6

[Bug 52133] New: winhttp/wininet should not query mDNS for proxy auto-detection
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=52133 Bug ID: 52133 Summary: winhttp/wininet should not query mDNS for proxy auto-detection Product: Wine Version: 6.22 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: winhttp Assignee: wine-bugs(a)winehq.org Reporter: bshanks(a)codeweavers.com At least on macOS, the default hostname is something like "XXs-MacBook-Pro.local". Wine then (correctly) reads the domain name as "local". When winhttp or wininet tries to use DNS proxy auto-detection (i.e. WinHttpDetectAutoProxyConfigUrl() with the WINHTTP_AUTO_DETECT_TYPE_DNS_A option), they try to resolve "wpad.local". On macOS this hangs for 5 seconds before failing, causing a 10-minute long hang while launching Halo: MCC. This also opens a security hole by allowing anyone on the local network to advertise an HTTP proxy that will be used automatically by other hosts on the network. Microsoft has disabled link-local name resolution (i.e. NetBIOS, LLMNR, mDNS) by default for WPAD for years: https://bugs.chromium.org/p/chromium/issues/detail?id=1176970#c29 This is done on Windows with the undocumented AI_DNS_ONLY flag to getaddrinfo(), unfortunately there is no equivalent UNIX flag. Adding a special-case for ".local" domains would at least prevent the most common case of mDNS resolution. -- 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 52103] New: Crazy Stone has been working on Wine for years but now crashes following update
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=52103 Bug ID: 52103 Summary: Crazy Stone has been working on Wine for years but now crashes following update Product: Wine Version: 6.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gerry(a)gavigan.me.uk Distribution: --- Created attachment 71125 --> https://bugs.winehq.org/attachment.cgi?id=71125 backtrace generated by Wine After splash screen Crazy Stone crashes. I have been using Crazy Stone under Wine for about five years without problem. Today, on Tumbleweed, after an update. -- 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 44

[Bug 52093] New: malloc() after installing Insta360 pro stitcher (incl. wine config)
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=52093 Bug ID: 52093 Summary: malloc() after installing Insta360 pro stitcher (incl. wine config) Product: Wine Version: 6.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: wwjdtd(a)gmail.com Distribution: --- To reproduce: 1. Download Insta360 STITCHER from here: https://www.insta360.com/download/insta360-pro2 Note: You will want to use the href link since it will otherwise ask for a serial number. 2. Run Installer 3. Close all wine programs 4. Try to run anything in wine or the wine config tool (or any other built-in). You will receive the following: ``` malloc(): invalid size (unsorted) Aborted (core dumped) ``` Copying the program files out and into a fresh wineprefix allows the program to run properly and does not corrupt the new prefix. All testing was done in bottles (to prevent stuff breaking from misconfiguration on my part) with `winehq-devel`. Versions effected is everything from somewhere above 6.0 to 6.22, this also means it's some form of regression since it didn't do this previously. Forum post: https://forum.winehq.org/viewtopic.php?f=8&t=35914&p=135171#p135140 -- 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 52072] New: winmm:mci fails in wow64 Wine
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=52072 Bug ID: 52072 Summary: winmm:mci fails in wow64 Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: winmm&mci Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- winmm:mci started failing in wow64 Wine on 2021-11-11. It now has 51 failures: mci.c:248: Test failed: status 4(mode): MCIERR_UNSUPPORTED_FUNCTION mci.c:328: Test failed: status mode: MCIERR_UNSUPPORTED_FUNCTION mci.c:656: Test marked todo: mci info new file returned 0=NOERROR mci.c:660: Test marked todo: status x length initial: MCIERR_UNSUPPORTED_FUNCTION mci.c:665: Test failed: mci status samplespersec returned MCIERR_UNSUPPORTED_FUNCTION mci.c:732: Test failed: mci status position returned MCIERR_UNSUPPORTED_FUNCTION mci.c:781: Test failed: mci status length returned MCIERR_UNSUPPORTED_FUNCTION mci.c:812: Test failed: mci status length returned MCIERR_UNSUPPORTED_FUNCTION mci.c:827: Test failed: mci status mode returned MCIERR_UNSUPPORTED_FUNCTION mci.c:848: Test failed: mci status mode returned MCIERR_UNSUPPORTED_FUNCTION mci.c:849: Test failed: mci status mode: after play from 0 to 0 mci.c:860: Test failed: mci status position returned MCIERR_UNSUPPORTED_FUNCTION mci.c:903: Test failed: mci status position notify returned MCIERR_UNSUPPORTED_FUNCTION mci.c:906: Test failed: Expect message 0001 from status position mci.c:909: Test failed: mci status mode returned MCIERR_UNSUPPORTED_FUNCTION mci.c:910: Test failed: mci status mode: mci.c:915: Test marked todo: Expect message 0001 from play to 250 wait notify mci.c:955: Test failed: mci status mode returned MCIERR_UNSUPPORTED_FUNCTION mci.c:956: Test failed: mci status mode: mci.c:974: Test failed: mci status position returned MCIERR_UNSUPPORTED_FUNCTION mci.c:975: position after Sleep: ms [...] https://test.winehq.org/data/patterns.html#winmm:mci Note that besides the test failures the "mci status mode: " and "position after Sleep: ms" messages are suspicious. All four Linux test machines are impacted by this: the failure test pattern makes it obvious for cw-gtx560, cw-rx460 and the TestBot's debiant2 VM. fg-deb64 is impacted as well but it is masked by the preexisting timeout. Strangely a bisect shows that these failures started with this commit: commit 7c5761ed40f0b8cead7fa837b745b687d5df67d8 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Thu Nov 11 16:21:00 2021 +0100 wrc: Ignore the target option. Nothing in resource files depends on the pointer size. 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 6

[Bug 52068] New: hid:device times out randomly in test_get_input_report()
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=52068 Bug ID: 52068 Summary: hid:device times out randomly in test_get_input_report() Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: hid Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- hid:device times out randomly (>10% of the time) in test_get_input_report(): device.c:406: HidD_GetInputRpeort tests on device :L"Wine HID mouse" hid:device:05cc done (258) in 120s https://test.winehq.org/data/patterns.html#hid:device So far this only happened in the pure 32-bit builds but it does impact various machines (cw-gtx560, cw-rx460, some debiant2 configurations and fg-deb64). A bisect shows that the timeouts started with this commit: commit fca0f18d0857d6aee67c6ef652c31c6810292270 Author: Rémi Bernon <rbernon(a)codeweavers.com> Date: Fri Nov 19 09:39:39 2021 +0100 winebus.sys: Avoid unnecessary scaling of effect parameter values. Signed-off-by: Rémi Bernon <rbernon(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 3

[Bug 52023] New: VirtualFree returning error when it should not
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=52023 Bug ID: 52023 Summary: VirtualFree returning error when it should not Product: Wine Version: 6.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: elpochodelagente(a)gmail.com Distribution: --- Created attachment 71022 --> https://bugs.winehq.org/attachment.cgi?id=71022 test case source and exe I find it odd that Wine's version of VirtualFree [1] with MEM_DECOMMIT does nothing, and always returns error (STATUS_NO_MEMORY, see decommit_pages and anon_map_fixed in dlls/ntdll/unix/virtual.c). The attached test passes, (crashing) in windows but doesn't in wine: $ x86_64-w64-mingw32-gcc -o decommit.exe decommit.c Windows: $ ./decommit.exe ====== test 1 - reserve, commit, release > success! ====== test 2 - reserve, commit, decommit, attempt use > Segmentation fault Wine: $ wine decommit.exe ====== test 1 - reserve, commit, release > success! ====== test 2 - reserve, commit, decommit, attempt use > Could not decommit memory. Error code: 8 ====== [1] https://docs.microsoft.com/en-us/windows/win32/api/memoryapi/nf-memoryapi-v… -- 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 51895] New: ucrtbase:misc fma(inf, 0, 0) 'succeeds' unexpectedly on some machines
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51895 Bug ID: 51895 Summary: ucrtbase:misc fma(inf, 0, 0) 'succeeds' unexpectedly on some machines Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ucrtbase Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ucrtbase:misc fma(inf, 0, 0) 'succeeds' unexpectedly on some machines: misc.c:799: Test failed: fma(inf, 0.000000, 0.000000) got errno -1 misc.c:799: Test failed: fma(0.000000, inf, 0.000000) got errno -1 misc.c:799: Test failed: fma(inf, 1.000000, -inf) got errno -1 misc.c:799: Test failed: fma(-inf, 1.000000, inf) got errno -1 misc.c:799: Test failed: fma(1.000000, inf, -inf) got errno -1 misc.c:799: Test failed: fma(1.000000, -inf, inf) got errno -1 https://test.winehq.org/data/patterns.html#ucrtbase:misc Additional tests seem to indicate this is related to the CPU features: * The test succeeds on all TestBot VMs, and they also all return _get_FMA3_enabled() = 0. * The test fails on fgtb-w10pro64 (i7-4790K) where _get_FMA3_enabled() returns 1. * Paul Gofman reported getting this failure on a modern AMD processor where _get_FMA3_enabled() presumably returns 1 too. Yet: * The documentation says _get_FMA3_enabled() is about transcendental functions. fma() is not one of them. * _get_FMA3_enabled() is only available in 64-bit code but the failures happen on both 32- and 64-bit code. So it does look like this is related to the fma() implementation (x87/SSE2/other?) picked by the ucrtbase library as opposed to library version issues. But the details are murky and there may be some other common factor. The MSDN documentation does say that fma(inf,0,0) should return NaN, which it does. The documentation is less clear on errno which is what we test. https://docs.microsoft.com/en-us/cpp/c-runtime-library/reference/fma-fmaf-f… So maybe applications cannot rely on errno being set (particularly on modern processors) and this particular test should be removed. -- 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 51624] New: TETRIS (16bit) shows wrong background for scoreboard
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51624 Bug ID: 51624 Summary: TETRIS (16bit) shows wrong background for scoreboard Product: Wine Version: 6.14 Hardware: x86-64 OS: Linux Status: NEW Severity: trivial Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Created attachment 70480 --> https://bugs.winehq.org/attachment.cgi?id=70480 Screenshot showing the issue Follow up to bug 51570. The graphics of the game almost work now, but the scoreboard to the left has the wrong background. -- 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 32991] New: ARM port of "WabbitEMU" crashes due to unimplemented function KERNEL32.dll.RtlUnwindEx (no ntdll forward on arch=arm)
by wine-bugs＠winehq.org 03 Dec '21

03 Dec '21

http://bugs.winehq.org/show_bug.cgi?id=32991 Bug #: 32991 Summary: ARM port of "WabbitEMU" crashes due to unimplemented function KERNEL32.dll.RtlUnwindEx (no ntdll forward on arch=arm) Product: Wine Version: 1.5.24 Platform: arm OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: kernel32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Classification: Unclassified Hello folks, the ARM port of "WabbitEMU", a Texas Instruments graphing calculator emulator and dev tools crashes after clicking "Browse for a ROM image" radio button in image selection dialog. Download: http://forum.xda-developers.com/showpost.php?p=37928562 (main thread: http://forum.xda-developers.com/showthread.php?t=2092348) --- snip --- $ WINEDEBUG=+tid,+seh,+relay wine ./Wabbitemu.exe ... 0024:Call user32.GetWindowTextA(00010096,40a0ebf0,00000104) ret=00439fa5 0024:Call window proc 0x40bc5f30 (hwnd=0x10096,msg=WM_GETTEXT,wp=00000104,lp=40a0ebf0) 0024:Ret window proc 0x40bc5f30 (hwnd=0x10096,msg=WM_GETTEXT,wp=00000104,lp=40a0ebf0) retval=00000000 0024:Ret user32.GetWindowTextA() retval=00000000 ret=00439fa5 0024:Call KERNEL32.GetLastError() ret=004141cf 0024:Ret KERNEL32.GetLastError() retval=00000000 ret=004141cf 0024:trace:seh:raise_exception info[0]=0047be54 0024:trace:seh:raise_exception info[1]=0047cc8e wine: Call from 0x7bc9a630 to unimplemented function KERNEL32.dll.RtlUnwindEx, aborting 0024:trace:seh:call_stack_handlers calling handler at 0x7bcb8d88 code=80000100 flags=1 0024:Call KERNEL32.UnhandledExceptionFilter(40a0e81c) ret=7bcb8df0 --- snip --- The app is importing all win32 API by name so it's the real thing :-) +module,+imports --- snip --- ... 0009:trace:module:load_dll looking for L"KERNEL32.dll" in L"Z:\\home\\linaro\\wine-apps\\wabbitemu;.;C:\\windows\\system32;C:\\windows\\system;C:\\windows;C:\\windows\\system32;C:\\windows;C:\\windows\\system32\\wbem" 0009:trace:module:load_dll Found L"C:\\windows\\system32\\KERNEL32.dll" for L"KERNEL32.dll" at 0x7b820000, count=19 0009:warn:module:import_dll No implementation for KERNEL32.dll.RtlUnwindEx imported from L"Z:\\home\\linaro\\wine-apps\\wabbitemu\\Wabbitemu.exe", setting to 0x41820000 0009:trace:imports:import_dll --- RtlUnwindEx KERNEL32.dll.1209 = 0x41820000 0009:trace:imports:import_dll --- GetCommandLineA KERNEL32.dll.481 = 0x7b846be0 0009:trace:imports:import_dll --- RtlPcToFileHeader KERNEL32.dll.1205 = 0x7bc69188 0009:warn:module:import_dll No implementation for KERNEL32.dll.RtlLookupFunctionEntry imported from L"Z:\\home\\linaro\\wine-apps\\wabbitemu\\Wabbitemu.exe", setting to 0x41820024 0009:trace:imports:import_dll --- RtlLookupFunctionEntry KERNEL32.dll.1203 = 0x41820024 0009:trace:imports:import_dll --- GetModuleFileNameW KERNEL32.dll.634 = 0x7b86b864 ... --- snip --- It also needs KERNEL32.dll.RtlLookupFunctionEntry later. Wine forwards both to ntdll but only on arch=x86_64. It seems Windows RT exposes both API. Interestingly only the MSDN page for KERNEL32.dll.RtlLookupFunctionEntry gives a hint about this: http://msdn.microsoft.com/en-us/library/windows/desktop/ms680597%28v=vs.85%… ("ARM Definition"). Regards -- 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

[Bug 52077] New: Windows PC Health Check crashes on unimplemented function api-ms-win-core-featurestaging-l1-1-0.dll.SubscribeFeatureStateChangeNotification
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=52077 Bug ID: 52077 Summary: Windows PC Health Check crashes on unimplemented function api-ms-win-core-featurestaging-l1-1-0.dll.SubscribeFea tureStateChangeNotification Product: Wine Version: 6.22 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: api-ms-win-* Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Steps to reproduce: 1. Run `winecfg` and set the Windows version to Windows 10. 2. Run `wine msiexec /i WindowsPCHealthCheckSetup.msi` and click through the installer. 3. When the installer finishes and the app tries to start, you will see: wine: Call from 000000007B01230E to unimplemented function api-ms-win-core-featurestaging-l1-1-0.dll.SubscribeFeatureStateChangeNotification, aborting $ sha256sum WindowsPCHealthCheckSetup.msi 45c82e40ed0e27db7c55e0554512631b8f175b06d9b2d2cf58db52b18f0913fa -- 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 52075] New: dinput8:device, dinput8:dinput and dinput8:hid cannot run on Windows 7 anymore
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=52075 Bug ID: 52075 Summary: dinput8:device, dinput8:dinput and dinput8:hid cannot run on Windows 7 anymore Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-dinput Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com dinput8:device, dinput8:dinput and dinput8:hid cannot run on Windows 7 anymore because they now need GetOverlappedResultEx() which is not available. https://test.winehq.org/data/patterns.html#dinput8:device https://test.winehq.org/data/patterns.html#dinput8:dinput https://test.winehq.org/data/patterns.html#dinput8:hid Before that the tests could run on Windows 7 and even succeeded. The call to GetOverlappedResultEx() was introduced in the commit below: commit 3f110402f6a503d7c312694092e25fc48737c980 Author: Rémi Bernon <rbernon(a)codeweavers.com> Date: Wed Nov 17 11:51:48 2021 +0100 dinput8/tests: Add some HID device gain report tests. Signed-off-by: Rémi Bernon <rbernon(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 7

[Bug 51971] New: postgresql-9.3 installer needs scrrun:folder_CreateTextFile implementation
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51971 Bug ID: 51971 Summary: postgresql-9.3 installer needs scrrun:folder_CreateTextFile implementation Product: Wine Version: 6.20 Hardware: x86-64 URL: https://web.archive.org/web/20211009084355if_/https:// get.enterprisedb.com/postgresql/postgresql-9.3.25-1-wi ndows-x64.exe OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: scrrun Assignee: wine-bugs(a)winehq.org Reporter: sloper42(a)yahoo.com Distribution: --- This is followup from https://bugs.winehq.org/show_bug.cgi?id=51911 Test with postgresql-9.3 installer from [1]. It runs a script during installation similar to https://github.com/three-plus-three/tpt_env_amd64/blob/master/postgresql/in… that reports non-critical error to main install, script itself terminates. This part ' Execute a command Function DoCmd(strCmd) Dim objBatchFile Set objBatchFile = objTempFolder.CreateTextFile(strBatchFile, True) objBatchFile.WriteLine "@ECHO OFF" ... leads to fixme:scrrun:folder_CreateTextFile (0000000000075E90)->(L"rad36105.tx" ffffffff 0 000000000064EF60): stub [1] https://www.enterprisedb.com/postgresql-tutorial-resources-training?cid=340 -- 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 51557] New: GetSystemFirmwareTable fails to return SMBIOS on Apple Silicon Macs
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51557 Bug ID: 51557 Summary: GetSystemFirmwareTable fails to return SMBIOS on Apple Silicon Macs Product: Wine Version: 6.14 Hardware: aarch64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: bshanks(a)codeweavers.com The macOS implementation of GetSystemFirmwareTable() retrieves the system's actual SMBIOS table using IOKit. This fails on Apple Silicon/ARM64 Macs, since they don't have an SMBIOS table. This breaks any applications that depend on getting an SMBIOS table (like the Rockstar Games Launcher) or that look for the HKLM/Hardware/Description/System/BIOS registry keys. I think the fix will be to use the SMBIOS table creation functions used by Linux currently, with strings and data (serial number, UUID, etc) coming from IOKit if possible. -- 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 51490] New: dinput:device has a random failure in overlapped_format_tests() on Windows 8.1
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51490 Bug ID: 51490 Summary: dinput:device has a random failure in overlapped_format_tests() on Windows 8.1 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-dinput Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com dinput:device has a random failure on the w8 VM: https://test.winehq.org/data/patterns.html#dinput:device device.c:374: Test failed: keydown for D did not register It sort of looks like a race condition though the pump_messages() call should take care of that. The failing test (and all of overlapped_format_tests()) was added by the following commit. commit d10887b8f56792ebcca717ccc28a289f7bcaf107 Author: Arkadiusz Hiler <ahiler(a)codeweavers.com> AuthorDate: Thu Jul 8 13:03:21 2021 +0300 dinput: Don't add 'default value 0' entries to the data transform. This helps when dealing with the quirky c_dfDIJoystick2 format, which defines all the sliders as overlapping, i.e. rglSlider[2], rglVSlider[2], rglASlider[2] and rglFSlider[2] all share the same offset. With the Linux backends, if the device exposes enough axes (e.g. some HOTAS) we end up using rglSlider. Let's make sure we don't unnecessarily override the values there. Signed-off-by: Arkadiusz Hiler <ahiler(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 48119] New: The tests sometimes trigger "critical section is not acquired" errors
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=48119 Bug ID: 48119 Summary: The tests sometimes trigger "critical section is not acquired" errors Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- The logs of most test runs, WineTest and others, contain critical section errors complaining that the critical section was not acquired before being released. Most are caused by the following two tests: msvcp120:msvcp120 intentionally triggers one such error in test_threads__Mtx(). It's easy to identify because it follows a bunch of CreateSymbolicLinkA() fixmes: 0044:fixme:file:CreateSymbolicLinkA ("tr2_test_dir/f1_symlink" "tr2_test_dir/f1" 0): stub 0044:fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: beef 0044:err:ntdll:RtlLeaveCriticalSection section 0x622088 is not acquired ntdll:rtl intentionally triggers two such errors in test_RtlLeaveCriticalSection(). They stand alone but would typically follow a bunch of RtlGetCompressionWorkSpaceSize fixmes from previous tests: https://testbot.winehq.org/JobDetails.pl?Key=60096 0009:err:ntdll:RtlLeaveCriticalSection section 0x7bfd88 is not acquired 0009:err:ntdll:RtlLeaveCriticalSection section 0x7bfd88 is not acquired But there are other logs that contain this error with no identified source. For instance in task 60103/4/2 (wow64) which is for an unrelated patch and only runs kernel32 tests which do not normally trigger this error: https://testbot.winehq.org/JobDetails.pl?Key=60103#k402 [...] Extracting: Done (1 of 1) Running tests 003e:err:ntdll:RtlLeaveCriticalSection section 0x14c80 is not acquired 002e:fixme:console:GetConsoleProcessList ((nil),0): stub [...] Or task 59774/4/1 (win32) which only ran comctl32 tests: https://testbot.winehq.org/JobDetails.pl?Key=59774#k401 Or task 59426/1/1 (wow32) which only ran user32 tests: https://testbot.winehq.org/JobDetails.pl?Key=59426 Or task 59176/3/1 (wow32/wow64?) which, again, only ran user32 tests: https://testbot.winehq.org/JobDetails.pl?Key=59176#k301 Or task 59042/1/1 (wow32/wow64?) which, again, only ran user32 tests: https://testbot.winehq.org/JobDetails.pl?Key=59042#k101 -- 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 25193] New: Dasher does not operate correctly
by wine-bugs＠winehq.org 03 Dec '21

03 Dec '21

http://bugs.winehq.org/show_bug.cgi?id=25193 Summary: Dasher does not operate correctly Product: Wine Version: 1.3.7 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: physicspirate(a)yahoo.ca Greetings, I've attempted to run Dasher(http://appdb.winehq.org/objectManager.php?sClass=version&iId=21982&i… and it does not appear to be loading or functioning correctly. I've attached a screenshot of what happens after loading. There is a gray box up top, and it appears to be non responsive. There also seems to be some problems with the networking as I have a high speed connection, and their servers tell me my latency is too high. If I run the same program on windows it runs like a dream. -- 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 51834] New: EMF DC emits invalid EMF when calling StretchDiBits with info->bmiHeader.biSizeImage = 0
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51834 Bug ID: 51834 Summary: EMF DC emits invalid EMF when calling StretchDiBits with info->bmiHeader.biSizeImage = 0 Product: Wine Version: 6.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: jinoh.kang.kr(a)gmail.com CC: jacek(a)codeweavers.com, zzhang(a)codeweavers.com Distribution: --- BITMAPINFOHEADER allows setting biSizeImage to zero when biCompression is BI_RGB. However, the Wine EMF DC does not handle this case and takes the biSizeImage value as-is. This results in an invalid Enhanced Metafile output. -- 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 51733] New: CreateProcess does not properly set the current directory of the new process.
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51733 Bug ID: 51733 Summary: CreateProcess does not properly set the current directory of the new process. Product: Wine Version: 6.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: johnfound(a)asm32.info Distribution: --- Regression. The current directory of the new process, created with CreateProcessW is always set to "/" (z:\) instead of the current directory of the parent process. I am testing with the following call: The last version that works properly is WINE 6.12 -- 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 51415] New: Windows PC Health Check requires msvcp_win.dll
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51415 Bug ID: 51415 Summary: Windows PC Health Check requires msvcp_win.dll Product: Wine Version: 6.12 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: msvcp Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Steps to reproduce: 1. Run `winecfg` and set the Windows version to Windows 10. 2. Run `wine msiexec /i WindowsPCHealthCheckSetup.msi` and click through the installer. 3. When the installer finishes and the app tries to start, you will see: 0164:err:module:import_dll Library msvcp_win.dll (which is needed by L"C:\\users\\alex\\AppData\\Local\\PCHealthCheck\\PCHealthClient.dll") not found This DLL appears to be yet another copy of the Microsoft C++ runtime. $ sha256sum WindowsPCHealthCheckSetup.msi 45c82e40ed0e27db7c55e0554512631b8f175b06d9b2d2cf58db52b18f0913fa -- 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 51307] New: msvcp140:msvcp140 fails on msvcp140 >= 14.25
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51307 Bug ID: 51307 Summary: msvcp140:msvcp140 fails on msvcp140 >= 14.25 Product: Wine Version: 6.10 Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: msvcp Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com On cw-rx460 machines that have either Radeon 21.3.2 or 21.4.1 the 64-bit msvcp140:msvcp140 test fails: https://test.winehq.org/data/patterns.html#msvcp140:msvcp140 msvcp140.c:1257: Test failed: ret = 37, expected 39 msvcp140.c:1258: Test failed: buf = The operation completed successfully.aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaThe operation completed successfully. , expected The operation completed successfully. This is probably because the Radeon driver upgrades the 64-bit msvcp140.dll. Currently we have: Radeon msvcp140 cw-rx460-1507 19.11.3 14.14.26429.4 cw-rx460-1709 19.11.3 14.14.26429.4 cw-rx460-1809 19.11.3 14.14.26429.4 cw-rx460-1909 21.4.1 14.25.28508.3 cw-rx460-2009 21.4.1 14.25.28508.3 Also: w1064v1507 - - w1064v1607 - 14.0.23026.0 w1064v1709 - 14.0.23026.0 w1064v1809 - 14.0.23026.0 w1064v1909 - 14.0.23026.0 w10pro64 (2004) - 14.0.23026.0 w1064 (2009) - 14.0.23026.0 Note that the 14.0.23026.0 version comes from the "Visual C++ 2015 redistributables" package [1]. So all Radeon drivers actually install a newer version. But according to Chocolatey there are quite a few even newer versions, the current latest being 14.29.30037. But there does not seem to be any microsoft.com download URLs for it :-( https://community.chocolatey.org/packages/vcredist140#versionhistory [1] https://wiki.winehq.org/Wine_TestBot_VMs#msvcp140.2C_msvcr140.2C_ucrtbase -- 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 49181] New: msvcrt_test.exe: missing entry point _point_get_sbh_threshold
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=49181 Bug ID: 49181 Summary: msvcrt_test.exe: missing entry point _point_get_sbh_threshold Product: Wine Version: 5.8 Hardware: arm OS: Windows Status: NEW Keywords: download, testcase Severity: normal Priority: P2 Component: msvcrt Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Depends on: 49179 Similar to 49180, when running winetest.exe on armv7/surface rt, msvcrt_test.exe throws an error dialog: The procedure entry point _get_sbh_threshold could not be located in the dynamic link library C:\Users\User\AppData\Local\Temp\wct\msvcrt_test.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 4

[Bug 52069] New: ntdll:virtual fails in test_NtAllocateVirtualMemory() on Windows 10 1709 and older
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=52069 Bug ID: 52069 Summary: ntdll:virtual fails in test_NtAllocateVirtualMemory() on Windows 10 1709 and older 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 ntdll:virtual fails in test_NtAllocateVirtualMemory() on Windows 7 to Windows 10 1709 in both 32- and 64-bit mode: virtual.c:248: Test failed: wrong size 10000 https://test.winehq.org/data/patterns.html#ntdll:virtual Unsurprisingly a bisect shows that the failure appeared with this commit: commit 7d2a7b94aad8a776a2ee3031a18bb3b53d5925cd Author: Alexandre Julliard <julliard(a)winehq.org> Date: Fri Nov 19 11:04:30 2021 +0100 ntdll: Fix handling of zero size with MEM_DECOMMIT. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=52023 Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> See also bug 52067. -- 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 51986] New: Extremely small fonts when using a theme
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51986 Bug ID: 51986 Summary: Extremely small fonts when using a theme Product: Wine Version: 6.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: uxtheme Assignee: wine-bugs(a)winehq.org Reporter: aros(a)gmx.com Distribution: --- Created attachment 70973 --> https://bugs.winehq.org/attachment.cgi?id=70973 notepad After upgrading from Wine 6.19 to 6.21 certain fonts in certain applications became tiny. I'm using Windows XP Royal Theme. When not using any themes, it's all fine. See the attached screenshot for more info. -- 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 51647] New: Gimp can't create an image from screenshot (it becomes unresponsive instead)
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51647 Bug ID: 51647 Summary: Gimp can't create an image from screenshot (it becomes unresponsive instead) 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: cedric.dewijs(a)eclipso.eu Distribution: --- Created attachment 70505 --> https://bugs.winehq.org/attachment.cgi?id=70505 console messages Gimp can't make an image from a screenshot. To reproduce: $ rm -rf ~/.wine $ wineboot $ wine ~/Downloads/gimp-2.10.24-setup-3.exe $ wine ~/.wine/drive_c/Program\ Files/GIMP\ 2/bin/gimp-2.10.exe Choose File->Create->Screenshot Now gimp is no longer responsive, and the console shows this message: "03bc:err:ntdll:RtlpWaitForCriticalSection section 00000000006D0C18 "?" wait timed out in thread 03bc, blocked by 04d8, retrying (60 sec)" My versions: Gimp: 2.10 $ wine --version wine-6.15-123-gbe8501ac6f1 $ uname -a Linux cedric 5.13.10-arch1-1 #1 SMP PREEMPT Thu, 12 Aug 2021 21:59:14 +0000 x86_64 GNU/Linux -- 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 51183] New: Navicat V15.0.25 crashes when attempting to open database: "Unhandled exception: page fault...."
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51183 Bug ID: 51183 Summary: Navicat V15.0.25 crashes when attempting to open database: "Unhandled exception: page fault...." Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: profconn1(a)gmail.com Distribution: --- Created attachment 70056 --> https://bugs.winehq.org/attachment.cgi?id=70056 Error report from Navicat crash When attempting to open a database connection, Navicat crashes, displays error message and closes (using under Fedora 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.

1 12

[Bug 50985] New: ns_name_skip is glibc specific, causes failure to build on musl
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=50985 Bug ID: 50985 Summary: ns_name_skip is glibc specific, causes failure to build on musl Product: Wine Version: 6.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: dnsapi Assignee: wine-bugs(a)winehq.org Reporter: abenson+winehq(a)gmail.com Distribution: --- 6.6 introduced a reliance on glibc-specific calls in dlls/dnsapi/libresolv.c in commit 5f44c46164a5c0c50fffdf6cda9980a74079e1ac. Specifically, musl does not implement ns_name_skip, and the library fails at link time. -- 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 49426] New: Sookasa calls unimplemented functions and ntoskrnl.exe.RtlGetElementGenericTable ntoskrnl.exe.RtlLookupElementGenericTable
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=49426 Bug ID: 49426 Summary: Sookasa calls unimplemented functions and ntoskrnl.exe.RtlGetElementGenericTable ntoskrnl.exe.RtlLookupElementGenericTable Product: Wine Version: 5.11 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntoskrnl Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Created attachment 67510 --> https://bugs.winehq.org/attachment.cgi?id=67510 Terminal output To reproduce: 1. Run `winetricks dotnet40` 2. Run `wine Sookasa_3.18.4.exe` Console output is attached. After installation, the installer automatically starts Sookasa, but the following error message appears: Please reinstall Sookasa Sookasa was unable to install one of its components. Please reinstall Sookasa. If the problem persists, please contact support(a)sookasa.com [803] Unfortunately, stub implementations of these two functions are not enough to prevent a crash or avoid the error message. First reported at https://www.playonmac.com/en/topic-13406-Sookasa_not_installing.html $ sha256sum Sookasa_3.18.4.exe 6379c6da33663616193aa38db022d37383010ab5a077c1f1cb48ab1fab5ffdf2 -- 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 44427] New: Crashes program
by wine-bugs＠winehq.org 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=44427 Bug ID: 44427 Summary: Crashes program Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sluke0091(a)gmail.com Distribution: --- Created attachment 60369 --> https://bugs.winehq.org/attachment.cgi?id=60369 bug file attached Program opens and then crashes 5 seconds later. -- 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 7

[Bug 39339] New: Adventure games from Daedalic Ent. (Night of the Rabbit, Edna & Harvey, A New Beginning) have no in-game audio and freeze on new game start - XAudio2_7
by wine-bugs＠winehq.org 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=39339 Bug ID: 39339 Summary: Adventure games from Daedalic Ent. (Night of the Rabbit, Edna & Harvey, A New Beginning) have no in-game audio and freeze on new game start - XAudio2_7 Product: Wine Version: 1.7.51 Hardware: x86 URL: http://store.steampowered.com/app/230820/ OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: xaudio2 Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: aeikum(a)codeweavers.com Distribution: --- On my system the problem was surfaced by the Xaudio2 implementation in 1.7.51, the games used to work properly before. It sounds similar to bug #39320 and bug #39321, except that the proposed patch doesn't help here. All the adventure games from the developer/publisher Daedalic Entertainment that use Xaudio2 interface are affected in a similar manner: - the main menu is missing audio - when I try to start a new game or load a saved game, the game freezes (100% cpu usage) as soon as the game is loaded. - quitting the games from the main menu takes a long time (1-2 minutes) I reproduced the problem in these games: The Night of the Rabbit, Edna & Harvey: Harvey's New Eyes, A New Beginning - Final Cut. The games load xaudio2_7.dll Note that almost all these games have demo versions either on Steam or elsewhere, but those demos are older versions of the games and they don't use XAudio2. The only demo (so far) which has the bug is the Night of the Rabbit demo on Steam (link added to url). Steps to reproduce the problem in NotR demo: 1. install the demo on Steam. Steam installs .Net 3.5 and MSVC++, they are not needed for the game, you can delete the installers located in _CommonRedist before starting the demo. 2. the demo starts with a video (audio works in there). The menu has no audio with built-in xaudio2. 3. start a new game...the game seems to be hung at this point. It takes 1-2 minutes until the first intro video begins to play. Skip the video <Esc>, the game screen appears and the game is frozen for good. 4. you can reproduce the long wait before the game completely quits, if you exit the game from the main menu. wine-1.7.51-201-g60d1d6f Fedora 22 32-bit alsa-lib-1.0.29-1.fc22.i686 openal-soft-1.16.0-5.fc22.i686 Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2) -- 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 8

[Bug 52153] New: Airport Madness 3D 2 crashes as soon as I execute it
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=52153 Bug ID: 52153 Summary: Airport Madness 3D 2 crashes as soon as I execute it Product: Wine Version: 5.0.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: itsarav.2021(a)gmail.com Distribution: --- Created attachment 71201 --> https://bugs.winehq.org/attachment.cgi?id=71201 log file that wine prompted me to save and report later. So uh hi, I'm using Ubuntu, my first Linux experience since windows. I tried to run a Windows game, Airport Madness 3D 2, on my Linux. I used PlayOnLinux, selected the game's name, installed whatever wine wanted me to do (gecko etc) and finally installed the game... And as soon as I fire it up, it brings up the Unity Crash Handler, soon after which wine throws an error(see the log file below) and then PlayOnLinux comes up with "Error in main Airport Madness 3D V2 crashed." Same error without using PlayOnLinux. That game is my favorite. Any help upon the subject shall be appreciated. Sincerely, It's Arav -- 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 52139] New: Crash when closing explorer in different thread
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=52139 Bug ID: 52139 Summary: Crash when closing explorer in different thread Product: Wine Version: 6.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mikrutrafal(a)protonmail.com Distribution: --- Created attachment 71187 --> https://bugs.winehq.org/attachment.cgi?id=71187 Full log When closing windows explorer inside my app, explorer crash with this backtrace(explorer is probably run inside different thread) ``` Unhandled exception: page fault on read access to 0x0000000000000000 in 64-bit code (0x0000000000409d9b). Register dump: rip:0000000000409d9b rsp:00000000006ae740 rbp:00000000006ae948 eflags:00010246 ( R- -- I Z- -P- ) rax:000000000003ee10 rbx:00000000000300ca rcx:0000000000000000 rdx:0000000000000000 rsi:0000000000000000 rdi:0000000000000000 r8:0000000000000008 r9:0000000000000001 r10:0000000000000008 r11:0000000000000246 r12:0000000000000000 r13:000000000003ee10 r14:000000000003f670 r15:0000000000000000 Stack dump: 0x00000000006ae740: 0000000000000000 0000000000000000 0x00000000006ae750: 0000000000000000 0000000000000000 0x00000000006ae760: 0000000000000000 0000000000000000 0x00000000006ae770: 0000000000000000 0000000000000000 0x00000000006ae780: 0000000000000000 000000006eb9149e 0x00000000006ae790: 0000000000000000 00000000000300ca 0x00000000006ae7a0: 0000000000000000 0000000000000002 0x00000000006ae7b0: 0000000000000012 0000000000409c50 0x00000000006ae7c0: 00000000ffff0025 000000006eb9fb55 0x00000000006ae7d0: 0000000000000000 000000006eb5dbd3 0x00000000006ae7e0: 0000000000000000 0000000000000000 0x00000000006ae7f0: 0000000000000000 0000000000000100 Backtrace: =>0 0x0000000000409d9b IShellWindows_Revoke+0x7(lCookie=<internal error>, This=<internal error>) [Z:\usr\src\packages\BUILD\include\exdisp.h:2615] in explorer (0x00000000006ae948) 1 0x0000000000409d9b explorer_wnd_proc+0x14b(hwnd=<register RBX not accessible in this frame>, uMsg=<register R12 not accessible in this frame>, wParam=<register RSI not accessible in this frame>, lParam=<register R15 not accessible in this frame>) [Z:\usr\src\packages\BUILD\programs\explorer\explorer.c:713] in explorer (0x00000000006ae948) 2 0x000000006eb9fb55 call_window_proc+0x65(hwnd=<register RBX not accessible in this frame>, msg=<register R12 not accessible in this frame>, wp=<register RSI not accessible in this frame>, lp=<register RDI not accessible in this frame>, result=[<register RSP not accessible in this frame>, arg=[<register RSP not accessible in this frame>) [Z:\usr\src\packages\BUILD\dlls\user32\winproc.c:216] in user32 (0x00000000006ae948) 3 0x000000006eba1d89 WINPROC_call_window+0x219(hwnd=<register R12 not accessible in this frame>, msg=<register R13 not accessible in this frame>, wParam=<register RBX not accessible in this frame>, lParam=<register RBP not accessible in this frame>, result=[<register RSP not accessible in this frame>, unicode=[<register RSP not accessible in this frame>, mapping=[<register RSP not accessible in this frame>) [Z:\usr\src\packages\BUILD\dlls\user32\winproc.c:957] in user32 (0x0000000000000000) 4 0x000000006eb58946 call_window_proc+0x96(hwnd=<register RSI not accessible in this frame>, msg=<register R12 not accessible in this frame>, wparam=<register RBP not accessible in this frame>, lparam=<register RBX not accessible in this frame>, unicode=[<register RSP not accessible in this frame>, same_thread=[<register RSP not accessible in this frame>, mapping=[<register RSP not accessible in this frame>) [Z:\usr\src\packages\BUILD\dlls\user32\message.c:2231] in user32 (0x0000000000000000) 5 0x000000006eb5dfac send_message+0x23c(info=<register R12 not accessible in this frame>, res_ptr=<register RBX not accessible in this frame>, unicode=<register RBP not accessible in this frame>) [Z:\usr\src\packages\BUILD\dlls\user32\message.c:3207] in user32 (0x0000000000000001) 6 0x000000006eb5e1c9 SendMessageW+0x49(hwnd=<internal error>, msg=<internal error>, wparam=<internal error>, lparam=<internal error>) [Z:\usr\src\packages\BUILD\dlls\user32\message.c:3455] in user32 (0x00000000003e0000) 7 0x000000006eb911e4 WIN_SendDestroyMsg+0x64(hwnd=<register R12 not accessible in this frame>) [Z:\usr\src\packages\BUILD\dlls\user32\win.c:1964] in user32 (0x00000000003e0000) 8 0x000000006eb93928 DestroyWindow+0x258(hwnd=<register R13 not accessible in this frame>) [Z:\usr\src\packages\BUILD\dlls\user32\win.c:2063] in user32 (0x00000000003e0000) 9 0x000000006eb25a79 DEFWND_DefWinProc+0x919(hwnd=<register R13 not accessible in this frame>, msg=<internal error>, wParam=<register R15 not accessible in this frame>, lParam=<register R14 not accessible in this frame>) [Z:\usr\src\packages\BUILD\dlls\user32\defwnd.c:408] in user32 (0x00000000000300ca) 10 0x000000006eb26a0b DefWindowProcW+0x12b(hwnd=<register R12 not accessible in this frame>, msg=<register RBX not accessible in this frame>, wParam=<register RDI not accessible in this frame>, lParam=<register RSI not accessible in this frame>) [Z:\usr\src\packages\BUILD\dlls\user32\defwnd.c:1088] in user32 (0x00000000000300ca) 11 0x0000000000409e23 explorer_wnd_proc+0x1d3(hwnd=<register RBX not accessible in this frame>, uMsg=<register R12 not accessible in this frame>, wParam=<register RSI not accessible in this frame>, lParam=<register R15 not accessible in this frame>) [Z:\usr\src\packages\BUILD\programs\explorer\explorer.c:711] in explorer (0x00000000006aefb8) 12 0x000000006eb9fb55 call_window_proc+0x65(hwnd=<register RBX not accessible in this frame>, msg=<register R12 not accessible in this frame>, wp=<register RSI not accessible in this frame>, lp=<register RDI not accessible in this frame>, result=[<register RSP not accessible in this frame>, arg=[<register RSP not accessible in this frame>) [Z:\usr\src\packages\BUILD\dlls\user32\winproc.c:216] in user32 (0x00000000006aefb8) 13 0x000000006eba1d89 WINPROC_call_window+0x219(hwnd=<register R12 not accessible in this frame>, msg=<register R13 not accessible in this frame>, wParam=<register RBX not accessible in this frame>, lParam=<register RBP not accessible in this frame>, result=[<register RSP not accessible in this frame>, unicode=[<register RSP not accessible in this frame>, mapping=[<register RSP not accessible in this frame>) [Z:\usr\src\packages\BUILD\dlls\user32\winproc.c:957] in user32 (0x0000000000000000) 14 0x000000006eb58946 call_window_proc+0x96(hwnd=<register RSI not accessible in this frame>, msg=<register R12 not accessible in this frame>, wparam=<register RBP not accessible in this frame>, lparam=<register RBX not accessible in this frame>, unicode=[<register RSP not accessible in this frame>, same_thread=[<register RSP not accessible in this frame>, mapping=[<register RSP not accessible in this frame>) [Z:\usr\src\packages\BUILD\dlls\user32\message.c:2231] in user32 (0x0000000000000000) 15 0x000000006eb5dfac send_message+0x23c(info=<register R12 not accessible in this frame>, res_ptr=<register RBX not accessible in this frame>, unicode=<register RBP not accessible in this frame>) [Z:\usr\src\packages\BUILD\dlls\user32\message.c:3207] in user32 (0x0000000000000001) 16 0x000000006eb5e1c9 SendMessageW+0x49(hwnd=<internal error>, msg=<internal error>, wparam=<internal error>, lparam=<internal error>) [Z:\usr\src\packages\BUILD\dlls\user32\message.c:3455] in user32 (0x00000000000300ca) 17 0x000000006eb26a0b DefWindowProcW+0x12b(hwnd=<register R12 not accessible in this frame>, msg=<register RBX not accessible in this frame>, wParam=<register RDI not accessible in this frame>, lParam=<register RSI not accessible in this frame>) [Z:\usr\src\packages\BUILD\dlls\user32\defwnd.c:1088] in user32 (0x00000000000300ca) 18 0x0000000000409e23 explorer_wnd_proc+0x1d3(hwnd=<register RBX not accessible in this frame>, uMsg=<register R12 not accessible in this frame>, wParam=<register RSI not accessible in this frame>, lParam=<register R15 not accessible in this frame>) [Z:\usr\src\packages\BUILD\programs\explorer\explorer.c:711] in explorer (0x00000000006af438) 19 0x000000006eb9fb55 call_window_proc+0x65(hwnd=<register RBX not accessible in this frame>, msg=<register R12 not accessible in this frame>, wp=<register RSI not accessible in this frame>, lp=<register RDI not accessible in this frame>, result=[<register RSP not accessible in this frame>, arg=[<register RSP not accessible in this frame>) [Z:\usr\src\packages\BUILD\dlls\user32\winproc.c:216] in user32 (0x00000000006af438) 20 0x000000006eba1d89 WINPROC_call_window+0x219(hwnd=<register R12 not accessible in this frame>, msg=<register R13 not accessible in this frame>, wParam=<register RBX not accessible in this frame>, lParam=<register RBP not accessible in this frame>, result=[<register RSP not accessible in this frame>, unicode=[<register RSP not accessible in this frame>, mapping=[<register RSP not accessible in this frame>) [Z:\usr\src\packages\BUILD\dlls\user32\winproc.c:957] in user32 (0x0000000000000000) 21 0x000000006eb61bd1 DispatchMessageW+0xa9(msg=[<register RSP not accessible in this frame>) [Z:\usr\src\packages\BUILD\dlls\user32\message.c:4028] in user32 (0x00000000006af6c0) 22 0x000000000040a9e8 make_explorer_window+0x709(params=<internal error>) [Z:\usr\src\packages\BUILD\programs\explorer\explorer.c:545] in explorer (0x00000000006af6c0) 23 0x000000000040a9e8 wWinMain+0x898(hinstance=<internal error>, previnstance=<internal error>, cmdline=<internal error>, cmdshow=<internal error>) [Z:\usr\src\packages\BUILD\programs\explorer\explorer.c:877] in explorer (0x00000000006af6c0) 24 0x000000000040f223 wmain+0xb3(argc=<internal error>, argv=<internal error>) [Z:\usr\src\packages\BUILD\dlls\msvcrt\crt_wwinmain.c:56] in explorer (0x0000000000000000) 25 0x000000000040f165 wmainCRTStartup+0x65() [Z:\usr\src\packages\BUILD\dlls\msvcrt\crt_wmain.c:58] in explorer (0x0000000000000000) 26 0x000000007b62c669 BaseThreadInitThunk+0x9(unknown=<internal error>, entry=<internal error>, arg=<internal error>) [Z:\usr\src\packages\BUILD\dlls\kernel32\thread.c:61] in kernel32 (0x0000000000000000) 27 0x000000007bc5b323 __wine_pop_frame(unknown=<internal error>, entry=<internal error>, arg=<internal error>) [Z:\usr\src\packages\BUILD\include\wine\exception.h:273] in ntdll (0x0000000000000000) 28 0x000000007bc5b323 RtlUserThreadStart+0x83(entry=[<register RSP not accessible in this frame>, arg=[<register RSP not accessible in this frame>) [Z:\usr\src\packages\BUILD\dlls\ntdll\thread.c:240] in ntdll (0x0000000000000000) 0x0000000000409d9b explorer_wnd_proc+0x14b [Z:\usr\src\packages\BUILD\programs\explorer\explorer.c:713] in explorer: movq (%rcx),%rax Unable to access file 'Z:\usr\src\packages\BUILD\programs\explorer\explorer.c' ``` Bigger log inside attachment Steps to reproduce - Download app - https://github.com/qarmin/czkawka/releases/download/3.3.1/windows_czkawka_g… - Open `windows_czkawka_gui.exe` - Find any file with one of tools - Click at the found file twice with right mouse button - Close explorer -- 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 52137] New: World of Warcraft (WoW) crashes in both DX11 modes
by WineHQ Bugzilla 02 Dec '21

02 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=52137 Bug ID: 52137 Summary: World of Warcraft (WoW) crashes in both DX11 modes Product: Wine Version: 6.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: blue-t(a)web.de Distribution: --- Created attachment 71184 --> https://bugs.winehq.org/attachment.cgi?id=71184 DX11 (modern renderer) For me the game boots find, gets to the character selection screen and when the progress bar finishes and the character should enter the world, the game crashes. ACCESS_VIOLATION : error 132: ERROR #132 (0x85100084) Fatal exception! The instruction at "0x00007f4222f8e937" referenced memory at "0x000000000000001c". The memory could not be "written". This happens for DX11 modern and DX11 legacy mode but so far hasn't occurred with DX12. -- 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 52134] New: Dragon's Dogma CTD after logo
by WineHQ Bugzilla 02 Dec '21

02 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=52134 Bug ID: 52134 Summary: Dragon's Dogma CTD after logo Product: Wine Version: 6.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: pashiri(a)laposte.net Distribution: --- Created attachment 71171 --> https://bugs.winehq.org/attachment.cgi?id=71171 standard output Dragon's Dogma dark arisen crash to desktop on reaching the menu after showing the logos on Archwith wine-dev. error is 01e8:err:module:ntdll_init_syscalls syscall count mismatch 0 / 96 Other games work fine, wine 6.19 works fine too. 6.20 has sound issues, 6.21 & 6.22 crash the same way. -- 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 36844] New: Multiple games need X3DAudio1_7.dll (BeamNG v0.3 Tech Demo)
by wine-bugs＠winehq.org 01 Dec '21

01 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=36844 Bug ID: 36844 Summary: Multiple games need X3DAudio1_7.dll (BeamNG v0.3 Tech Demo) Product: Wine Version: 1.7.21 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-dsound Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Hello folks, as the summary says. Bug 12182 should be avoided in future (meta bug) .. very unfortunate, covering all XAudio dlls. Better are bugs that specifically target stub dlls like bug 24545 ("Monkey Island: Special Edition wants X3DAudio1_6.dll"). --- snip --- $ pwd /home/focht/.wine/drive_c/users/focht/Local Settings/Application Data/BeamNG/BeamNG-Techdemo-0.3 ... $ wine ./BeamNGSandbox.x86.exe ... err:module:import_dll Library X3DAudio1_7.dll (which is needed by L"C:\\users\\focht\\Local Settings\\Application Data\\BeamNG\\BeamNG-Techdemo-0.3\\BeamNGSandbox.x86.dll") not found --- snip --- $ sha1sum BeamNG-Techdemo-0.3-setup.zip 21b29af0c77cf138ec69edf1c4cb0d4504bb2ed9 BeamNG-Techdemo-0.3-setup.zip $ du -sh BeamNG-Techdemo-0.3-setup.zip 95M BeamNG-Techdemo-0.3-setup.zip $ wine --version wine-1.7.21-50-g10e6a66 Regards -- 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 42449] New: unimplemented function msvcr120.dll.fesetround called in 32-bit code
by wine-bugs＠winehq.org 01 Dec '21

01 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=42449 Bug ID: 42449 Summary: unimplemented function msvcr120.dll.fesetround called in 32-bit code Product: Wine Version: 2.1 Hardware: x86 URL: https://play0ad.com/ OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: version2013(a)openmailbox.org Distribution: --- Created attachment 57287 --> https://bugs.winehq.org/attachment.cgi?id=57287 backtrace (Windows XP) Seeing if "O A.D." will run in Wine. Running it the first time to get backtrace. See attachment "backtrace (Windows XP)". Running game a second time to get other terminal output: wine pyrogenesis.exe fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x33fb8c 1 C) semi-stub fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x33fa6c 1 C) semi-stub fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x33f9c0 1 C) semi-stub fixme:heap:RtlSetHeapInformation 0x110000 0 0x33fd40 4 stub fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x33f5dc 1 C) semi-stub fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x33f400 1 C) semi-stub fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x33f67c 1 C) semi-stub fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x33f74c 1 C) semi-stub wine: Call from 0x7b43e046 to unimplemented function msvcr120.dll.fesetround, aborting fixme:msvcrt:__clean_type_info_names_internal (0x3b97d4) stub fixme:msvcrt:__clean_type_info_names_internal (0x39d3c0) stub fixme:msvcrt:__clean_type_info_names_internal (0xd80af4) stub AL lib: (EE) alc_cleanup: 1 device not closed fixme:msvcrt:__clean_type_info_names_internal (0xc89764) stub fixme:msvcrt:__clean_type_info_names_internal (0xbdc218) stub fixme:msvcrt:__clean_type_info_names_internal (0x4a95facc) stub fixme:msvcrt:__clean_type_info_names_internal (0x8d51a4) stub fixme:msvcrt:__clean_type_info_names_internal (0x9c0348) stub fixme:msvcrt:__clean_type_info_names_internal (0x38137c) stub fixme:msvcrt:__clean_type_info_names_internal (0x103b30f4) stub fixme:msvcrt:__clean_type_info_names_internal (0x3675fc) stub -- 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 51674] New: Uplay Connect app doesn't run
by WineHQ Bugzilla 01 Dec '21

01 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51674 Bug ID: 51674 Summary: Uplay Connect app doesn't run Product: Wine-staging Version: 6.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: omrkrdmnmlt0044(a)outlook.com.tr CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Uplay Connect app doesn't run -- 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs December 2021