September 2023 - Wine-bugs - list.winehq.org

[Bug 55555] New: secur32:secur32 - test_ticket_cache() crashes on macOS
by WineHQ Bugzilla 29 Oct '23

29 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55555 Bug ID: 55555 Summary: secur32:secur32 - test_ticket_cache() crashes on macOS Product: Wine Version: unspecified Hardware: x86-64 OS: Mac OS X Status: NEW Severity: normal Priority: P2 Component: secur32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com secur32:secur32 - test_ticket_cache() crashes on macOS: secur32.c:485: Test failed: got c0000135 Unhandled exception: page fault on read access to 0x0000000000000000 in 64-bit code (0x00000140013f0a). See https://test.winehq.org/data/patterns.html#secur32:secur32 Where 0xc0000135 == STATUS_DLL_NOT_FOUND The crash is systematic and only happens macOS (see Remi's rbernon-macos-* cloud test machines). Maybe Kerberos support is missing? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 55605] New: winmm:mci sometimes gets an assertion in GitLab CI's Wine tests
by WineHQ Bugzilla 29 Oct '23

29 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55605 Bug ID: 55605 Summary: winmm:mci sometimes gets an assertion in GitLab CI's Wine tests 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 sometimes crashes in Wine: mci.c:1259: Wine style MCI auto-close upon notification Unhandled exception: assertion failed in wow64 32-bit code (0xf7faf559). See https://test.winehq.org/data/patterns.html#winmm:mci test_AutoOpenWAVE()'s "Wine style" trace is usually the last in the report so the crash may happen in that function or one that is called after. Furthermore this crash is specific to the GitLab CI Wine test environment and the oldest known instance happened on 2023-07-18. So this may have started with GitLab CI's switch to the Debian 12 build environment (2023-07-10): * 2023-09-15 MR!3808 * 2023-09-14 MR!3805 * 2023-09-14 MR!3779 * 2023-09-14 MR!3757 * 2023-09-12 MR!3802 * 2023-09-01 MR!3505 * 2023-08-29 linux_gitlab-debian-32 * 2023-08-28 linux_gitlab-debian-32 * 2023-08-23 MR!3635 * 2023-08-22 MR!3632 * 2023-08-16 MR!3577 * 2023-08-14 MR!3473 * 2023-08-03 linux_gitlab-debian-32 * 2023-08-02 MR!3433 * 2023-08-01 MR!3452 * 2023-07-31 MR!3323 * 2023-07-27 MR!3379 * 2023-07-20 MR!3260 * 2023-07-18 MR!3350 -- 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 55267] New: gdi32:font - The 64-bit test_RealizationInfo() gets invalid parameter errors on Windows 8+
by WineHQ Bugzilla 29 Oct '23

29 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55267 Bug ID: 55267 Summary: gdi32:font - The 64-bit test_RealizationInfo() gets invalid parameter errors on Windows 8+ Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com gdi32:font - The 64-bit test_RealizationInfo() gets invalid parameter errors on Windows 8+: font.c:4470: Test failed: ret 0 gle 87 font.c:4472: Test failed: mismatch See https://test.winehq.org/data/patterns.html#gdi32:font Where 87 == ERROR_INVALID_PARAMETER This is specific to the 64-bit tests and first happened on 2023-07-10 which corresponds to the GitLab CI's move to Debian 12 for building the Windows test binaries (5799e89f15b5). This is confirmed by the fact that test executables built on Debian 11 still don't get these failures. In particular this means: * These failures will show up in the TestBot's nightly WineTest results since they use the official winetest.exe binaries built by the GitLab CI on Debian 12. * But they will not happen when testing patches on the TestBot since, so far, it still builds the tests on Debian 11. -- 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 49731] New: Shtriga: Summer Camp freezes with a black screen (PE-build only)
by WineHQ Bugzilla 29 Oct '23

29 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=49731 Bug ID: 49731 Summary: Shtriga: Summer Camp freezes with a black screen (PE-build only) Product: Wine Version: 5.15 Hardware: x86 URL: https://store.steampowered.com/app/560740/Shtriga_Summ er_Camp/ OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com Distribution: --- The game displays some company logos after startup then it gets stuck with a black screen. Wine built without Mingw loads the game properly. Plain terminal output: 0024:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION 0024:fixme:dwmapi:DwmSetWindowAttribute (00020064, 7, 0031BD7C, 4) stub 0024:fixme:d3d:state_linepattern_w Setting line patterns is not supported in OpenGL core contexts. wine-5.15-108-gab94abb14f -- 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 45144] New: The GED Keeper 2 program does not start.
by wine-bugs＠winehq.org 29 Oct '23

