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

[Bug 39876] New: Humanity Asset crashes on start with built-in d3dx
by wine-bugs＠winehq.org 15 Oct '23

15 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=39876 Bug ID: 39876 Summary: Humanity Asset crashes on start with built-in d3dx Product: Wine Version: 1.9.0 Hardware: x86 URL: http://www.moddb.com/games/humanity-asset/downloads/hu manity-asset-demo# OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: directx-d3dx9 Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com Distribution: --- Created attachment 53243 --> https://bugs.winehq.org/attachment.cgi?id=53243 +d3dx log The demo comes bundled with native d3dx9_38.dll, if you set it to 'built-in' in winecfg, then the game crashes while loading to the main menu. HumanityAssetDemo.2.rar sha1: 619538846bc8c8a6d8d319378708582ef41be1c4 -- 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 25988] New: Mr. Smoozles Goes Nutso: problems playing sound
by wine-bugs＠winehq.org 14 Oct '23

14 Oct '23

http://bugs.winehq.org/show_bug.cgi?id=25988 Summary: Mr. Smoozles Goes Nutso: problems playing sound Product: Wine Version: 1.3.12 Platform: x86 URL: http://www.juniper-games.com/smoozles/Nutsosetup.exe OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: gyebro69(a)gmail.com Created an attachment (id=33126) --> (http://bugs.winehq.org/attachment.cgi?id=33126) terminal output (only built-in dlls) The game is a nice, freeware adventure puzzle game. Neither sound nor music is playing in the game with a clean Wine install. After installing the directmusic components via winetricks and starting Timidity as a separate process music is playing fine in the menu and in some of the scenes. However there are still problems playing sound effects during gameplay: it is most noticeable in the first scene where a simple sound effect is intended to play (sounds like a shooting sound). The game becomes almost unplayable because of a strange lagging issue: the game barely responds to keyboard events while the sound is playing. Once you manage to make it past the first scene, gameplay seems to be back to normal in the second scene. It seems that the lagging issue has something to do with the looping sound effect during the first scene. The first log is showing the output without native directmusic dlls. -- 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 44276] New: Poor resolution change handling with Shadow of Memories demo
by wine-bugs＠winehq.org 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=44276 Bug ID: 44276 Summary: Poor resolution change handling with Shadow of Memories demo Product: Wine Version: 2.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jhansonxi(a)gmail.com Distribution: Ubuntu Created attachment 60099 --> https://bugs.winehq.org/attachment.cgi?id=60099 Log from successful demo gameplay start When game starts (fresh boot) it shows only the upper-left quadrant of the logo screens. It then changes resolution and shows the intro video the size of a postage stamp (often loses focus and an alt-tab is needed to see it). It then shows only the upper-left quadrant of the main menu. It's possible to pan around and see all of it but the button graphics don't align with the buttons so they're hard to target with the pointer. At the main menu, if the game is started it often freezes at the "Prologue" screen. Alt-tabbing during these various stages can trigger some odd effects (at least with the Nvidia proprietary driver). The game will crash, the screen gets left at a low resolution, etc. Eventually the behavior changes - the game launches the opening screens correctly sized but with the Xfce desktop panel still visible. The game will then be startable (won't freeze at the "Prologue" screen). It still seems to freeze further along, normally after the tea house scene when control is returned to the player. The behavior is persistent until the system is rebooted. The CD version of the game acts the same except it never seems to get past "Prologue". Some of this may be related to bug #44275. Install notes (demo download link on same page): https://appdb.winehq.org/objectManager.php?sClass=version&iId=31628#notes System tested: Xubuntu 17.04 x86, Intel Pentium D 3.46GHz, GeForce 8600 GT with Nvidia 340.102 driver. wine-staging 2.21.0~zesty from dl.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.

2 6

