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

[Bug 54333] New: Game "10S": crashes when starting new game
by WineHQ Bugzilla Jan. 26, 2023

Jan. 26, 2023

https://bugs.winehq.org/show_bug.cgi?id=54333 Bug ID: 54333 Summary: Game "10S": crashes when starting new game Product: Wine Version: 8.0-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: stabilergriller(a)gmail.com Distribution: --- Created attachment 73899 --> https://bugs.winehq.org/attachment.cgi?id=73899 complete output of the "code error" window A free demo of the game is provided on https://owch.itch.io/10s. Wine boots up the main menu successfully, but crashes when actually trying to get ingame (click the "Let's Play!" button). A "Code Error" pops up. My stats: OS: Arch GPU: Intel HD Graphics 610 Driver Mesa 22.3.3 Kernel version: 6.1.5 -- 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

[Bug 50306] New: Riptide GP Renegade: not able to connect to online multiplayer server (Error code 403)
by WineHQ Bugzilla Jan. 26, 2023

Jan. 26, 2023

https://bugs.winehq.org/show_bug.cgi?id=50306 Bug ID: 50306 Summary: Riptide GP Renegade: not able to connect to online multiplayer server (Error code 403) Product: Wine Version: 5.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ranplayer(a)protonmail.com Distribution: --- Created attachment 68878 --> https://bugs.winehq.org/attachment.cgi?id=68878 Wine output When you try to connect to the Online Multiplayer, the game shows the following message: """ Connection error: Unable to connect to the game server. Please, check you network connection and try again. (Error code 403) """ I created a clean prefix and installed only the Steam client and the game. No additional library was added. This issue happens on previous Wine versions as well. Game link: https://store.steampowered.com/app/443860/Riptide_GP_Renegade Setup: O.S: Manjaro Linux Arch: x86_64 Kernel: 5.4.80 Desktop Environment: KDE Plasma 5.20.4 CPU: Intel Core i5-4690s GPU: Nvidia GTX 970 4GB -- 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 54310] New: Test on an older distribution
by WineHQ Bugzilla Jan. 26, 2023

Jan. 26, 2023

https://bugs.winehq.org/show_bug.cgi?id=54310 Bug ID: 54310 Summary: Test on an older distribution Product: Wine-Testbot Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: novae.harpist06(a)icloud.com Distribution: --- There were several recent bugs that affect / affected older distros: https://bugs.winehq.org/show_bug.cgi?id=54060 https://bugs.winehq.org/show_bug.cgi?id=54166 https://bugs.winehq.org/show_bug.cgi?id=54210 https://bugs.winehq.org/show_bug.cgi?id=51268 I think it'd make sense to have an older distro as test VM to avoid these. The current oldest vendor-supported distro is RHEL7 (and rebuilds). I think it'd make sense to use that / a rebuild. I tested on an Oracle Linux 7.9 install, and used the following commands to get a compilation going: yum install -y -q https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm printf '[epel-archive]\nname=EPEL Archive\nbaseurl=https://archives.fedoraproject.org/pub/archive/epel/7.2019…' > /etc/yum.repos.d/epel-archive.repo yum install -y -q gcc-c++ make glibc-devel.i686 mingw32-gcc mingw64-gcc yum-builddep wine the archive repo is necessary as mingw was removed from EPEL around that time. -- 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 54226] New: widl: implement `cstruct_out` option to generate C bindings compatible with small struct return values
by WineHQ Bugzilla Jan. 26, 2023

Jan. 26, 2023