29 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=45144 Bug ID: 45144 Summary: The GED Keeper 2 program does not start. Product: Wine-staging Version: 3.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: michal.michcik(a)interia.pl CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 61329 --> https://bugs.winehq.org/attachment.cgi?id=61329 Log from PlayOnLinux Debuger Link to the mentioned program. https://sourceforge.net/projects/gedkeeper/?source=typ_redirect -- 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 10

[Bug 43372] New: valgrind shows a definite leak in dlls/d3dx9_36/tests/ texture.c
by wine-bugs＠winehq.org 29 Oct '23

29 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=43372 Bug ID: 43372 Summary: valgrind shows a definite leak in dlls/d3dx9_36/tests/texture.c Product: Wine Version: 2.12 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase, valgrind Severity: normal Priority: P2 Component: directx-d3dx9 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: --- ../../../tools/runtest -q -P wine -T ../../.. -M d3dx9_36.dll -p d3dx9_36_test.exe.so texture && touch texture.ok ==9786== 8 bytes in 1 blocks are definitely lost in loss record 165 of 2,887 ==9786== at 0x7BC51061: notify_alloc (heap.c:254) ==9786== by 0x7BC5554F: RtlAllocateHeap (heap.c:1716) ==9786== by 0x4CBB72D: D3DXCreateTextureShader (shader.c:2405) ==9786== by 0x4AA083C: test_texture_shader (texture.c:2053) ==9786== by 0x4AA1B5A: func_texture (texture.c:2297) ==9786== by 0x4AA5A93: run_test (test.h:603) ==9786== by 0x4AA5EF2: main (test.h:687) ==9786== ==9786== 8 bytes in 1 blocks are definitely lost in loss record 166 of 2,887 ==9786== at 0x7BC51061: notify_alloc (heap.c:254) ==9786== by 0x7BC5554F: RtlAllocateHeap (heap.c:1716) ==9786== by 0x4CBB72D: D3DXCreateTextureShader (shader.c:2405) ==9786== by 0x4AA08DA: test_texture_shader (texture.c:2056) ==9786== by 0x4AA1B5A: func_texture (texture.c:2297) ==9786== by 0x4AA5A93: run_test (test.h:603) ==9786== by 0x4AA5EF2: main (test.h:687) ==9786== ==9786== 8 bytes in 1 blocks are definitely lost in loss record 167 of 2,887 ==9786== at 0x7BC51061: notify_alloc (heap.c:254) ==9786== by 0x7BC5554F: RtlAllocateHeap (heap.c:1716) ==9786== by 0x4CBB72D: D3DXCreateTextureShader (shader.c:2405) ==9786== by 0x4AA0978: test_texture_shader (texture.c:2059) ==9786== by 0x4AA1B5A: func_texture (texture.c:2297) ==9786== by 0x4AA5A93: run_test (test.h:603) ==9786== by 0x4AA5EF2: main (test.h:687) ==9786== -- 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 3

[Bug 55577] New: advapi32:registry - The 64-bit test_performance_keys() sometimes crashes on Windows 10
by WineHQ Bugzilla 29 Oct '23

29 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55577 Bug ID: 55577 Summary: advapi32:registry - The 64-bit test_performance_keys() sometimes crashes on Windows 10 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: advapi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com advapi32:registry - The 64-bit test_performance_keys() sometimes crashes on Windows 10: registry.c:4203: Test failed: key FFFFFFFF80000050: got 8 registry.c:4204: Test failed: key FFFFFFFF80000050: got size 0 registry.c:4209: Test failed: key FFFFFFFF80000050: got 8 registry.c:4210: Test failed: key FFFFFFFF80000050: got size 0 registry.c:4250: Test failed: key FFFFFFFF80000050: got 8 registry.c:4251: Test failed: key FFFFFFFF80000050: got size 0 registry.c:4261: Test failed: key FFFFFFFF80000050: got 8 registry.c:4091: Test failed: key FFFFFFFF80000050: did not find name registry.c:4093: this is the last test seen before the exception 0304:registry: unhandled exception c0000005 at 00007FFA9AD2D110 See https://test.winehq.org/data/patterns.html#advapi32:registry The number of test failures varies a bit from one run to the next. The crashes started on 2023-09-04 and so far only happen on the non-English configurations of the w10pro64 TestBot VM. -- 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 45893] New: Midtown Madness: Extremely Slow with csmt on
by wine-bugs＠winehq.org 29 Oct '23