[Bug 43017] New: Unreal Tournament 2004/UT2004.exe crashes due to " intel_do_flush_locked failed: Cannot allocate memory"
by wine-bugs＠winehq.org 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=43017 Bug ID: 43017 Summary: Unreal Tournament 2004/UT2004.exe crashes due to "intel_do_flush_locked failed: Cannot allocate memory" Product: Wine Version: 2.7 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: krichter(a)posteo.de Distribution: --- Unreal Tournament 2004/UT2004.exe crashes due to `intel_do_flush_locked failed: Cannot allocate memory` the debug output of PlayOnLinux reads ``` [05/12/17 23:55:35] - Running wine-2.7 UT2004.exe (Working directory : /home/richter/.PlayOnLinux/wineprefix/UnrealT2004/drive_c/Program Files/Unreal Tournament 2004/System) err:module:load_builtin_dll failed to load .so lib for builtin L"winebus.sys": libudev.so.0: cannot open shared object file: No such file or directory err:winedevice:async_create_driver failed to create driver L"WineBus": c0000142 fixme:process:GetProcessWorkingSetSize (0xffffffff,0x32e540,0x32e53c): stub fixme:system:SystemParametersInfoW Unimplemented action: 59 (SPI_SETSTICKYKEYS) err:ole:CoGetClassObject class {96749377-3391-11d2-9ee3-00c04f797396} not registered err:ole:CoGetClassObject class {96749377-3391-11d2-9ee3-00c04f797396} not registered err:ole:create_server class {96749377-3391-11d2-9ee3-00c04f797396} not registered err:ole:CoGetClassObject no class object {96749377-3391-11d2-9ee3-00c04f797396} could be created for context 0x7 fixme:win:EnumDisplayDevicesW ((null),0,0x32bc98,0x00000000), stub! fixme:d3d:wined3d_swapchain_set_gamma_ramp Ignoring flags 0x1. err:xvidmode:ComputeGammaFromRamp low-biased gamma ramp (3604), rejected fixme:d3d:wined3d_swapchain_set_gamma_ramp Ignoring flags 0x1. err:xvidmode:ComputeGammaFromRamp low-biased gamma ramp (3604), rejected fixme:imm:ImmReleaseContext (0x1007c, 0x2165e0): stub fixme:hnetcfg:fw_profile_get_FirewallEnabled 0x6404c88, 0x32ccc4 err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_ENUM in glClampColorARB(clamp)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=-1042267284)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1082643741)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1129305379)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=-1017464658)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1106373278)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1061644189)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1103102115)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1102202262)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1127878391)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1133393126)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1064431753)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1056334452)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1103590910)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1128011843)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=-1012511863)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1129177136)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1064579615)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1107545964)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1127492263)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1131588260)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=-1009667614)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1064940315)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1102388947)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1107645235)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1127352012)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1106599611)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1065065837)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1056114040)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1104285584)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1127422744)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=-1029644321)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1126051816)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1065075311)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_ENUM in glClampColorARB(clamp)". intel_do_flush_locked failed: Cannot allocate memory ``` -- 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 54744] New: explorerframe:taskbarlist - test_ITaskbarList() sometimes gets E_NOTIMPL on Windows
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=54744 Bug ID: 54744 Summary: explorerframe:taskbarlist - test_ITaskbarList() sometimes gets E_NOTIMPL on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: explorerframe Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com explorerframe:taskbarlist - test_ITaskbarList() sometimes gets E_NOTIMPL on Windows: taskbarlist.c:61: Test failed: Got hr 0x80004001. taskbarlist.c:66: Test failed: Got hr 0x80004001. See https://test.winehq.org/data/patterns.html#explorerframe:taskbarlist Where 0x80004001 == E_NOTIMPL On average this happens about once every other month on recent Windows 10 versions: * 2022-08-31 on w1064-tsign-64 (21h2) * 2022-11-14 on w1064-tsign-32 (21h2) * 2023-01-10 on fgtb-w10pro64-rx550-64 (22h2) * 2023-02-06 on w10pro64-rx550-64 (22h2) * 2023-03-27 on w10pro64-ar-64 (21h1) -- 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 54069] New: ddraw:ddraw7 - test_texture_wrong_caps() sometimes fails on Windows 8+
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=54069 Bug ID: 54069 Summary: ddraw:ddraw7 - test_texture_wrong_caps() sometimes fails on Windows 8+ Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ddraw:ddraw7 - test_texture_wrong_caps() sometimes fails on Windows 8+. ddraw7.c:18954: Test failed: Got unexpected color 0x00000040. and ddraw7.c:18972: Test failed: Got unexpected color 0x00ff00ff. See https://test.winehq.org/data/patterns.html#ddraw:ddraw7 Notes: * There is no evidence of this happening on Windows 11. * This seems to only happen with Microsoft's "Microsoft Basic Display Adapter" driver: the "-1qxl" and "-2qxl" (dual-monitor) configuration use the "Red Hat QXL controller" driver and are are not affected. Neither are the AMD / NVIDIA PCI passthrough configurations. * The 0x00000040 result mostly happens on Windows 8 to Windows 10 1607 but it also happened a couple of times on Windows 10 21H2. Meanwhile the 0x00ff00ff result seems to only happen on Windows 10 2004+. * ddraw:ddraw1, ddraw:ddraw2 and ddraw:ddraw4 have a similar test function but don't have this failure. -- 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 43185] New: "Battle Bugs" game in unresponsive once game starts
by wine-bugs＠winehq.org 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=43185 Bug ID: 43185 Summary: "Battle Bugs" game in unresponsive once game starts Product: Wine Version: 2.9 Hardware: x86-64 OS: Linux Status: NEW Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: matt(a)nightrealms.com Distribution: --- Created attachment 58457 --> https://bugs.winehq.org/attachment.cgi?id=58457 Wine output from before starting the game When playing the free game "Battle Bugs" (https://ldjam.com/events/ludum-dare/38/battle-bugs) on 64 bit Linux, the game start screen loads just fine, and pressing an indicated key starts the game just fine, but once the game starts nothing is moving and the game doesn't respond to any keys. Got the same results with both versions of the executable, and both WINEARCH unspecified or set to win32 -- 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 6

