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

[Bug 55122] New: oleaut32:vartest - test_VarParseNumFromStrFr() fails on Windows 11
by WineHQ Bugzilla June 23, 2023

June 23, 2023

https://bugs.winehq.org/show_bug.cgi?id=55122 Bug ID: 55122 Summary: oleaut32:vartest - test_VarParseNumFromStrFr() fails on Windows 11 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: oleaut32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com oleaut32:vartest - test_VarParseNumFromStrFr() fails on Windows 11: vartest.c:1999: Test failed: 1: Call succeeded, hres = 00000000 vartest.c:2012: Test failed: 1: returned 80020005 vartest.c:2049: Test failed: 1: returned 80020005 vartest.c:2121: Test failed: 1: Call succeeded, hres = 00000000 vartest.c:2135: Test failed: 1: returned 80020005 See https://test.winehq.org/data/patterns.html#oleaut32:vartest Where 80020005 == DISP_E_TYPEMISMATCH -- 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 55121] New: wintrust:asn - test_encodeSPCPEImage() fails on Windows 11
by WineHQ Bugzilla June 23, 2023

June 23, 2023

https://bugs.winehq.org/show_bug.cgi?id=55121 Bug ID: 55121 Summary: wintrust:asn - test_encodeSPCPEImage() fails on Windows 11 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: wintrust Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com wintrust:asn - test_encodeSPCPEImage() fails on Windows 11: asn.c:385: Test failed: CryptEncodeObjectEx failed: c0000005 asn.c:398: Test failed: CryptEncodeObjectEx failed: c0000005 asn.c:563: Test failed: CryptEncodeObjectEx failed: c0000005 asn.c:673: Test failed: CryptEncodeObjectEx failed: c0000005 asn.c:696: Test failed: CryptEncodeObjectEx failed: c0000005 asn.c:709: Test failed: CryptEncodeObjectEx failed: c0000005 See https://test.winehq.org/data/patterns.html#wintrust:asn Where c0000005 == STATUS_ACCESS_VIOLATION -- 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 53431] New: widl generates enum forward declarations in typedefs which are not valid in C++
by WineHQ Bugzilla June 23, 2023

June 23, 2023

https://bugs.winehq.org/show_bug.cgi?id=53431 Bug ID: 53431 Summary: widl generates enum forward declarations in typedefs which are not valid in C++ Product: Wine Version: 7.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: tools Assignee: wine-bugs(a)winehq.org Reporter: gfw.kra(a)gmail.com Distribution: --- Hi everyone, I recently discovered an issue with C++ code in headers compiled from winrt idl's using widl. It does not compile when included, when tried using mingw g++ v12.1.0. There’s seems to be issue with how enum typedefs are translated within namespaces. Example: When tried to include windows.media.speechsynthesis.h compiled from windows.media.speechsynthesis.idl in cpp file, the following output is received (compiler output shows headers from mingw, but these look the same when compiled using widl in wine). ``` /usr/x86_64-w64-mingw32/include/windows.foundation.h:90:26: error: use of enum ‘PropertyType’ without previous declaration 90 | typedef enum PropertyType PropertyType; | ^~~~~~~~~~~~ /usr/x86_64-w64-mingw32/include/windows.foundation.h:164:18: error: using typedef-name ‘ABI::Windows::Foundation::PropertyType’ after ‘enum’ 164 | enum PropertyType { | ^~~~~~~~~~~~ /usr/x86_64-w64-mingw32/include/windows.foundation.h:90:39: note: ‘ABI::Windows::Foundation::PropertyType’ has a previous declaration here 90 | typedef enum PropertyType PropertyType; | ^~~~~~~~~~~~ /usr/x86_64-w64-mingw32/include/windows.media.speechsynthesis.h:218:30: error: use of enum ‘VoiceGender’ without previous declaration 218 | typedef enum VoiceGender VoiceGender; | ^~~~~~~~~~~ /usr/x86_64-w64-mingw32/include/windows.media.speechsynthesis.h:476:22: error: using typedef-name ‘ABI::Windows::Media::SpeechSynthesis::VoiceGender’ after ‘enum’ 476 | enum VoiceGender { | ^~~~~~~~~~~ /usr/x86_64-w64-mingw32/include/windows.media.speechsynthesis.h:218:42: note: ‘ABI::Windows::Media::SpeechSynthesis::VoiceGender’ has a previous declaration here 218 | typedef enum VoiceGender VoiceGender; | ^~~~~~~~~~~ /usr/x86_64-w64-mingw32/include/windows.media.speechsynthesis.h:822:30: error: using typedef-name ‘ABI::Windows::Media::SpeechSynthesis::VoiceGender’ after ‘enum’ 822 | enum VoiceGender *value) = 0; | ^~~~~~~~~~~ /usr/x86_64-w64-mingw32/include/windows.media.speechsynthesis.h:218:42: note: ‘ABI::Windows::Media::SpeechSynthesis::VoiceGender’ has a previous declaration here 218 | typedef enum VoiceGender VoiceGender; ``` windows.media.speechsynthesis.idl has typedef of enum VoiceGender, which is defined later. ``` namespace Windows { namespace Foundation { interface IClosable; } namespace Media { namespace SpeechSynthesis { typedef enum VoiceGender VoiceGender; ``` This is translated to following: ``` #ifdef __cplusplus namespace ABI { namespace Windows { namespace Media { namespace SpeechSynthesis { typedef enum VoiceGender VoiceGender; } } } } #else /* __cplusplus */ typedef enum __x_ABI_CWindows_CMedia_CSpeechSynthesis_CVoiceGender __x_ABI_CWindows_CMedia_CSpeechSynthesis_CVoiceGender; #endif /* __cplusplus */ ``` This typedef is not valid in C++. According to the standard, enum cannot be forward declared using typedef. This could be replaced with just simple enum declaration, but it would need to have type specifier (that goes for definition as well). Best regards. -- 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 36079] New: loader fails to build with clang -faddress=sanitize
by wine-bugs＠winehq.org June 23, 2023

