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

[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

[Bug 54704] New: Black screen with Dungeon Keeper 2 and Wine v8.4
by WineHQ Bugzilla 29 Oct '23

29 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=54704 Bug ID: 54704 Summary: Black screen with Dungeon Keeper 2 and Wine v8.4 Product: Wine Version: 8.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: reserv0(a)yahoo.com Distribution: --- Created attachment 74213 --> https://bugs.winehq.org/attachment.cgi?id=74213 DK2 log (with broken Wine 8.4 and working Wine 8.3) I just compiled and tried Wine v8.4, and with it, I get a black screen after the intro screen, at the menu stage of Dungeon Keeper 2. This game is working just fine with (almost) all Wine versions between 6.something (I don't remember exactly which) and 8.3 (I reverted to the latter for now). There is alas no clue in the messages I get when starting DK2 from a terminal (I get the exact same messages as with v8.3; log attached). Note that I am using MATE (v1.14.1, GTK2) as the desktop environment, without any compositor, and in X11 mode (no Wayland installed on my system and Wine 8.4 compiled --without-wayland) with a NVIDIA GPU (RTX 3070) and the latest NVIDIA proprietary drivers. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 24

[Bug 45135] New: Black Rockman Shooter has no sound, implementation missing in dmime
by wine-bugs＠winehq.org 29 Oct '23

29 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=45135 Bug ID: 45135 Summary: Black Rockman Shooter has no sound, implementation missing in dmime Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: l12436(a)yahoo.com.tw Distribution: --- Created attachment 61322 --> https://bugs.winehq.org/attachment.cgi?id=61322 stdout of that game. Game "Black Rockman Shooter" has not sound at the begin. Although override the dmime could make sound, the game will become laggy. Some other game also using same dll to make sound and has same situation. -- 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 52014] New: Memento Mori stucks on launch
by WineHQ Bugzilla 29 Oct '23

29 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=52014 Bug ID: 52014 Summary: Memento Mori stucks on launch Product: Wine Version: 6.21 Hardware: x86-64 OS: Linux Status: NEW Severity: minor Priority: P2 Component: wmp&wmvcore Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- winegstreamer warning: videoconvert1: not negotiated winegstreamer warning: videoconvert1: ../libs/gst/base/gstbasetransform.c(1431): gst_base_transform_reconfigure_unlocked (): /GstBin:bin0/GstVideoConvert:videoconvert1: not negotiated winegstreamer warning: videoconvert1: not negotiated winegstreamer warning: videoconvert1: ../libs/gst/base/gstbasetransform.c(1431): gst_base_transform_reconfigure_unlocked (): /GstBin:bin0/GstVideoConvert:videoconvert1: not negotiated 04a0:fixme:dsound:IDirectSoundBufferImpl_Restore (14B393D0):stub 04a0:err:sync:RtlpWaitForCriticalSection section 00DD85F4 "../wine/dlls/winegstreamer/wm_asyncreader.c: async_reader.stream_cs" wait timed out in thread 04a0, blocked by 04e8, retrying (60 sec) 04e8:err:sync:RtlpWaitForCriticalSection section 0A6DF734 "?" wait timed out in thread 04e8, blocked by 04a0, retrying (60 sec) wine-6.21-116-g6a072b98c10 -- 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 55228] New: kernel32:loader - test_ResolveDelayLoadedAPI() fails on Windows 10+
by WineHQ Bugzilla 29 Oct '23

29 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55228 Bug ID: 55228 Summary: kernel32:loader - test_ResolveDelayLoadedAPI() fails on Windows 10+ Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com kernel32:loader - test_ResolveDelayLoadedAPI() fails on Windows 10+: loader.c:3979: Test failed: Test 0: expected 74464550, got 10001A00 loader.c:3998: Test failed: Test 0: expected 74464550, got 10001A00 loader.c:3979: Test failed: Test 1: expected 70492CF0, got 10001A20 loader.c:3998: Test failed: Test 1: expected 70492CF0, got 10001A20 loader.c:3979: Test failed: Test 2: expected 74462DC0, got 10001A40 loader.c:3998: Test failed: Test 2: expected 74462DC0, got 10001A40 loader.c:3987: Test failed: Test 3: ResolveDelayLoadedAPI succeeded with 10001A60 loader.c:3989: Test failed: Test 3: Wrong sys callback count: 0 loader.c:4018: Test failed: Test 3: ResolveDelayLoadedAPI succeeded with 10001A60 loader.c:3987: Test failed: Test 4: ResolveDelayLoadedAPI succeeded with 10001A80 loader.c:3989: Test failed: Test 4: Wrong sys callback count: 0 loader.c:4018: Test failed: Test 4: ResolveDelayLoadedAPI succeeded with 10001A80 See https://test.winehq.org/data/patterns.html#kernel32:loader -- 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 55654] New: High RAM usage in GTA San Andreas with SkyGFX
by WineHQ Bugzilla 29 Oct '23