[Bug 53276] New: user32:edit - test_paste() sometimes fails to access the clipboard on Windows
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=53276 Bug ID: 53276 Summary: user32:edit - test_paste() sometimes fails to access the clipboard on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com user32:edit - test_paste() sometimes fails to access the clipboard on Windows: edit.c:3222: Test failed: expected 1, got 0 le=5 edit.c:3224: Test failed: expected 1, got 0 edit.c:3226: Test failed: expected 00000000008500A8, got 0000000000000000 edit.c:3228: Test failed: expected 1, got 0 edit.c:3234: Test failed: got 21 edit.c:3240: Test failed: got 21 https://test.winehq.org/data/patterns.html#user32:edit Where 5 is ERROR_ACCESS_DENIED and indicates that the clipboard has already been opened in another thread, process, etc. This happens a lot on machines with an AMD GPU due to known interference from the Radeon driver (see bug 47888). But it also happens sometimes on machines with an Nvidia GPU (cw-gtx560) and even on pure QEmu VMs such as w1064-1qxl (or fgtb-w10pro64). So there is either some other source of interference, maybe from some Windows component, or an issue (a race condition?) in the test itself. It would be nice to identify the source of interference, if any, to see if it can be neutralized. But maybe the only solution is to work around the issue as in user32:clipboard (see commit 316eec8f6658). -- 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 54156] New: comctl32:edit & user32:edit - test_paste() sometimes gets an empty string on Windows
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=54156 Bug ID: 54156 Summary: comctl32:edit & user32:edit - test_paste() sometimes gets an empty string on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com comctl32:edit - test_paste() sometimes gets an empty string on Windows edit.c:3238: Test failed: got 0 See https://test.winehq.org/data/patterns.html#comctl32:edit This happens on Windows 10 1809 to 21H2 a bit less than 3 times per month. Where 0 is the length of the string in the field we pasted to. So that field is empty instead of having received the string we pasted. We can also get this failure in user32:edit (2022-11-15 w10pro64v1809): edit.c:3211: Test failed: got 0 See https://test.winehq.org/data/patterns.html#user32:edit But the case above is for the single-line to single-line case and there is also the same issue happening in the multi-line to multi-line case (2022-10-25 w11pro64-amd): edit.c:3240: Test failed: got 0 So it's a pretty general, if rare (only 4 known instances in 6 months), problem. Note that while one could expect this to be caused by yet another OpenClipboard() failure, like in bug 53276, there is no failure message indicating this to be the case. -- 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 54441] New: windows.media.speech:speech - test_Recognition() sometimes gets unexpected recognizer state on Windows 10
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=54441 Bug ID: 54441 Summary: windows.media.speech:speech - test_Recognition() sometimes gets unexpected recognizer state on Windows 10 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com windows.media.speech:speech - test_Recognition() sometimes gets unexpected recognizer state on Windows 10: speech.c:1775: Test failed: recog_state was 0. See https://test.winehq.org/data/patterns.html#windows.media.speech:speech This failure started on 2023-01-25. -- 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