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

[Bug 54143] New: Chessbase 11 arrows draw too large
by WineHQ Bugzilla 29 Aug '23

29 Aug '23

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 29 Aug '23

29 Aug '23

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 55006] New: vbscript single line if else without else body fails compilation
by WineHQ Bugzilla 29 Aug '23

29 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55006 Bug ID: 55006 Summary: vbscript single line if else without else body fails compilation Product: Wine Version: unspecified Hardware: aarch64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: vbscript Assignee: wine-bugs(a)winehq.org Reporter: francisdb(a)gmail.com This is valid vbs when run with `cscript` ``` If x = 1 Then DoSomething() Else ``` wine vbscript fails with: "Compile error: Line: #, Character: #, Description unavailable" Workaround is changing the code to ``` If x = 1 Then DoSomething() Else: ``` or ``` If x = 1 Then DoSomething() ``` -- 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 53371] New: 0024:fixme:ntdll:create_logical_proc_info stub
by WineHQ Bugzilla 27 Aug '23

27 Aug '23

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 25 Aug '23

25 Aug '23

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 51678] New: Avogadro crashes when adding atoms
by WineHQ Bugzilla 25 Aug '23

25 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=51678 Bug ID: 51678 Summary: Avogadro crashes when adding atoms Product: Wine Version: 6.15 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Just install, open the program (avogadro.exe) and click two times into the black 3D part of the window. Wine crashes with something like "Unhandled page fault on read access to 8010C497 at address 72A562D3" -- 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 55204] New: ws2_32:sock - test_close_events() sometimes misses the close event on Windows
by WineHQ Bugzilla 25 Aug '23

25 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55204 Bug ID: 55204 Summary: ws2_32:sock - test_close_events() sometimes misses the close event on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ws2_32:sock - test_close_events() sometimes misses the close event on Windows: sock.c:6845: Test failed: got events 0 sock.c:6858: Test failed: got -1 sock.c:6872: Test failed: got events 0 sock.c:6890: Test failed: expected timeout See https://test.winehq.org/data/patterns.html#ws2_32:sock This happened 9 times in the past 8 months, mostly on Windows 7 but it did happen once on Windows 10: * 2022-12-14 win7_newtb-w7u-adm * 2023-02-08 win22H2_fgtb-w10pro64-64 * 2023-02-22 win7_newtb-w7u-de * 2023-03-17 win7_newtb-w7u-de * 2023-03-27 win7_newtb-w7u-2qxl * 2023-03-27 win7_newtb-w7u * 2023-05-04 win7_newtb-w7u * 2023-05-10 win7_newtb-w7u-es * 2023-06-29 win7_newtb-w7u There are also two cases where the second events check does get an FD_CLOSE event: sock.c:6697: Test failed: got events 0 sock.c:6710: Test failed: got -1 sock.c:6712: Test failed: expected timeout sock.c:6712: Test failed: got events 0x20 * 2022-11-28 win21H1_newtb-w10pro64-he-64 * 2023-02-27 win22H2_fgtb-w10pro64-rx550-64 -- 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 53939] New: TextOut will output ASCII control character（0～31） as tofu cause crash
by WineHQ Bugzilla 24 Aug '23

24 Aug '23

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

[Bug 45329] New: Fresh steam install will not install games -- error: " content servers unreachable"
by wine-bugs＠winehq.org 24 Aug '23

24 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=45329 Bug ID: 45329 Summary: Fresh steam install will not install games -- error: "content servers unreachable" Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alasky(a)codeweavers.com Distribution: --- Created attachment 61617 --> https://bugs.winehq.org/attachment.cgi?id=61617 Steam error dialogue box Ubuntu 18.04 Wine tip (most recent commit is 83f845dfa1bb4a6ec6e8b7f65e9469dc9a8a7787) When attempting to install a game on a fresh Steam install, an error comes up that says "content servers unreachable." The servers are not down and I am able to install games correctly on my steam account not using wine. This issue seems to be caused by an update on Steam's side. -- 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 42

[Bug 54761] New: D3D12CreateDevice no longer in ABI of libvkd3d-utils.so.1
by WineHQ Bugzilla 23 Aug '23

23 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=54761 Bug ID: 54761 Summary: D3D12CreateDevice no longer in ABI of libvkd3d-utils.so.1 Product: vkd3d Version: 1.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: vkd3d Assignee: wine-bugs(a)winehq.org Reporter: smcv(a)collabora.com Distribution: --- While looking at updating Debian's vkd3d package from 1.2 to 1.7, I noticed that `D3D12CreateDevice(a)VKD3D_1_0` disappeared from the ABI of libvkd3d-utils.so.1. Was this intentional? (D3D12CreateDeviceVKD3D(a)VKD3D_1_0 is still there, but if I'm understanding the intention of this library correctly, D3D12CreateDevice(a)VKD3D_1_0 should have continued to be present for backwards compat with older library binaries.) -- 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