wine-bugs July 2023

wine-bugs@winehq.org

1 participants
3313 discussions

[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 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 55273] New: ntdll:wow64 - The 64-bit test_cpu_area() gets bad offsets on Windows 10 1607 & 1709
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55273 Bug ID: 55273 Summary: ntdll:wow64 - The 64-bit test_cpu_area() gets bad offsets on Windows 10 1607 & 1709 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:wow64 - The 64-bit test_cpu_area() gets bad offsets on Windows 10 1607 & 1709: wow64.c:783: Test failed: 0:0: wrong offset 4 wow64.c:783: Test failed: 0:1: wrong offset 6 wow64.c:783: Test failed: 0:2: wrong offset 4 wow64.c:783: Test failed: 0:3: wrong offset 6 wow64.c:783: Test failed: 0:4: wrong offset 4 wow64.c:783: Test failed: 0:5: wrong offset 6 wow64.c:783: Test failed: 0:6: wrong offset 4 wow64.c:783: Test failed: 0:7: wrong offset 6 wow64.c:783: Test failed: 1:0: wrong offset 16 wow64.c:783: Test failed: 1:1: wrong offset 14 wow64.c:783: Test failed: 1:2: wrong offset 12 wow64.c:783: Test failed: 1:3: wrong offset 10 wow64.c:783: Test failed: 1:4: wrong offset 8 wow64.c:783: Test failed: 1:5: wrong offset 6 wow64.c:783: Test failed: 1:6: wrong offset 4 wow64.c:783: Test failed: 1:7: wrong offset 18 wow64.c:783: Test failed: 2:0: wrong offset 8 wow64.c:783: Test failed: 2:1: wrong offset 6 wow64.c:783: Test failed: 2:2: wrong offset 4 wow64.c:783: Test failed: 2:3: wrong offset 10 wow64.c:783: Test failed: 2:4: wrong offset 8 wow64.c:783: Test failed: 2:5: wrong offset 6 wow64.c:783: Test failed: 2:6: wrong offset 4 wow64.c:783: Test failed: 2:7: wrong offset 10 wow64.c:783: Test failed: 3:0: wrong offset 16 wow64.c:783: Test failed: 3:1: wrong offset 14 wow64.c:783: Test failed: 3:2: wrong offset 12 wow64.c:783: Test failed: 3:3: wrong offset 10 wow64.c:783: Test failed: 3:4: wrong offset 8 wow64.c:783: Test failed: 3:5: wrong offset 6 wow64.c:783: Test failed: 3:6: wrong offset 4 wow64.c:783: Test failed: 3:7: wrong offset 18 See https://test.winehq.org/data/patterns.html#ntdll:wow64 The failures started with GitLab CI's switch to Debian 12 for the WineTest builds which are used in the WineTest nightlies. However they also happen with binaries built on Debian 11 so in this case it is just a coincidence. See also bug 55272 for ntdll:exception crashes that started at the same time on the same set of machines. -- 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 55211] New: Print file not truncated when printing to file in FrameMaker 8
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55211 Bug ID: 55211 Summary: Print file not truncated when printing to file in FrameMaker 8 Product: Wine Version: 8.12 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: spooler Assignee: wine-bugs(a)winehq.org Reporter: ulrich.gemkow(a)ikr.uni-stuttgart.de Distribution: --- A existing print file ist not truncated when printing to the same file again. So when printing a smaller document to the print file which was generated for a larger file, the resultung file contains garbage at its end. This happens in Framemaker 8 and may happen in other apps too. To reproduce - Install Framemaker from the given URL - Print the attached Document Large.fm to a file (select print to file in the printer dialog). Check the size of the generated file. - Print the attached Document Small.fm to the same file generated in the previous step. Check again the size of the file - its the same. Depending on the used Postscript interpreter reading the file fails because of the garbage at the files end. This is simple to see when using different documents as descibed above. When printing existing documents again after (even small) changes the resulting print file may be garbage without notice. -- 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 13

[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 55236] New: scrrun:dictionary - test_hash_value() gets bad hashes on Windows
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55236 Bug ID: 55236 Summary: scrrun:dictionary - test_hash_value() gets bad hashes on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: scrrun Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com scrrun:dictionary - test_hash_value() gets bad hashes on Windows: dictionary.c:676: Test failed: got hash 0x2eb, expected 0x2ea dictionary.c:686: Test failed: got hash 0x2eb, expected 0x2ea dictionary.c:695: Test failed: got hash 0x2db, expected 0x2da dictionary.c:721: Test failed: got hash 0x2eb, expected 0x2ea dictionary.c:732: Test failed: got hash 0x2eb, expected 0x2ea dictionary.c:742: Test failed: got hash 0x2db, expected 0x2da See https://test.winehq.org/data/patterns.html#scrrun:dictionary Note that the hash values change with every run causing false positives. -- 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 54791] New: explorerframe:nstc - test_events() sometimes gets unexpected events on Windows 7
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=54791 Bug ID: 54791 Summary: explorerframe:nstc - test_events() sometimes gets unexpected events on Windows 7 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:nstc - test_events() sometimes gets unexpected events on Windows 7. This can either be a single event but it can also happen multiple times for multiple events: nstc.c:2265: Test failed: Got event 4, count 1 or nstc.c:1906: Test failed: Got event 7, count 0 nstc.c:1908: Test failed: Got event 4, count 0 nstc.c:1912: Test failed: Got event 4, count 1 nstc.c:1912: Test failed: Got event 7, count 1 nstc.c:1912: Test failed: Got event 12, count 8 See https://test.winehq.org/data/patterns.html#explorerframe:nstc This first happened on 2022-12-07 and has been happening roughly once every three week since. So it's probably caused by a commit in the fall of 2022. -- 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

[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

Jump to page:

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 July 2023