April 2023 - Wine-Bugs - list.winehq.org

[Bug 54758] New: shell32:progman_dde - test_parser() sometimes gets DMLERR_NOTPROCESSED in Wine
by WineHQ Bugzilla Aug. 31, 2023

Aug. 31, 2023

https://bugs.winehq.org/show_bug.cgi?id=54758 Bug ID: 54758 Summary: shell32:progman_dde - test_parser() sometimes gets DMLERR_NOTPROCESSED in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- shell32:progman_dde - test_parser() sometimes gets DMLERR_NOTPROCESSED in Wine: progman_dde.c:274: Test failed: expected DMLERR_NO_ERROR, got 16393 progman_dde.c:275: Test failed: directory should not exist See https://test.winehq.org/data/patterns.html#shell32:progman_dde Where 16393 == DMLERR_NOTPROCESSED The first known instance happened on 2023-03-02: this did not happen in the previous 6 months. Since then there has been a bit over 1 instance per week so it seems likely this is caused by a commit in late February: * 2023-03-02 on debian11-win32-ar-MA * 2023-03-03 on fgtb-debian11-win32 * 2023-03-10 in MR!2368 on debian11-win32 * 2023-03-22 in MR!2466 in the test-linux32 GitLab CI * 2023-03-28 in MR!2526 on debian11-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.

1 2

[Bug 53505] New: d3d9:visual - test_vshader_input() sometimes fails on Windows <= 10 1607
by WineHQ Bugzilla Aug. 31, 2023

Aug. 31, 2023

https://bugs.winehq.org/show_bug.cgi?id=53505 Bug ID: 53505 Summary: d3d9:visual - test_vshader_input() sometimes fails on Windows <= 10 1607 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 d3d9:visual - test_vshader_input() sometimes fails on Windows <= 10 1607: visual.c:8907: Test failed: Input test: Quad 3(2crd-wrongidx) returned color 0x00ff00ff, expected 0x00ff0080 https://test.winehq.org/data/patterns.html#d3d9:visual This happens on Windows 8, Windows 10 1507 and 1607 but is rare enough (~7%) to sometimes cause 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 5

[Bug 53385] New: Vulkan was running really fine, before MESA/Xorg Update last month, current version crashes
by WineHQ Bugzilla Aug. 31, 2023

Aug. 31, 2023

https://bugs.winehq.org/show_bug.cgi?id=53385 Bug ID: 53385 Summary: Vulkan was running really fine, before MESA/Xorg Update last month, current version crashes Product: vkd3d Version: 1.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: vkd3d Assignee: wine-bugs(a)winehq.org Reporter: juergen.sauer(a)automatix.de Distribution: --- I was using dxvk-bin in Arch Linux. [jojo(a)pc7 wotlk]$ cd /usr/share/dxvk/ [jojo(a)pc7 dxvk]$ ./setup_dxvk.sh install This worked over years like a charm, rocksteady. Since a month ago, I got: [jojo(a)pc7 wotlk]$ wine Wow.exe .. info: Game: Wow.exe info: DXVK: v1.10.2 info: Built-in extension providers: info: Win32 WSI info: OpenVR info: OpenXR info: OpenVR: could not open registry key, status 2 info: OpenVR: Failed to locate module info: Enabled instance extensions: info: VK_KHR_get_surface_capabilities2 info: VK_KHR_surface info: VK_KHR_win32_surface terminate called after throwing an instance of 'dxvk::DxvkError' abnormal program termination wine-7.13 (Staging) ... uninstalling dxvk-bin -> game works again, but it runs sometimes in Wow Errors accordinf the OpenGL Stack. You can reproduce on Arch Linux, current update, wine-staging, running Wow WoW_3.3.5a_rising-gods.de. Client avaible via rising-gods.de -- 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

[Bug 54785] New: ole32:compobj - test_CoWaitForMultipleHandles() sometimes does not receive WM_USER on Windows
by WineHQ Bugzilla Aug. 30, 2023

Aug. 30, 2023

https://bugs.winehq.org/show_bug.cgi?id=54785 Bug ID: 54785 Summary: ole32:compobj - test_CoWaitForMultipleHandles() sometimes does not receive WM_USER on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ole32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ole32:compobj - test_CoWaitForMultipleHandles() sometimes does not receive WM_USER on Windows. There are two places where this can happen: compobj.c:2999: Test failed: expected message 1024, received none and compobj.c:3034: Test failed: expected message 1024, received none See https://test.winehq.org/data/patterns.html#ole32:compobj This failure impacts all Windows version but still only happens once every other month on average: * 2022-12-09 on fgtb-w10pro64-rx550-64 * 2023-01-24 on fgtb-w10pro64-rx550-64 * 2023-03-10 on w7u-pt-PT * 2023-04-04 on w7u-de * 2022-08-28 on w1064-tsign-32 This is a slightly different case because compobj received an unexpected WM_DEVICECHANGE message instead of no message: compobj.c:3000: Test failed: unexpected message 537 compobj.c:3034: Test failed: expected message 1024, received 537 compobj.c:3035: Test failed: unexpected message 1024 -- 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

