wine-bugs March 2023

wine-bugs@winehq.org

1 participants
3669 discussions

[Bug 54742] New: The 64-bit advapi32:registry breaks the 32-bit test_redirection() in Wine
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=54742 Bug ID: 54742 Summary: The 64-bit advapi32:registry breaks the 32-bit test_redirection() in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: advapi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- The 64-bit advapi32:registry breaks the 32-bit test_redirection() in Wine. To reproduce run the following commands: $ rm -rf ~/.wine # start from a fresh wineprefix $ ./wow64/wine64 wow64/dlls/advapi32/tests/x86_64-windows/advapi32_test.exe registry 2>&1 | grep -E '(Test failed|tests executed)' 0020:registry: 6309 tests executed (156 marked as todo, 0 as flaky, 0 failures), 2 skipped. $ ./wow32/wine wow32/dlls/advapi32/tests/i386-windows/advapi32_test.exe registry 2>&1 | grep -E '(Test failed|tests executed)' registry.c:2837: Test failed: RegOpenKeyExA failed: 2 registry.c:2842: Test failed: RegOpenKeyExA failed: 2 registry.c:2861: Test failed: 00000000: wrong value 32/64 registry.c:2863: Test failed: 00000200: wrong value 32/64 registry.c:2868: Test failed: 00000000: wrong value 64/0 registry.c:2869: Test failed: 00000100: wrong value 64/0 registry.c:2870: Test failed: 00000200: wrong value 64/0 registry.c:3168: Test failed: RegOpenKeyExA failed: 2 registry.c:3174: Test failed: RegOpenKeyExA failed: 2 registry.c:3180: Test failed: RegOpenKeyExA failed: 2 registry.c:3206: Test failed: found equals 0 registry.c:3208: Test failed: found equals 0 registry.c:3210: Test failed: found equals 0 registry.c:3212: Test failed: found equals 1 registry.c:3214: Test failed: wrong number of subkeys: 10 registry.c:3216: Test failed: found equals 1 registry.c:3218: Test failed: found equals 0 registry.c:3220: Test failed: wrong number of subkeys: 10 registry.c:3222: Test failed: found equals 0 0128:registry: 7658 tests executed (74 marked as todo, 0 as flaky, 19 failures), 2 skipped. See https://test.winehq.org/data/patterns.html#advapi32:registry The reason why this failure is only visible with the fg-deb64-wow32 is because this is the only test configuration that runs the 32-bit tests in the same wineprefix as the 64-bit tests. What this shows is that advapi32:registry does not correctly cleans up after itself which has the potential for breaking any test that follows (not just 32-bit ones). -- 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 53431] New: widl generates enum forward declarations in typedefs which are not valid in C++
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

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 23 Jun '23

23 Jun '23

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@aw25 ~/wine-gcc49-asan $ clang --version clang version 3.3 (tags/RELEASE_33/final) Target: x86_64-pc-linux-gnu Thread model: posix austin@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 49797] New: WIDL doesn't tolerate anonymous structs within interfaces
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

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 37346] New: New application , installed successfully , starts up fine , no data storing , BUSY WIN ACCOUNTING APP
by wine-bugs＠winehq.org 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=37346 Bug ID: 37346 Summary: New application , installed successfully , starts up fine , no data storing , BUSY WIN ACCOUNTING APP Product: Wine Version: unspecified Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lax.sunny(a)gmail.com Created attachment 49664 --> https://bugs.winehq.org/attachment.cgi?id=49664 Log created by wine on running the app , problem is with database storage and runtime functions Application named busy win very much famous accounting software tried using number of prefixes application installs smoothly when i run the app it starts up normally but crashes on adding a new company or detecting an old DATABASE -- 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 10

[Bug 50079] New: Wine msiexec fails when building inside a windows/mac os x docker container
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=50079 Bug ID: 50079 Summary: Wine msiexec fails when building inside a windows/mac os x docker container Product: Wine Version: 5.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: spam(a)crasu.de Distribution: --- Created attachment 68535 --> https://bugs.winehq.org/attachment.cgi?id=68535 Run with winedebug=msi and strace Sample dockerfile: FROM ubuntu:20.04 RUN export DEBIAN_FRONTEND="noninteractive" \ && dpkg --add-architecture i386 \ && apt-get update \ && apt-get install -y wget winbind xvfb unzip curl jq \ && apt-get remove -y libmysqlclient21 mysql-common \ && apt autoremove -y RUN wget -nc https://dl.winehq.org/wine-builds/winehq.key && apt-key add winehq.key RUN echo 'deb https://dl.winehq.org/wine-builds/ubuntu/ focal main' > /etc/apt/sources.list.d/wine.list RUN export DEBIAN_FRONTEND="noninteractive" \ && apt-get update \ && apt-get install -o APT::Immediate-Configure=false --install-recommends -y winehq-devel RUN useradd -ms /bin/bash wineuser # Install winemono RUN wget https://dl.winehq.org/wine/wine-mono/5.1.1/wine-mono-5.1.1-x86.msi RUN WINEPREFIX=/home/wineuser/.wine su wineuser -c "wine msiexec /i wine-mono-5.1.1-x86.msi && wineserver -w" Eroor message: 0024:err:msi:ACTION_InstallFiles compressed file wasn't installed (L"bin\\libmono-2.0-x86.dll") 0024:err:msi:execute_script Execution of script 0 halted; action L"InstallFiles" returned 1603 I tried different msis (wine gecko, wine mono, ....) they all fail. After serveral tries the installation sometimes does not through an error. But the package is still not fully installed. Reference: https://github.com/Winetricks/winetricks/issues/1525 -- 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 51502] New: Civilization 3 Sound Stutters, loops, and fails (eventually)
by WineHQ Bugzilla 22 Jun '23

