wine-bugs November 2023

wine-bugs@winehq.org

1 participants
2714 discussions

[Bug 54037] New: user32:msg - test_SendMessage_other_thread() sometimes gets a todo success (GitLab CI)
by WineHQ Bugzilla 08 Dec '23

08 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=54037 Bug ID: 54037 Summary: user32:msg - test_SendMessage_other_thread() sometimes gets a todo success (GitLab CI) Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- user32:msg - test_SendMessage_other_thread() sometimes gets a todo success: msg.c:19067: Test succeeded inside todo block: WaitForSingleObject failed, ret:0 msg.c:19091: Test succeeded inside todo block: wrong status 00000000 See https://test.winehq.org/data/patterns.html#user32:msg This happens about once a month on the Debian VMs in the TestBot nightly WineTest runs, but is also known to impact the GitLab CI (e.g. MR!1596 MR!1519 ). -- 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 53175] New: Roon no longer works under wine staging, help needed, thanks.
by WineHQ Bugzilla 08 Dec '23

08 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=53175 Bug ID: 53175 Summary: Roon no longer works under wine staging, help needed, thanks. Product: Wine-staging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rustytone(a)gmx.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 72621 --> https://bugs.winehq.org/attachment.cgi?id=72621 backtrace of the roon application - failed start, get it every time i launch. hello sorry if this in the wrong section, I have roon installed using wine-staging, the wine (non staging) doesn't seem to work well with the roon windows application so decided to go with staging release. it was working correctly until 2 days ago, there was an update to wine-staging and an update to the roon application as well. hopefully the backtrace is helpful and I have included it, running arch, latest updates, latest kernel, latest wine-staging etc. any more information you need I will be happy to assist. sorry again if this in the wrong section. thank you - antonio. -- 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 49527] New: Printing font Chilanka crashes Notepad and Word
by WineHQ Bugzilla 08 Dec '23

08 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=49527 Bug ID: 49527 Summary: Printing font Chilanka crashes Notepad and Word Product: Wine Version: 5.12 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wineps.drv Assignee: wine-bugs(a)winehq.org Reporter: bernhardu(a)mailbox.org Distribution: --- Created attachment 67657 --> https://bugs.winehq.org/attachment.cgi?id=67657 Avoid crash in get_glyf_pos in wineps.drv with font Chilanka. Function get_glyf_pos accesses unconditionally the memory pointed to by ".data". Unfortunately with this font we end up here with a null pointer. 123 *start = GET_BE_WORD(((WORD*)t42->tables[t42->loca_tab].data) + index); I could observe this with following font: fonts-smc-chilanka_1.400-1_all.deb from Ubuntu focal (20.04LTS). https://packages.ubuntu.com/focal/fonts-smc-chilanka http://de.archive.ubuntu.com/ubuntu/pool/main/f/fonts-smc-chilanka/fonts-sm… To reproduce just enter "Test" and select font "Chilanka" in either Notepad or Word. Then attempt to print. Attached path on top of 5.12 avoids the crash, but does still not produce the expected output, maybe related to 42739. But avoiding the crash separately might still be desired? -- 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 55807] New: uiautomationcore:uiautomation - test_uia_com_event_handler_event_advisement() fails on Windows 10 1709
by WineHQ Bugzilla 08 Dec '23

08 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=55807 Bug ID: 55807 Summary: uiautomationcore:uiautomation - test_uia_com_event_handler_event_advisement() fails on Windows 10 1709 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: uiautomationcore Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com uiautomationcore:uiautomation - test_uia_com_event_handler_event_advisement() fails on Windows 10 1709: uiautomation.c:15492: Test failed: Wait for method_event(s) timed out. uiautomation.c:15498: Test failed: Provider2: Unexpected advise event added, event ID 0. See https://test.winehq.org/data/patterns.html#uiautomationcore:uiautomation These failures started on 2023-10-10 and are systematic but only happen on w1064v1709. A bisect shows that they started with the commit below: commit 4569157b282f0274bb774795f207a25822105065 Author: Connor McAdams <cmcadams(a)codeweavers.com> Date: Tue Oct 10 07:39:11 2023 -0400 uiautomationcore: Use EVENT_OBJECT_DESTROY to remove HWNDs from the COM API focus change HWND map. Signed-off-by: Connor McAdams <cmcadams(a)codeweavers.com> -- 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 55591] New: Castlevania: Lords of Shadow 2 has rendering glitches
by WineHQ Bugzilla 08 Dec '23

08 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=55591 Bug ID: 55591 Summary: Castlevania: Lords of Shadow 2 has rendering glitches Product: Wine Version: 7.2 Hardware: x86-64 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com CC: z.figura12(a)gmail.com Regression SHA1: 1b1b03055db8bf03c6783d4fcb19abf670d53338 Distribution: --- Created attachment 75118 --> https://bugs.winehq.org/attachment.cgi?id=75118 example Doesn't matter what graphics settings are used. -- 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 55744] New: psapi:psapi_main fails on Debian 11
by WineHQ Bugzilla 08 Dec '23

