November 2021 - Wine-bugs - list.winehq.org

[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 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 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 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 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 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 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 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 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