22 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=51502 Bug ID: 51502 Summary: Civilization 3 Sound Stutters, loops, and fails (eventually) Product: Wine Version: 6.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mountmgr.sys Assignee: wine-bugs(a)winehq.org Reporter: bryan(a)varnernet.com Distribution: --- Audio on Civilization III is just not very good. Typical short sounds stutter, playback sounding badly rendered into the target buffer, loop when they shouldn't, etc. The most common problem is for the sound (all of it) to just stop, or just continuously loop a small soundfile that should have been a one-off play at the triggered point in time. Looks like the app is using dsound, along with winmm to mmioOpenA the .wav's. -- 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 52762] New: DesignDoll will not boot/crashes upon booting.
by WineHQ Bugzilla 22 Jun '23

22 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=52762 Bug ID: 52762 Summary: DesignDoll will not boot/crashes upon booting. Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: catchyandcleche(a)gmail.com Distribution: --- Created attachment 72129 --> https://bugs.winehq.org/attachment.cgi?id=72129 This file (designdoll_backtrace01.txt) is the backtrace file/error log file that was created when I tried to run the DesignDoll application. I am using a GUI version of Ubuntu for Desktop (Ubuntu 20.04.4 LTS), also utilizing WINE version 7.0 (Displayed as wine-7.0 in the terminal). When double clicking the .desktop application created on the desktop (DesignDoll.desktop) after installing the DesginDollLauncher.exe program and after making sure that the DesignDoll.desktop shortcut created during the installation process allows launching, the program will boot* but quickly crash. I attached the program error log (see "designdoll_backtrace01.txt). *I can only assume that the application booted (or at least tried to) and quickly crashed. It did not display any indication that the program had booted in the GUI environment. When a window did show up to indicate that the program had run (in a sense), it was to inform me of the fact that the program crashed (or simply could not boot). -- 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 54271] New: gdiplus:get_gif_background_color can't get gif background color
by WineHQ Bugzilla 21 Jun '23

21 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=54271 Bug ID: 54271 Summary: gdiplus:get_gif_background_color can't get gif background color Product: Wine Version: unspecified Hardware: x86 OS: other Status: UNCONFIRMED Severity: critical Priority: P2 Component: gdiplus Assignee: wine-bugs(a)winehq.org Reporter: 399989567(a)qq.com Created attachment 73837 --> https://bugs.winehq.org/attachment.cgi?id=73837 wrong picture OS：debian When I was using WeChat, I found that when sending an animated gif, the same image would have different serious errors, such as misalignment, flickering, solid black(sometimes pink, brown) background . I know that using winetricks gidplus can fix this problem, but this method introduces some other problems, so I come here for help hoping to find a solution to the problem. I really need your help! ! ! Maybe you need an account for this application. Of course, it would be great if you can find a similar demo. I am trying to find a demo APP download url：https://weixin.qq.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 11

[Bug 52619] New: Dungeon Fighter Online: Launcher crash when accepting Terms of Service
by WineHQ Bugzilla 20 Jun '23

20 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=52619 Bug ID: 52619 Summary: Dungeon Fighter Online: Launcher crash when accepting Terms of Service Product: Wine Version: 7.2 Hardware: x86-64 URL: https://www.dfoneople.com/support/download OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: wannabetheguy(a)gmail.com Distribution: Fedora Created attachment 71944 --> https://bugs.winehq.org/attachment.cgi?id=71944 Terminal log output With Proton 7.0 announcing Dungeon Fighter Online as playable, I gave it a try and ran into this crash when trying to log-in with my old Neople account. Both the Steam version and standalone version of the launcher crashed this way. A clean Wine 7.2 (staging) prefix with the standaline client gives me an identical result, so I am reporting here as well. The problem occurs with NeopleLauncher.exe. After logging in with my Neople account, I am required to accept the Terms of Service that appears within the window before being able to continue. When I click the Accept button, the launcher crashes. On subsequent log-ins, the Terms of Service appears again. The only change to the Wine prefix was changing the Windows version to 10 as the launcher gives a "no longer supported" message with 7. 8/8.1 work but crash the same as 10. The ieframe messages just before the backtrace seem notable, but as I'm not sure I have set this report to unknown. -- 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 31

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