[Bug 35336] New: HoMM 3: Horn of the Abyss launcher freezes on the game update (Mono issue)
by wine-bugs＠winehq.org Aug. 30, 2023

Aug. 30, 2023

http://bugs.winehq.org/show_bug.cgi?id=35336 Bug ID: 35336 Summary: HoMM 3: Horn of the Abyss launcher freezes on the game update (Mono issue) Product: Wine Version: 1.7.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: winebugs140(a)gmail.com Classification: Unclassified How to reproduce: open HotA_launcher.exe and then click on Update HotA. If you try to cancel the update or there will be no updates available, the application freezes. With 'winetricks dotnet30' the launcher works fine, so it looks like a problem with Mono. You DON'T NEED Heroes of Might & Magic 3 to test this, you can open the launcher of this unofficial expansion without downloading the original game. There is nothing in the logs. TESTED ON: Ubuntu 13.04 and Mac OS X 10.9 Mavericks -- 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 22

[Bug 54143] New: Chessbase 11 arrows draw too large
by WineHQ Bugzilla Aug. 29, 2023

Aug. 29, 2023

https://bugs.winehq.org/show_bug.cgi?id=54143 Bug ID: 54143 Summary: Chessbase 11 arrows draw too large Product: Wine Version: 8.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdiplus Assignee: wine-bugs(a)winehq.org Reporter: dav75uk(a)yahoo.co.uk Distribution: --- Created attachment 73675 --> https://bugs.winehq.org/attachment.cgi?id=73675 Picture of arrow on wine8.0-rc1 When arrows are drawn using Chessbase 11, they are too big. See attached screenshot and log. Compare with: https://www.youtube.com/watch?v=xvJd97ZnHAk At 4:58 an arrow is showing from g8 to f6 pointing to a knight that has just moved. I've also set up this arrow on chessbase 11 with wine 8.0-rc1. Note later chessbase draws arrows slightly different, so software like CBReader14 doesn't appear to be affecting by this issue. On wine 8.0-rc1 in CB 11 the stem of the arrow looks approx in the right place. It crosses f7/g7 (the squares occupied by pawns) at the right point. The tip of the arrow is in the right place on the knight between the white on the mane and the chin. On wine 7.22 the endcap square (some default catch in a switch statement maybe) is being drawn which is not on native chessbase (thus the arrow isn't meant to hide it). Finally the back of the arrow head is in the wrong place (some scaling maybe?) which is making it too large. On wine 7.22 the back of the arrow is drawn from the right shoulder of the pawn on f7 (the one nearest the king) to near (left of) the base of the one on g7. In the video the arrow appears from under the base of the f7 pawn (almost but not quite lined up horizontally the bishop on f8's cross right hand edge) to just inside the corner of the square the knight is on. -- 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 17

[Bug 51890] New: A lot more old games would be so much more usable if wine's virtual desktop had proper resizing
by WineHQ Bugzilla Aug. 29, 2023

Aug. 29, 2023

https://bugs.winehq.org/show_bug.cgi?id=51890 Bug ID: 51890 Summary: A lot more old games would be so much more usable if wine's virtual desktop had proper resizing Product: Wine-staging Version: 6.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: el(a)horse64.org CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- I have a really significant amount of older games around, none of which will launch on this machine without wine's virtual desktop feature because on a widescreen monitor, they determine there is no "expected" fullscreen resolution available and crash. Now I'd just use the virtual desktop, except it feels archaic and not very usable: why is it that for a 800x600 game on a 800x600 virtual desktop, I can't just maximize the virtual desktop window and get the virtual desktop SCALED UP with proper letterboxing so I can play in some other way than a tiny window with zero immersion and everything so small I can barely see it? Funnily enough I can even resize the virtual desktop window except the resizing is fully ignored and I just get black void with no scaling up all around with the game stuck in the top-left, and the maximizing is blocked. Scaling up (with automatic letterboxing), maximizing would seem like such obvious features to make virtual desktop gaming infinitely less clumsy and weird that I am a bit surprised it's not in there yet. Can it please be added?? -- 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 53371] New: 0024:fixme:ntdll:create_logical_proc_info stub
by WineHQ Bugzilla Aug. 27, 2023

Aug. 27, 2023

https://bugs.winehq.org/show_bug.cgi?id=53371 Bug ID: 53371 Summary: 0024:fixme:ntdll:create_logical_proc_info stub Product: Wine Version: 7.12 Hardware: x86-64 OS: FreeBSD Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: yklaxds(a)gmail.com Created attachment 72755 --> https://bugs.winehq.org/attachment.cgi?id=72755 log FreeBSD 13.1 release amd64 KDE plasma 5 emulators/wine-devel 7.12 not work at all. -- 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 52235] New: Many surfaces in the game Obduction look black
by WineHQ Bugzilla Aug. 25, 2023

Aug. 25, 2023

