wine-bugs January 2023

wine-bugs@winehq.org

1 participants
3730 discussions

[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 54334] New: qasf:asfreader - test_threading(TRUE) sometimes fails in Wine (GitLab CI)
by WineHQ Bugzilla 18 Jan '23

18 Jan '23

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 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 54330] New: Folder save-to path doesn't update if you navigate using the "bookmarks" left sidebar; subsequently clicking "Open" does nothing or crashes
by WineHQ Bugzilla 17 Jan '23

17 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=54330 Bug ID: 54330 Summary: Folder save-to path doesn't update if you navigate using the "bookmarks" left sidebar; subsequently clicking "Open" does nothing or crashes 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: NM64+bugs.winehq.org(a)PM.me Distribution: --- Created attachment 73893 --> https://bugs.winehq.org/attachment.cgi?id=73893 video demonstration of the full process for reproducing the issue On software such as VirtualDub2 or RPA Explorer, when navigating the "save to" folder location, if you instead navigate by clicking on the "bookmarks" left sidebar, then the location entry path does not get updated. When you do this in VirtualDub2, subsequently clicking the "Open" button does nothing. When you do this in RPA Explorer, subsequently clicking the "Open" button throws up an error and crashes the program. (also, why does the button say "Open" rather than "Save"? We're selecting the folder to save to after all...) See the attached video which demonstrates the issue in its entirety to the point that you should be able to fully replicate and reproduce the issue (note that it was performed on a live ISO of Linux Mint 21.1 Cinnamon). And for reference, here are the URLs that were visited in the aforementioned video: VirtualDub2: https://sourceforge.net/projects/vdfiltermod/ RPA Explorer: https://github.com/UniverseDevel/RPA-Explorer Example RPA file: http://katawa-shoujo.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 0

[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 54326] New: nsi:nsi - test_ndis_ifinfo() sometimes gets out-of-order InUcastPkts bounds on Windows 10 <= 1607
by WineHQ Bugzilla 17 Jan '23

17 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=54326 Bug ID: 54326 Summary: nsi:nsi - test_ndis_ifinfo() sometimes gets out-of-order InUcastPkts bounds on Windows 10 <= 1607 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com nsi:nsi - test_ndis_ifinfo() sometimes gets out-of-order InUcastPkts bounds on Windows 10 <= 1607: * 2023-01-09 on w1064v1607 (64-bit) nsi.c:344: Test failed: 1: InUcastPkts: 48607845 not in [48607847 48685030] * 2023-01-16 on w1064v1507 (32-bit) nsi.c:344: Test failed: 1: InUcastPkts: 19183127 not in [19183127 19183125] See https://test.winehq.org/data/patterns.html#nsi:nsi Only two instances so far. -- 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 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

[Bug 54324] New: shell32:autocomplete - The dropdown is sometimes unexpectedly visible in test_prefix_filtering() on Windows
by WineHQ Bugzilla 17 Jan '23

17 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=54324 Bug ID: 54324 Summary: shell32:autocomplete - The dropdown is sometimes unexpectedly visible in test_prefix_filtering() on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com shell32:autocomplete - The dropdown is sometimes unexpectedly visible in test_prefix_filtering() on Windows: autocomplete.c:671: Test failed: AutoComplete DropDown visible See https://test.winehq.org/data/patterns.html#shell32:autocomplete There have been 4 instances in the past 6 months: * 2022-08-16 on fgtb-w10pro64 (but this one had a lot of other failures so it may just have been a side-effect of some other issue) * 2022-09-01 on w10pro64-hi-u8 * 2022-11-03 on w10pro64-en-AE-u8 * 2022-01-16 on w10pro64-ar -- 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 54320] New: BCryptDecrypt Symmetric Key Flags Behavior
by WineHQ Bugzilla 17 Jan '23

17 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=54320 Bug ID: 54320 Summary: BCryptDecrypt Symmetric Key Flags Behavior Product: Wine Version: 7.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: bcrypt Assignee: wine-bugs(a)winehq.org Reporter: jutras.marc(a)gmail.com Distribution: --- In the BCryptDecrypt function, the behavior of the function is to check if the `key_is_symmetric`, then if that is the case confirm whether the flags are implemented or not. If the flags are not implemented a FIXME is printed and the function returns an error. In the software Solid Edge 2023, this behavior is preventing the software from running correctly. Solid Edge appears to have a bug where it is passing an invalid key to the `handle` parameter (a bad pointer?) which results in the key type being recognized as symmetric (likely because `key->alg_id` of zero (after a deref to empty memory) is 3DES which is symmetric). The call to BCryptDecrypt has the flag `BCRYPT_PAD_PKCS1` set which, combined with the key being recognized as symmetric, causes the function to return an error status. My assumption is that Windows is not checking the flags and is returning garbage as the decryption. This allows the program to continue running (ignorance is bliss). I have not run the debugger to confirm that `key->alg_id` is zero. I have also not confirmed this function's behavior on Windows. I have confirmed that removing the `return STATUS_NOT_IMPLEMENTED` fixes the issue in Solid Edge 2023. The proposal would be to change the check from `flags & ~BCRYPT_BLOCK_PADDING` to `flags == BCRYPT_BLOCK_PADDING`. This allows the STATUS_NOT_IMPLEMENTED to be returned in the correct scenario. All other flag values are errors, which it appears Windows ignores. Tested in Wine 7.2-2 Lutris. There were additional problems which prevented running the software under my system's Wine 7.22. -- 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

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