29 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55654 Bug ID: 55654 Summary: High RAM usage in GTA San Andreas with SkyGFX Product: Wine Version: 8.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: aidas957(a)gmail.com CC: z.figura12(a)gmail.com Regression SHA1: c065b4fe0b3622e0c737a4c7c1c514273ad2d8a7 Distribution: ArchLinux Hello, So GTA San Andreas has high RAM usage when using the SkyGFX mod since commit c065b4fe0b3622e0c737a4c7c1c514273ad2d8a7 At first the RAM usage seems normal (no more 400 MB) but after doing a loop around the city the RAM usage gets to ~1.5 GB Commit 22fcf28f05a2478df01b0a0cfae1a49376c990f5 does improve things (the RAM usage when doing the same test is ~1.2 GB) but it's still noticeably higher than before Disabling/removing the SkyGFX mod or switching to DXVK makes the issue disappear (so it's some weird interaction with the SkyGFX mod and WineD3D) I do use wine-staging like always (but disabling all of the wined3d staging patchsets didn't make a difference) The mod is open-source though (https://github.com/aap/skygfx) so it should be easier to tell what graphics code/shader file is triggering the high RAM issue I tried using valgrind's massif to track the cause of this issue but valgrind didn't support some instructions that are used by 2 mods (and doing some byte patching caused SkyGFX to segfault so that's out of the question) +d3d logs/an apitrace might be helpful but the issue only becomes noticeable enough after a few minutes so both of these are going to be likely too big -- 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 48550] New: Right click doesn't work on system tray icons (Plasma desktop issue)
by WineHQ Bugzilla 29 Oct '23

29 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=48550 Bug ID: 48550 Summary: Right click doesn't work on system tray icons (Plasma desktop issue) Product: Wine Version: 5.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ahmed.com(a)protonmail.com Distribution: --- When clicking by the right button on any system-tray icons under Wine, it doesn't respond, and shows the menu. This issue happens only with KDE Plasma desktop, and it is quite old issue, but I didn't report it before, because I was using a modified wine builds that had a patch for this issue. System info: OS: Kubuntu 19.10 KDE Plasma version: 5.16.5 KDE Frameworks version: 5.62.0 Qt version: 5.12.4 -- 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 54175] New: MAME 0.224 (windows version) cannot start any machine due to Direct3d 9 initialization failure
by WineHQ Bugzilla 28 Oct '23

28 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=54175 Bug ID: 54175 Summary: MAME 0.224 (windows version) cannot start any machine due to Direct3d 9 initialization failure Product: Wine Version: 7.0.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: VladimirVSC(a)yandex.ru Distribution: --- Created attachment 73697 --> https://bugs.winehq.org/attachment.cgi?id=73697 MAME crash when starting any machine (NES in this case) The windows version of MAME 0.224 cannot start any machine because of direct3d 9 initialization error (as it is written in console output) in stable 7.0.1 version (with dxvk 1.10.3 installed). However, everything was working fine in stable 7.0. It seems to be some kind of regression in 7.0.1. I cannot test dxvk 2.0 version (if it is the reason) because of my GTX 760 support abandoning. The drivers tested were 470.131.03 and the latest 470.161.03. -- 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 55685] New: FlatOut 2 crashes due to HLSL syntax error 'unexpected NEW_IDENTIFIER'
by WineHQ Bugzilla 28 Oct '23

28 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55685 Bug ID: 55685 Summary: FlatOut 2 crashes due to HLSL syntax error 'unexpected NEW_IDENTIFIER' Product: vkd3d Version: 1.9 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: hlsl Assignee: wine-bugs(a)winehq.org Reporter: gijsvrm(a)gmail.com Distribution: --- Created attachment 75206 --> https://bugs.winehq.org/attachment.cgi?id=75206 log + shader 0024:err:d3dcompiler:D3DCompile2 Failed to compile shader, vkd3d result -4. 0024:err:d3dcompiler:D3DCompile2 Shader log: 0024:err:d3dcompiler:D3DCompile2 <anonymous>:11:1: E5000: syntax error, unexpected NEW_IDENTIFIER 0024:err:d3dcompiler:D3DCompile2 Attached is an archive including a vkd3d & +d3dcompiler log and the relevant dumped shader. This might be related to bug 54872, but I'm not sure. -- 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