https://bugs.winehq.org/show_bug.cgi?id=54226 Bug ID: 54226 Summary: widl: implement `cstruct_out` option to generate C bindings compatible with small struct return values 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 According to https://devblogs.microsoft.com/oldnewthing/20220113-00/?p=106152, the previous C bindings are incompatible with the C++ COM ABI when the method returns a small struct for MSVC. Their solution is to add the `/cstruct_out` flag to the MIDL compiler (https://learn.microsoft.com/en-us/windows/win32/midl/-cstruct-out, added in the Win11 SDK according to comments) to generate new C bindings compatible with the C++ COM ABI. This is similar to the (long-standing) GCC issue with its mingw-w64 MS ABI (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64384) which has been worked around in widl/mingw-w64 by having special wrapper functions in the C++ bindings, guarded by `WIDL_EXPLICIT_AGGREGATE_RETURNS`. I think widl should follow suit to implement a `--cstruct_out` flag to do the same thing for the C bindings. This does not need to be guarded by `WIDL_EXPLICIT_AGGREGATE_RETURNS` because both GCC and MSVC has the same issue and will require the same fix. (I do not know if we need some kind of guard for the mingw-w64 headers to revert to the old function declarations, but given that the old bindings are practically broken perhaps it doesn't matter.) (I have not checked what `/cstruct_out` on MIDL actually does to the C bindings.) -- 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 54316] New: wine staging lacks wine-staging package (8.0~rc4~jammy-1)
by WineHQ Bugzilla Jan. 26, 2023

Jan. 26, 2023

https://bugs.winehq.org/show_bug.cgi?id=54316 Bug ID: 54316 Summary: wine staging lacks wine-staging package (8.0~rc4~jammy-1) Product: Packaging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: monsterovich(a)gmail.com CC: dimesio(a)earthlink.net Distribution: --- ┌(monsterovich(a)pc)─(pts/0)─(~) └─(>) LANG= sudo apt dist-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: wine-staging The following NEW packages will be installed: wine-staging:i386 The following packages will be upgraded: wine-staging-amd64 wine-staging-i386:i386 winehq-staging 3 upgraded, 1 newly installed, 1 to remove and 0 not upgraded. Need to get 216 MB of archives. After this operation, 46.1 kB of additional disk space will be used. Do you want to continue? [Y/n] -- 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 51484] New: dmloader:loader fails randomly with a DMUS_E_LOADER_BADPATH error
by WineHQ Bugzilla Jan. 26, 2023

Jan. 26, 2023

https://bugs.winehq.org/show_bug.cgi?id=51484 Bug ID: 51484 Summary: dmloader:loader fails randomly with a DMUS_E_LOADER_BADPATH error Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-dmusic Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Created attachment 70320 --> https://bugs.winehq.org/attachment.cgi?id=70320 Unsuccessful attempt to more reliably reproduce the failure dmloader:loader fails randomly in test_directory(): https://test.winehq.org/data/patterns.html loader.c:105: Test failed: SetSearchDirectory failed with 0x88781181 loader.c:107: Test failed: SetSearchDirectory failed with 0x88781181 where 0x88781181 == DMUS_E_LOADER_BADPATH. As of writing only w7u and cw-gtx560-1506 had failures but they are quite rare (up to 110 runs between failures), so maybe the other platforms just got lucky. Also once (2021-06-21) there was this set of failures: loader.c:105: Test failed: SetSearchDirectory failed with 0x88781181 loader.c:107: Test failed: SetSearchDirectory failed with 0 So it's as if there was a race condition causing SetSearchDirectory() to fail until some initialization process completed. That or it's some sort of uninitialized memory issue and the failures truly are random; or SetSearchDirectory() checks the presence of some directory corresponding to "", and some other process interferes with that. The attached patch has no success reproducing this issue so maybe the cause is external. -- 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 9

[Bug 52107] New: %ERRORLEVEL% shall not be reset when setting an environment variable in a batch file
by WineHQ Bugzilla Jan. 26, 2023

Jan. 26, 2023