08 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=55744 Bug ID: 55744 Summary: psapi:psapi_main fails on Debian 11 Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: psapi Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- psapi:psapi_main fails on Debian 11: Pure 32-bit case: psapi_main.c:105: Test failed: hMod=7BD20000 GetModuleHandleA(NULL)=00400000 psapi_main.c:121: Test failed: hMod=7BD20000 GetModuleHandleA(NULL)=00400000 psapi_main.c:406: Test failed: hMod=7BD20000 GetModuleHandleA(NULL)=00400000 psapi_main.c:1018: Test failed: szModExPath="C:\windows\system32\ntdll.dll" szModPath="C:\users\winetest\Temp\wct\psapi_test.exe" psapi_main.c:1079: Test failed: szModPath="C:\users\winetest\Temp\wct\psapi_test.exe" szModBaseName="ntdll.dll" 64-bit Windows-on-Windows: psapi_main.c:105: Test failed: hMod=00006FFFFFC60000 GetModuleHandleA(NULL)=0000000000400000 psapi_main.c:121: Test failed: hMod=00006FFFFFC60000 GetModuleHandleA(NULL)=0000000000400000 psapi_main.c:163: Test failed: got ntdll.dll psapi_main.c:167: Test failed: got C:\windows\system32\ntdll.dll psapi_main.c:406: Test failed: hMod=00006FFFFFC60000 GetModuleHandleA(NULL)=0000000000400000 psapi_main.c:346: Test failed: self: 2: expecting psapi_test.exe but got ntdll.dll psapi_main.c:349: Test failed: self: 2: expecting C:\users\winetest\Temp\wct\psapi_test.exe but got C:\windows\system32\ntdll.dll psapi_main.c:346: Test failed: self: 0: expecting psapi_test.exe but got ntdll.dll psapi_main.c:349: Test failed: self: 0: expecting C:\users\winetest\Temp\wct\psapi_test.exe but got C:\windows\system32\ntdll.dll psapi_main.c:346: Test failed: self: 3: expecting psapi_test.exe but got ntdll.dll psapi_main.c:349: Test failed: self: 3: expecting C:\users\winetest\Temp\wct\psapi_test.exe but got C:\windows\system32\ntdll.dll psapi_main.c:346: Test failed: pcs-6464: 2: expecting msinfo32.exe but got ntdll.dll psapi_main.c:349: Test failed: pcs-6464: 2: expecting C:\windows\system32\msinfo32.exe but got C:\windows\system32\ntdll.dll psapi_main.c:346: Test failed: pcs-6464: 0: expecting msinfo32.exe but got ntdll.dll psapi_main.c:349: Test failed: pcs-6464: 0: expecting C:\windows\system32\msinfo32.exe but got C:\windows\system32\ntdll.dll psapi_main.c:346: Test failed: pcs-6464: 3: expecting msinfo32.exe but got ntdll.dll psapi_main.c:349: Test failed: pcs-6464: 3: expecting C:\windows\system32\msinfo32.exe but got C:\windows\system32\ntdll.dll psapi_main.c:519: Test failed: pcs-6432: default and all module list should match psapi_main.c:346: Test failed: pcs-6432: 1: expecting msinfo32.exe but got ntdll.dll psapi_main.c:349: Test failed: pcs-6432: 1: expecting C:\windows\syswow64\msinfo32.exe but got C:\windows\system32\ntdll.dll psapi_main.c:346: Test failed: pcs-6432: 0: expecting msinfo32.exe but got ntdll.dll psapi_main.c:349: Test failed: pcs-6432: 0: expecting C:\windows\syswow64\msinfo32.exe but got C:\windows\system32\ntdll.dll psapi_main.c:346: Test failed: pcs-6432: 3: expecting msinfo32.exe but got ntdll.dll psapi_main.c:349: Test failed: pcs-6432: 3: expecting C:\windows\syswow64\msinfo32.exe but got C:\windows\system32\ntdll.dll psapi_main.c:1018: Test failed: szModExPath="C:\windows\system32\ntdll.dll" szModPath="C:\users\winetest\Temp\wct\psapi_test.exe" psapi_main.c:1079: Test failed: szModPath="C:\users\winetest\Temp\wct\psapi_test.exe" szModBaseName="ntdll.dll" See https://test.winehq.org/data/patterns.html#psapi:psapi_main A bisect shows that these failures started with the commit below: commit de81e2ea41b27a14f88177639c5b5d35a210b5bd Author: Alexandre Julliard <julliard(a)winehq.org> AuthorDate: Fri Oct 6 15:08:02 2023 +0200 ntdll: Only create the main module on the 32-bit side for wow64. -- 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 53905] New: widl: support MIDL 3.0 and WinMD output
by WineHQ Bugzilla 06 Dec '23