https://bugs.winehq.org/show_bug.cgi?id=52235 Bug ID: 52235 Summary: Many surfaces in the game Obduction look black Product: Wine Version: 7.0-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: zerooneo(a)01101001.net Distribution: --- Created attachment 71338 --> https://bugs.winehq.org/attachment.cgi?id=71338 Screenshot When running the game Obduction in wine, an interesting effect occurs where most surfaces are pure black, yet with some lighting etc. applied, leaving the game looking extremely dark. This effect does not occur when running the game with DXVK, meaning there's a very specific difference the two implementations that has a large effect on this game. The log shows a few DirectX and Direct3D-messages initially (counts on the left): 1 03d8:fixme:dxgi:DXGID3D10CreateDevice Ignoring flags 0x1. 1 03d8:fixme:dxgi:DXGID3D10CreateDevice Ignoring flags 0x20. 1 03d8:fixme:dxgi:dxgi_output_GetDisplayModeList iface 0x12d2cad0, format DXGI_FORMAT_R8G8B8A8_UNORM, flags 0, mode_count 0x4e8d30, modes 0x7fe90cc3ac00 partial stub! 1 03d8:fixme:dxgi:dxgi_output_GetDisplayModeList iface 0x12d2cad0, format DXGI_FORMAT_R8G8B8A8_UNORM, flags 0, mode_count 0x4e8d30, modes (nil) partial stub! 1 03d8:fixme:dxgi:dxgi_output_GetDisplayModeList iface 0xed354e0, format DXGI_FORMAT_R8G8B8A8_UNORM, flags 0, mode_count 0x4e8ad0, modes 0x18fa4d80 partial stub! 1 03d8:fixme:dxgi:dxgi_output_GetDisplayModeList iface 0xed354e0, format DXGI_FORMAT_R8G8B8A8_UNORM, flags 0, mode_count 0x4e8ad0, modes (nil) partial stub! 1 03d8:fixme:dxgi:dxgi_output_GetDisplayModeList iface 0xed39050, format DXGI_FORMAT_R8G8B8A8_UNORM, flags 0, mode_count 0x4e8ab0, modes 0x1aece780 partial stub! 1 03d8:fixme:dxgi:dxgi_output_GetDisplayModeList iface 0xed39050, format DXGI_FORMAT_R8G8B8A8_UNORM, flags 0, mode_count 0x4e8ab0, modes (nil) partial stub! 1 03d8:fixme:dxgi:dxgi_output_GetDisplayModeList iface 0xf0f51c0, format DXGI_FORMAT_R8G8B8A8_UNORM, flags 0, mode_count 0x4e8d50, modes 0x1af84680 partial stub! 1 03d8:fixme:dxgi:dxgi_output_GetDisplayModeList iface 0xf0f51c0, format DXGI_FORMAT_R8G8B8A8_UNORM, flags 0, mode_count 0x4e8d50, modes (nil) partial stub! 2 04a8:fixme:d3d:create_texture_view Depth slice (0-1) not supported. 10 04a8:fixme:d3d_shader:shader_glsl_handle_instruction Backend can't handle opcode dcl_stream. 46 03d8:fixme:d3d11:d3d11_device_CheckFeatureSupport Unhandled feature 0x3. 432 04a8:fixme:d3d_shader:shader_glsl_interpolation_qualifiers Unhandled interpolation mode 0x3. And then thousands of these: 1080 04a8:err:d3d:wined3d_debug_callback 0x578c00: "GL_INVALID_ENUM in glTexBufferRange(internalFormat GL_RGBA16_SNORM)". 4632 04a8:err:d3d:wined3d_debug_callback 0x578c00: "GL_INVALID_ENUM in glTexBufferRange(internalFormat GL_RGBA8_SNORM Might it be that certain textures or shaders aren't supported, and that that leads to them being rendered as black? This game also requires some other features in order to work fully, but it might be worth it to fix this issue either for the sake of other games, or in case further support for this game is added in the future. -- 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 53939] New: TextOut will output ASCII control character（0～31） as tofu cause crash
by WineHQ Bugzilla Aug. 24, 2023

Aug. 24, 2023

https://bugs.winehq.org/show_bug.cgi?id=53939 Bug ID: 53939 Summary: TextOut will output ASCII control character（0～31） as tofu cause crash Product: Wine Version: 7.12 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: 399989567(a)qq.com Distribution: --- TextOut will output ASCII control character（0～31） as tofu cause crash build a string on windows > static WCHAR str[] = {0x1c,0x30,0x31,0x32,0} use TextOut(hdc,x,y,str,wcslen(str)) to output this str on windows: output is "012" on wine : output is "?012" The reason is that this API does not filter ASCII control characters, and treats the control characters as an ordinary character to output. by the way if we fillter the control character we alse need fix the API :GetTextExtentExPointW Because my program uses control characters, there will be problems when calculating the length, resulting in a crash. If I filter out the control characters in the code myself, it will not crash. And in principle, the focus should be on whether control characters should be output -- 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 8