June 23, 2023

https://bugs.winehq.org/show_bug.cgi?id=36079 Bug ID: 36079 Summary: loader fails to build with clang -faddress=sanitize Product: Wine Version: 1.7.17 Hardware: x86 OS: Linux Status: NEW Keywords: download, source Severity: enhancement Priority: P2 Component: build-env Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Created attachment 48263 --> https://bugs.winehq.org/attachment.cgi?id=48263 make log I tried building wine with clang's address sanitizer enabled, which mostly worked, until the loader: make[1]: Entering directory '/home/austin/wine-gcc49-asan/loader' clang -fsanitize=address -m32 -o wine-preloader -static -nostartfiles -nodefaultlibs -Wl,-Ttext=0x7c400000 preloader.o ../libs/port/libwine_port.a /usr/lib64/gcc/x86_64-pc-linux-gnu/4.8.2/../../../../lib32/libpthread.a(pthread_mutex_lock.o): In function `__pthread_mutex_lock': /var/tmp/portage/sys-libs/glibc-2.19/work/glibc-2.19/nptl/../nptl/pthread_mutex_lock.c:80: undefined reference to `__assert_fail' /var/tmp/portage/sys-libs/glibc-2.19/work/glibc-2.19/nptl/../nptl/pthread_mutex_lock.c:116: undefined reference to `__assert_fail' /var/tmp/portage/sys-libs/glibc-2.19/work/glibc-2.19/nptl/../nptl/pthread_mutex_lock.c:146: undefined reference to `__assert_fail' /var/tmp/portage/sys-libs/glibc-2.19/work/glibc-2.19/nptl/../nptl/pthread_mutex_lock.c:151: undefined reference to `__assert_fail' .. austin(a)aw25 ~/wine-gcc49-asan $ clang --version clang version 3.3 (tags/RELEASE_33/final) Target: x86_64-pc-linux-gnu Thread model: posix austin(a)aw25 ~/wine-gcc49-asan $ git describe wine-1.7.17-42-g24c5728 -- 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 3

[Bug 55119] New: advapi32:security - test_process_security() fails on GitLab CI's Windows VM
by WineHQ Bugzilla June 23, 2023

June 23, 2023

https://bugs.winehq.org/show_bug.cgi?id=55119 Bug ID: 55119 Summary: advapi32:security - test_process_security() fails on GitLab CI's Windows VM Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: advapi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com advapi32:security - test_process_security() fails on GitLab CI's Windows VM: security.c:3176: Test failed: OpenProcess(PROCESS_VM_READ) should have failed security.c:3178: Test failed: OpenProcess(PROCESS_ALL_ACCESS) should have failed security.c:3209: Test failed: OpenThread(THREAD_SET_THREAD_TOKEN) should have failed See https://test.winehq.org/data/patterns.html#advapi32:security These three failures happen in both the 32- and 64-bit tests but only on gitlab-win10-21h2, the GitLab's Windows VM. -- 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 49797] New: WIDL doesn't tolerate anonymous structs within interfaces
by WineHQ Bugzilla June 23, 2023