29 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=45893 Bug ID: 45893 Summary: Midtown Madness: Extremely Slow with csmt on Product: Wine Version: 3.16 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sa(a)whiz.se Distribution: --- The game Midtown Madness is unplayably slow with csmt turned on. This can be reproduced with the demo version of the game. This is an old title from 1999 that uses direct draw AFAICT. The game needs Windows version set to XP or lower, and either be run with an Xserver supporting 16bpp colors, or a hack to force Wine to use 16bpp. https://www.fileplanet.com/19814/10000/fileinfo/Midtown-Madness-Demo -- 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 10

[Bug 32395] New: Neverwinter Nights 2 : Broken sky
by wine-bugs＠winehq.org 29 Oct '23

29 Oct '23

http://bugs.winehq.org/show_bug.cgi?id=32395 Bug #: 32395 Summary: Neverwinter Nights 2 : Broken sky Product: Wine Version: 1.5.19 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: xvachon(a)gmail.com Classification: Unclassified Created attachment 42747 --> http://bugs.winehq.org/attachment.cgi?id=42747 Screenshot In Neverwinter Nights 2, the sky fails to display properly. Look at the attached screenshot for an example. It reminds me of http://bugs.winehq.org/show_bug.cgi?id=23012 in the sense that the faulty portion of the sky seems similar, but the sky is not black. The console outputs this error appears in loop , is it related to this bug? err:d3d_surface:surface_blt_fbo >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glBlitFramebuffer() @ surface.c / 1265 Otherwise the console outputs nothing in particular. A specific channel could be required to identify the culprit. Wine 1.5.19 Neverwinter Nights 2 1.23 Nvidia 550 Ti Arch Linux X64 -- 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 9

[Bug 55223] New: d3dx10_34:d3dx10 & d3dx10_35:d3dx10 sometimes fail on w11pro64-amd
by WineHQ Bugzilla 29 Oct '23

29 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55223 Bug ID: 55223 Summary: d3dx10_34:d3dx10 & d3dx10_35:d3dx10 sometimes fail on w11pro64-amd Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: d3d-util Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com d3dx10_34:d3dx10 & d3dx10_35:d3dx10 sometimes fail on w11pro64-amd-64: d3dx10.c:2970: Test failed: Test 4: Got unexpected hr2 0xdeadbeef. d3dx10.c:2979: Test failed: Test 4: Got unexpected hr2 0xdeadbeef. d3dx10.c:2970: Test failed: Test 25: Got unexpected hr2 0xdeadbeef. d3dx10.c:2979: Test failed: Test 25: Got unexpected hr2 0xdeadbeef. d3dx10.c:3161: Test failed: Test 4: Got unexpected hr 0x88760b59. d3dx10.c:3163: Test failed: Test 4: Got unexpected hr2 0xdeadbeef. d3dx10.c:3174: Test failed: Test 4: Got unexpected hr 0x88760b59. d3dx10.c:3176: Test failed: Test 4: Got unexpected hr2 0xdeadbeef. d3dx10.c:3161: Test failed: Test 25: Got unexpected hr 0x88760b59. d3dx10.c:3163: Test failed: Test 25: Got unexpected hr2 0xdeadbeef. d3dx10.c:3174: Test failed: Test 25: Got unexpected hr 0x88760b59. d3dx10.c:3176: Test failed: Test 25: Got unexpected hr2 0xdeadbeef. See https://test.winehq.org/data/patterns.html#d3dx10_34:d3dx10 https://test.winehq.org/data/patterns.html#d3dx10_35:d3dx10 Where 0x88760b59 == D3DXERR_INVALIDDATA And the number of failures is variable but always happens in either test_get_image_info() or test_create_texture(), but seemingly on random test_image indexes. Also the failure always happens on the TestBot's AMD RX6600 PCI passthrough configuration (the QEmu QXL and Nvidia configurations have no failure). And this error first happened on 2023-06-14 and has been happening about twice a week but I could not identify which commit is causing the failures. -- 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