December 2022 - Wine-bugs - list.winehq.org

[Bug 50306] New: Riptide GP Renegade: not able to connect to online multiplayer server (Error code 403)
by WineHQ Bugzilla 19 Jan '23

19 Jan '23

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 54226] New: widl: implement `cstruct_out` option to generate C bindings compatible with small struct return values
by WineHQ Bugzilla 19 Jan '23

19 Jan '23

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 51484] New: dmloader:loader fails randomly with a DMUS_E_LOADER_BADPATH error
by WineHQ Bugzilla 18 Jan '23

18 Jan '23

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 40446] New: WinSCP is missing text in the "About" window
by wine-bugs＠winehq.org 18 Jan '23

18 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=40446 Bug ID: 40446 Summary: WinSCP is missing text in the "About" window Product: Wine Version: 1.9.7 Hardware: x86 URL: http://winscp.net/download/winscp577.zip OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mshtml Assignee: wine-bugs(a)winehq.org Reporter: t.artem(a)mailcity.com Distribution: --- Run WinSCP, invoke Tools -> About, see no text. Logged errors in console: fixme:ieframe:PersistStreamInit_InitNew (0x1c1728) fixme:ieframe:OleControl_OnAmbientPropertyChange Unknown dispID -702 fixme:ieframe:OleControl_OnAmbientPropertyChange Unknown dispID -701 fixme:ieframe:OleControl_OnAmbientPropertyChange Unknown dispID -703 fixme:ieframe:OleControl_OnAmbientPropertyChange Unknown dispID -704 fixme:iphlpapi:NotifyIpInterfaceChange (family 0, callback 0x6a0a6836, context 0x215da80, init_notify 0, handle 0x2a6e7f4): stub fixme:imm:ImmGetDescriptionW (0x4090409, (nil), 0): semi stub fixme:imm:ImmGetDescriptionW (0x4090409, 0x503f508, 9): semi stub fixme:imm:ImmReleaseContext (0x40116, 0x1b7458): stub fixme:win:EnumDisplayDevicesW ((null),0,0x32a304,0x00000000), stub! fixme:ntdll:NtLockFile I/O completion on lock not implemented yet fixme:ieframe:BrowserService_GetTravelLog 0x1e00b0 0x32ae98 fixme:mshtml:OleControl_OnAmbientPropertyChange edit mode is not supported fixme:ieframe:ClientSite_GetContainer (0x1c17ec)->(0x32ae7c) fixme:mshtml:nsChannel_GetContentDisposition (0x1fcec0)->(0x3285e8) fixme:mshtml:nsChannel_GetContentDispositionHeader (0x1fcec0)->(0x327d3c) err:mshtml:update_window_doc SetDesignMode failed: 80070057 fixme:ieframe:ClientSite_GetContainer (0x1c17ec)->(0x32dd4c) fixme:ieframe:DocHostUIHandler_GetDropTarget (0x1c17ec) fixme:win:WINNLSEnableIME hwnd 0x40084 enable -1: stub! fixme:ntdll:EtwRegisterTraceGuidsW (0x69ee122c, 0x503c9f8, {509962e0-406b-46f4-99ba-5a009f8d2225}, 3, 0x5e60ab8, (null), (null), 0x503ca28): stub fixme:ntdll:EtwRegisterTraceGuidsW register trace class {a3da04e0-57d7-482a-a1c1-61da5f95bacb} fixme:ntdll:EtwRegisterTraceGuidsW register trace class {917b96b1-ecad-4dab-a760-8d49027748ae} fixme:ntdll:EtwRegisterTraceGuidsW register trace class {26d1e091-0ae7-4f49-a554-4214445c505c} fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) err:mshtml:do_ns_command DoCommand("cmd_fontFace") failed: 80004005 fixme:ieframe:PropertyNotifySink_OnChanged unimplemented dispid 1005 fixme:mshtml:HTMLDocument_put_designMode Unsupported arg L"Off" fixme:ieframe:ClientSite_GetContainer (0x1c17ec)->(0x32f1ec) fixme:mshtml:nsChannel_GetContentDisposition (0x1fce28)->(0x32ec68) fixme:mshtml:nsChannel_GetContentDispositionHeader (0x1fce28)->(0x32e3bc) err:mshtml:update_window_doc SetDesignMode failed: 80070057 fixme:ieframe:ControlSite_OnFocus (0x1c17ec)->(0) fixme:ieframe:InPlaceSite_OnInPlaceDeactivateEx fNoRedraw (1) ignored fixme:mshtml:HlinkTarget_SetBrowseContext (0x1e15c8)->((nil)) -- 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 15