June 23, 2023

https://bugs.winehq.org/show_bug.cgi?id=49797 Bug ID: 49797 Summary: WIDL doesn't tolerate anonymous structs within interfaces Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: tools Assignee: wine-bugs(a)winehq.org Reporter: kolan_n(a)mail.ru Distribution: --- IDLs in Windows SDKs sometimes contain anonymous structs within interfaces. WIDL fails to compile such IDLs. -- 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 55118] New: shell32:shlfolder - test_SHOpenFolderAndSelectItems() is missing a registry key in the new WoW mode
by WineHQ Bugzilla June 23, 2023

June 23, 2023

https://bugs.winehq.org/show_bug.cgi?id=55118 Bug ID: 55118 Summary: shell32:shlfolder - test_SHOpenFolderAndSelectItems() is missing a registry key in the new WoW mode 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:shlfolder - test_SHOpenFolderAndSelectItems() is missing a registry key in the new WoW mode: shlfolder.c:5512: Test failed: Got unexpected hr 0x80040152. shlfolder.c:5513: Test failed: Failed to create window. shlfolder.c:5520: Test failed: Got unexpected hr 0x80040152. shlfolder.c:5521: Test failed: Failed to create window. shlfolder.c:5530: Test failed: Got unexpected hr 0x80040152. shlfolder.c:5531: Test failed: Failed to create window. shlfolder.c:5540: Test failed: Got unexpected hr 0x80040152. shlfolder.c:5541: Test failed: Failed to create window. shlfolder.c:5550: Test failed: Got unexpected hr 0x80040152. shlfolder.c:5551: Test failed: Failed to create window. See https://test.winehq.org/data/patterns.html#shell32:shlfolder Where 0x80040152 == REGDB_E_KEYMISSING This happens in both the 32-bit and 64-bit tests but only in the new Windows-on-Windows mode. See the *-i386 and *-x86_64 results. See also bug 55117 where shell32:shelldispatch has a similar issue. -- 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 55117] New: shell32:shelldispatch - test_ShellWindows() is missing a registry key in the new WoW mode
by WineHQ Bugzilla June 23, 2023

June 23, 2023

https://bugs.winehq.org/show_bug.cgi?id=55117 Bug ID: 55117 Summary: shell32:shelldispatch - test_ShellWindows() is missing a registry key in the new WoW mode 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:shelldispatch - test_ShellWindows() is missing a registry key in the new WoW mode: shelldispatch.c:1025: Test failed: got 0x80040152 See https://test.winehq.org/data/patterns.html#shell32:shelldispatch Where 0x80040152 == REGDB_E_KEYMISSING This happens in both the 32-bit and 64-bit tests but only in the new Windows-on-Windows mode. See the *-i386 and *-x86_64 results. -- 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 55116] New: services.exe:service - service_main() is missing PATHEXT in the new WoW mode
by WineHQ Bugzilla June 23, 2023

June 23, 2023

https://bugs.winehq.org/show_bug.cgi?id=55116 Bug ID: 55116 Summary: services.exe:service - service_main() is missing PATHEXT in the new WoW mode Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- services.exe:service - test_service() is missing PATHEXT in the new WoW mode: service.c:420: Test failed: service: did not find PATHEXT environment variable See https://test.winehq.org/data/patterns.html#services.exe:service This happens during both test_service() and test_kill_service_process(), in both the 32-bit and 64-bit tests but only in the new Windows-on-Windows mode. -- 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 55094] New: Memory Access Violation & Run-Time Error 7 in WINE
by WineHQ Bugzilla June 23, 2023

June 23, 2023

https://bugs.winehq.org/show_bug.cgi?id=55094 Bug ID: 55094 Summary: Memory Access Violation & Run-Time Error 7 in WINE Product: Wine Version: 8.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: vbscript Assignee: wine-bugs(a)winehq.org Reporter: vikasy.enjay(a)gmail.com Distribution: --- Created attachment 74654 --> https://bugs.winehq.org/attachment.cgi?id=74654 Memory Access Violation & Run-Time Error 7 in WINE Memory Access Violation & Run-Time Error 7 in WINE: I am writing this to seek assistance regarding an issue I encountered while installing and running "Busy Accounting Software" using Wine. Despite my previous unsuccessful attempts, I was eventually able to install the software. However, I am currently facing an ongoing problem when attempting to execute the application. It consistently displays a "Runtime 7 Error and Memory Access Violation" error. Any assistance or troubleshooting steps you can provide would be greatly appreciated. Thank you for your attention to this matter. -- 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 7