https://bugs.winehq.org/show_bug.cgi?id=52107 Bug ID: 52107 Summary: %ERRORLEVEL% shall not be reset when setting an environment variable in a batch file Product: Wine Version: 6.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: jinoh.kang.kr(a)gmail.com CC: others.meder(a)gmail.com Distribution: --- The fix in https://bugs.winehq.org/show_bug.cgi?id=47791 (commit 617d14bc1238b57327a8400eda1c1ab22624beb7) is incomplete; it only applies to interactive case, and the bug is left unchanged for the batch mode case. When a variable is successfully set, %ERRORLEVEL% is left as-is regardless of whether the interpreter is in batch mode or not. See also: https://ss64.com/nt/set.html -- 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 54334] New: qasf:asfreader - test_threading(TRUE) sometimes fails in Wine (GitLab CI)
by WineHQ Bugzilla Jan. 26, 2023

Jan. 26, 2023

https://bugs.winehq.org/show_bug.cgi?id=54334 Bug ID: 54334 Summary: qasf:asfreader - test_threading(TRUE) sometimes fails in Wine (GitLab CI) Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: quartz Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- qasf:asfreader - test_threading(TRUE) sometimes fails in Wine: asfreader.c:954: Test failed: blocking 1: Got hr 0x8004022a. asfreader.c:977: Test failed: blocking 1: Wait timed out. asfreader.c:986: Test succeeded inside todo block: blocking 1: got wrong thread asfreader.c:998: Test failed: blocking 1: Got hr 0x1. So far this has not shown up in the WineTest results but it has impacted the GitLab CI results of at least two merge requests: * MR1668 https://gitlab.winehq.org/wine/wine/-/merge_requests/1668 * MR1965 https://gitlab.winehq.org/wine/wine/-/merge_requests/1965 -- 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 54016] New: dwmapi:dwmapi fails on Windows 10 21H2+ and 11
by WineHQ Bugzilla Jan. 26, 2023

Jan. 26, 2023

https://bugs.winehq.org/show_bug.cgi?id=54016 Bug ID: 54016 Summary: dwmapi:dwmapi fails on Windows 10 21H2+ and 11 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: dwmapi Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com dwmapi:dwmapi fails on Windows 10 21H2+ and 11: dwmapi.c:75: Test failed: Got wrong monitor refresh rate 156250/10000000. dwmapi.c:78: Test failed: Got wrong composition rate 156250/10000000. See https://test.winehq.org/data/patterns.html#dwmapi:dwmapi Note that this already impacted w10pro64-rx550 when it was running 21H2. However the TestBot's plain QXL 21H2 and 22H2 VMs are not impacted despite having the same dwmapi.dll version. Also Windows 11's QXL test configuration is impacted too so it's not something specific to AMD / NVIDIA GPUs. -- 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 54159] New: kernel32:debugger - crash_and_winedbg() gets an unexpected failure count on Windows 11
by WineHQ Bugzilla Jan. 26, 2023

Jan. 26, 2023

https://bugs.winehq.org/show_bug.cgi?id=54159 Bug ID: 54159 Summary: kernel32:debugger - crash_and_winedbg() gets an unexpected failure count on Windows 11 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com kernel32:debugger - crash_and_winedbg() gets an unexpected failure count on Windows 11 in the 'dbg,attach,process,event,detach' case: debugger.c:610: running dbg,attach,process,event,detach... debugger.c:621: waiting for child exit... debugger.c:198: child: crashing... debugger.c:659: waiting for the debugger... debugger.c:166: debugger traces: processing debug messages setting event done debugging... debugger.c:681: Test failed: debugger reported 4 failures See https://test.winehq.org/data/patterns.html#kernel32:debugger While this error is systematic on Windows 11 it never happened on Windows 10 and lower... except in MR!1823 which had something very similar: debugger.c:600: running dbg,attach,process,event,detach... debugger.c:611: waiting for child exit... debugger.c:198: child: crashing... debugger.c:649: waiting for the debugger... debugger.c:166: debugger traces: processing debug messages setting event done debugging... debugger.c:671: Test failed: debugger reported 7 failures -- 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