[Bug 52107] New: %ERRORLEVEL% shall not be reset when setting an environment variable in a batch file
by WineHQ Bugzilla 18 Jan '23

18 Jan '23

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 54016] New: dwmapi:dwmapi fails on Windows 10 21H2+ and 11
by WineHQ Bugzilla 18 Jan '23

18 Jan '23

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 18 Jan '23

18 Jan '23

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

[Bug 53863] New: Tsui no Stella = Stella of the End: doesn't launch anymore (GL_INVALID_OPERATION)
by WineHQ Bugzilla 18 Jan '23

18 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=53863 Bug ID: 53863 Summary: Tsui no Stella = Stella of the End: doesn't launch anymore (GL_INVALID_OPERATION) Product: Wine Version: 7.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: pernegger(a)gmail.com Distribution: --- Created attachment 73393 --> https://bugs.winehq.org/attachment.cgi?id=73393 terminal output for 7.20 and 7.19 You can get a trial copy of the game here: https://key.visualarts.gr.jp/kinetic/stella/#download. Random direct link: https://sample9.dmm.co.jp/mono/pcgame/1041apc14123/1041apc14123t.zip The game runs fine in 7.18 and 7.19 at least, but it fails to launch for me after the update to 7.20: 0118:err:d3d:wined3d_debug_callback 0A542890: "GL_INVALID_OPERATION in glMapBufferRange(access indicates neither read or write)". 0118:err:d3d:wined3d_allocator_chunk_gl_map Failed to map chunk memory. 0118:err:d3d:wined3d_bo_gl_map Failed to map chunk. 0118:err:d3d:wined3d_context_gl_map_bo_address Failed to map bo. (Downgrading to 7.19 fixes the issue.) [Ubuntu 18.04.6, WINE packages from the official WineHQ repo] -- 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 15

[Bug 52177] New: Gamepad stopped working (In The Groove, Fedora 35, wine 6.21)
by WineHQ Bugzilla 17 Jan '23

17 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=52177 Bug ID: 52177 Summary: Gamepad stopped working (In The Groove, Fedora 35, wine 6.21) Product: Wine Version: 6.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kas(a)yenya.net Distribution: --- After upgrade to Fedora 35 (wine-6.21-1.fc35.x86_64) from Fedora 34 I am no longer able to play the game In The Groove (a rhythm game based on StepMania engine): The game itself detects my gamepad both as /dev/input/eventX and /dev/input/jsY, but when I try to configure the input, pressing buttons on the gamepad is not recognized by the game. When I disable the /dev/input/js* (by chmod a-rw), it can see the first four buttons out of ten, but when the button 3 is pressed, it does not see the button 0 being pressed. When I run "jstest /dev/input/jsY", jstest recognizes all ten buttons and their combinations. So the hardware works as expected. What should I try in order to get the game working with my gamepad? Thanks! -- 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 10

[Bug 28960] New: Mount & Blade: WFAS configuration menu panels are partially hidden
by wine-bugs＠winehq.org 17 Jan '23

17 Jan '23

http://bugs.winehq.org/show_bug.cgi?id=28960 Bug #: 28960 Summary: Mount & Blade: WFAS configuration menu panels are partially hidden Product: Wine Version: 1.3.31 Platform: x86 URL: http://www.fileplanet.com/219895/210000/fileinfo/Mount &Blade-with-Fire-and-Sword-Demo OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdi32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: pavel.ondracka(a)gmail.com Classification: Unclassified Regression SHA1: 3b9669017bc8425f04860f331d8a1f689c8d63e0 Created attachment 37237 --> http://bugs.winehq.org/attachment.cgi?id=37237 comparison of good and bad behavior 3b9669017bc8425f04860f331d8a1f689c8d63e0 is the first bad commit commit 3b9669017bc8425f04860f331d8a1f689c8d63e0 Author: Huw Davies <huw(a)codeweavers.com> Date: Wed Oct 12 11:55:13 2011 +0100 gdi32: Add the liberation fonts to the default fallback lists. Screenshot attached, reverting mentioned commit from latest wine fixes this issue. To reproduce: start game, select trial and click configure when launcher menu starts. -- 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 20