06 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=53905 Bug ID: 53905 Summary: widl: support MIDL 3.0 and WinMD output Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: UNCONFIRMED Severity: normal Priority: P2 Component: tools Assignee: wine-bugs(a)winehq.org Reporter: alvin(a)alvinhc.com C++/WinRT (cppwinrt): https://github.com/microsoft/cppwinrt It is currently impossible to build the custom components in the cppwinrt test suite with mingw-w64. For this to work, widl needs to: - understand MIDL 3.0 syntax, - generate the ABI header (not required if only using C++/WinRT projection), - produce .winmd metadata of the component, - read existing system .winmd metadata (not sure if actually needed). The MIDL command line for this: midl.exe /metadata_dir C:\Windows\System32\WinMetadata /winrt /winmd "D:\a\cppwinrt\cppwinrt\_build\x64\Debug\test_component.winmd" /h "D:\a\cppwinrt\cppwinrt\_build\x64\Debug\test_component.h" /ns_prefix /nomidl test_component.idl ## MIDL 3.0 https://learn.microsoft.com/en-us/uwp/midl-3/intro What I can tell is missing widl so far: - MIDL 3.0 uses different basic type names (e.g. Int32, String) - Attribute types, and using custom attributes Example file: https://github.com/microsoft/cppwinrt/blob/5ca626adae21be363399b44d2b6a9ab3… > widl --winrt -h -H out/test_component.h --ns_prefix test_component.idl test_component.idl:5: error: syntax error, unexpected aIDENTIFIER, expecting ',' or ']' (widl version 7.7 from mingw-w64) ## WinMD metadata https://learn.microsoft.com/en-us/uwp/winrt-cref/winmd-files These are CLR (think .NET and ECMA 335) assemblies used as a replacement for the old typelib files. -- 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 1

[Bug 41977] New: Gunner3 always crashes due to wine having a different allocation scheme than windows
by wine-bugs＠winehq.org 04 Dec '23

04 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=41977 Bug ID: 41977 Summary: Gunner3 always crashes due to wine having a different allocation scheme than windows Product: Wine Version: 1.9.24 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: ArchLinux Created attachment 56382 --> https://bugs.winehq.org/attachment.cgi?id=56382 Hack to get the game working, patch for the exe Gunner 3 always crashes when selecting a level. According to my debugging, it's because the game allocates memory with RtlAllocateHeap and then accesses the area before that, aka undefined behavior. But note that it works just fine on all windows versions and ReactOS. It's probably WONTFIX, but since it works on windows I'll provide a hack (and maybe a patch) for usage on linux. Attached an patch for the gunner3.exe, make sure it has the MD5 4481bc4382bb00353edf0635516d904d. -- 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 55925] New: StarOffice 4.0 crashes on start
by WineHQ Bugzilla 04 Dec '23

04 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=55925 Bug ID: 55925 Summary: StarOffice 4.0 crashes on start Product: Wine Version: 8.20 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Created attachment 75485 --> https://bugs.winehq.org/attachment.cgi?id=75485 WINEDEBUG=+ole Steps to reproduce: 1. Run `SETUP.EXE` (straightforward even if you don't know German) 2. Run `wine 'C:\office40\soffice.exe'` This looked suspicious: 0114:trace:ole:StgOpenStorage16 (c:\office40\config\soffice.cfg,00000000,0x00000040,00000000,0,02D7F530) 0114:warn:ole:StgOpenStorage16 Couldn't open file for storage $ sha256sum SETUP.EXE 68f4fa4f1b2cc18056190c8082dacf4d8e296b4aec97527bb5b52eafabf6c699 -- 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 29255] New: Microsoft Office 2003, 2007 & 2010 applications do not print OTF
by wine-bugs＠winehq.org 04 Dec '23

04 Dec '23

http://bugs.winehq.org/show_bug.cgi?id=29255 Bug #: 29255 Summary: Microsoft Office 2003, 2007 & 2010 applications do not print OTF Product: Wine Version: 1.3.34 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: gunwald(a)gmx.de Classification: Unclassified Created attachment 37835 --> http://bugs.winehq.org/attachment.cgi?id=37835 Document showing that OTF printing does not work All Microsoft Office applications form 2003 to 2010 are not able to print documents using any OTF (Open Type Font). Printing a Document using any OTF leads in a completely blank page. I think, this is an important bug, because printing is a main function of any office application. This bug may be related to bug 25515 (http://bugs.winehq.org/show_bug.cgi?id=25515). I did attach an document to demonstrate the bug. -- 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 11

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