wine-bugs June 2022

wine-bugs@winehq.org

1 participants
3997 discussions

[Bug 52997] New: Integration of D3D12 support with a PE build of vkd3d causes a crash in Steam Overlay.
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=52997 Bug ID: 52997 Summary: Integration of D3D12 support with a PE build of vkd3d causes a crash in Steam Overlay. Product: Wine Version: 7.8 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: cmccarthy(a)codeweavers.com Distribution: --- Launching a D3D12 game with Steam Overlay enabled results in a null pointer dereference right after a call to D3D11On12CreateDevice(). Changing the returned values alters the crash location. This is a regression caused by integration of a vkd3d PE build in commit 5d62e5603. The call to D3D11On12CreateDevice() doesn't occur when using an ELF vkd3d build. -- 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 8

[Bug 52873] New: oleaut32:typelib fails in Wine in Hindi
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=52873 Bug ID: 52873 Summary: oleaut32:typelib fails in Wine in Hindi Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: oleaut32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- oleaut32:typelib fails in Wine in Hindi: typelib.c:2514: Test failed: got: L"default?" typelib.c:2526: Test failed: got: L"default?" typelib.c:3314: Test failed: got: L"default?" typelib.c:3326: Test failed: got: L"default?" https://test.winehq.org/data/patterns.html#oleaut32:typelib A bisect shows that the test started failing with the commit below: commit e81327358a26b160740b3421a4c7f300b4d2f06f Author: Alexandre Julliard <julliard(a)winehq.org> Date: Wed Apr 13 15:13:16 2022 +0200 kernelbase: Move codepage initialization to ntdll. Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> Oddly this is the same commit as for a recent set of vbscript:run failures (see bug 52872). -- 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 52779] New: Construction Set Extender crash with an Assertion Error in wine 7.5
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=52779 Bug ID: 52779 Summary: Construction Set Extender crash with an Assertion Error in wine 7.5 Product: Wine Version: 7.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lorenzofer(a)live.it Distribution: --- Using wine 7.5 Consturction Set Extender (plugin for Oblivion Construction Set) crash with the following assertion Assertion failed: Data != ActiveComboBoxes.cend(), file Y:\CSE\Construction-Set-Extender\UIManager.cpp, line 623 Everything works fine with wine 7.4 There is no log except the common imm fixme and a lot of d3d:wined3d_check_device_format_conversion and d3d:state_linepattern_w that are present even in 7.4 Bisection in progress -- 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 12

[Bug 42797] New: ICU64 for VICE: No highlighted read/ write-colors in Memory-window.
by wine-bugs＠winehq.org 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=42797 Bug ID: 42797 Summary: ICU64 for VICE: No highlighted read/write-colors in Memory-window. Product: Wine Version: 2.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: enkorv(a)yahoo.com Distribution: --- Created attachment 57824 --> https://bugs.winehq.org/attachment.cgi?id=57824 terminal output when running ICU64.exe VICE is a Commodore 64 (and siblings) emulator. "ICU64 for VICE" is a hacking tool that piggybacks onto the emulator and shows memory maps in useful ways. When starting ICU64.exe it opens a small toolbar and starts the VICE emulator as well. When selecting Memory in the toolbar a window opens which shows the memory map of the Commodore 64. It should also highlight the memory read and writes as well as where the CPU is currently running, using color highlighting. This part doesn't work so the window just has a black background. You can still zoom in and out in the memory map (using mouse scroll-wheel) and see the values of the memory locations changing live. An example of how the color highlighting typically looks is here (could not find a clip of ICU64 for VICE, so this clip shows ICU64 for Frodo, which is another Commodore 64 emulator): https://www.youtube.com/watch?v=tjcvR5McmSg Testing and wine-environment: Ubuntu 16.10 - 4.8.0-46-generic wine-2.4 ICU64 needs Microsoft .NET Framework 2.0 (see http://icu64.blogspot.se/p/download.html ) WINEPREFIX=~/.winetest2017 WINEARCH=win32 wineboot WINEPREFIX=~/.winetest2017 winetricks dotnet2 ICU64 - https://sites.google.com/site/mathfigure/icu64vice23-v0.1.2.zip c89d54ea7d64834694c3590660dee69e0738a418 WinVICE 2.3 - https://sourceforge.net/projects/vice-emu/files/releases/binaries/windows/W… b2a7ffafbcef1ab159681002616d9cf819c1ef84 Download both, unzip into same folder and run ICU64.exe. -- 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 2

[Bug 31927] New: ws2_32: sock.c fails intermittently - 'Test succeeded inside todo block: GetQueuedCompletionStatus returned 0'
by wine-bugs＠winehq.org 21 Dec '22

21 Dec '22

http://bugs.winehq.org/show_bug.cgi?id=31927 Bug #: 31927 Summary: ws2_32: sock.c fails intermittently - 'Test succeeded inside todo block: GetQueuedCompletionStatus returned 0' Product: Wine Version: 1.5.14 Platform: x86 OS/Version: Linux Status: NEW Keywords: download, testcase Severity: minor Priority: P2 Component: winsock AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Classification: Unclassified Running in a loop for about 15 minutes, I got: sock.c:5385: Test succeeded inside todo block: GetQueuedCompletionStatus returned 0 sock.c:5386: Test succeeded inside todo block: Last error was 64 make: *** [sock.ok] Error 2 -- 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 10

[Bug 50013] New: MyPhoneExplorer 1.8.15 crashes
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=50013 Bug ID: 50013 Summary: MyPhoneExplorer 1.8.15 crashes Product: Wine Version: 5.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: maiktapwagner(a)aol.com Distribution: --- Created attachment 68435 --> https://bugs.winehq.org/attachment.cgi?id=68435 Backtrace (5.18 Staging) Hello everyone, Download-URL is at: https://fjsoft.at/de/ There is also an AppDB entry: https://appdb.winehq.org/objectManager.php?sClass=version&iId=34110 Installation works fine in a clean prefix with 5.18 (Staging) and the app requires vb6run installed to start it up. However it throws a fatal error. Backtrace is attached. -- 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 13

[Bug 49394] New: CED1401 USB function driver fails to install
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=49394 Bug ID: 49394 Summary: CED1401 USB function driver fails to install Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: usb Assignee: wine-bugs(a)winehq.org Reporter: alois.schloegl(a)gmail.com Distribution: --- Created attachment 67461 --> https://bugs.winehq.org/attachment.cgi?id=67461 WINEDEBUG=+wineusb,+setupapi,+ntoskrnl,+plugplay,+pid,+msgbox ./wine winsupp.exe I'm try to test the fix for bug 35903. In order to do so, I compiled wine from source (commit 634cb775c27b61ad6ce1fbe3e9972b0edfa31dcb), and used wine from the build directory. Now the installation of winsupp.exe is failing (this has been working before) with this error: 0020:0024:err:module:__wine_process_init L"Z:\\home\\schloegl\\src\\wineapps\\winsupp.8081a20bbc0c9b99f37b98a823ce07ab25f15e9d.exe" not supported on this system The log file is attached. -- 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 12

[Bug 52708] New: libs/xslt/libxslt/attributes.c:136:9: error: variadic functions must use the base AAPCS variant
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=52708 Bug ID: 52708 Summary: libs/xslt/libxslt/attributes.c:136:9: error: variadic functions must use the base AAPCS variant Product: Wine Version: 6.20 Hardware: arm OS: Linux Status: NEW Keywords: download, regression, source Severity: major Priority: P2 Component: build-env Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Regression SHA1: 9d9d4fcc379b2541a43b14f197facb6fa8c93ee8 Distribution: Debian gcc -c -o libs/xslt/libxslt/attributes.o libs/xslt/libxslt/attributes.c -Ilibs/xslt -Iinclude -Iinclude/msvcrt \ -I./libs/xml2/include -I./libs/xslt -DLIBXML_STATIC -DLIBXSLT_STATIC -D_UCRT -pipe \ -fcf-protection=none -fno-stack-protector -fno-strict-aliasing -Wno-packed-not-aligned -gdwarf-4 \ -fPIC -fasynchronous-unwind-tables -D_WIN32 -fno-builtin -fshort-wchar -Wno-format -g -O2 -mthumb -mfloat-abi=hard libs/xslt/libxslt/attributes.c: In function 'xsltNewAttrElem': libs/xslt/libxslt/attributes.c:136:9: error: variadic functions must use the base AAPCS variant 136 | xsltGenericError(xsltGenericErrorContext, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 137 | "xsltNewAttrElem : malloc failed\n"); | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ libs/xslt/libxslt/attributes.c: In function 'xsltNewUseAttrSet': libs/xslt/libxslt/attributes.c:217:9: error: variadic functions must use the base AAPCS variant 217 | xsltGenericError(xsltGenericErrorContext, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 218 | "xsltNewUseAttrSet : malloc failed\n"); | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ libs/xslt/libxslt/attributes.c: In function 'xsltResolveAttrSet.part.0': libs/xslt/libxslt/attributes.c:651:17: error: variadic functions must use the base AAPCS variant 651 | xsltGenericDebug(xsltGenericDebugContext, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 652 | "xsl:attribute-set : merging import for %s\n", name); | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ libs/xslt/libxslt/attributes.c: In function 'xsltResolveSASCallback': libs/xslt/libxslt/attributes.c:694:6: error: variadic functions must use the base AAPCS variant 694 | xsltGenericError(xsltGenericErrorContext, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 695 | "xsl:attribute-set : internal error, can't move imported " | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 696 | " attribute set %s\n", name); | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ libs/xslt/libxslt/attributes.c: In function 'xsltParseStylesheetAttributeSet': libs/xslt/libxslt/attributes.c:432:2: error: variadic functions must use the base AAPCS variant 432 | xsltGenericDebug(xsltGenericDebugContext, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 433 | "creating attribute set table\n"); | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ libs/xslt/libxslt/attributes.c:301:9: error: variadic functions must use the base AAPCS variant 301 | xsltGenericError(xsltGenericErrorContext, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 302 | "xsltNewAttrSet : malloc failed\n"); | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ libs/xslt/libxslt/attributes.c:473:6: error: variadic functions must use the base AAPCS variant 473 | xsltGenericDebug(xsltGenericDebugContext, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 474 | "add attribute to list %s\n", ncname); | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ libs/xslt/libxslt/attributes.c:518:3: error: variadic functions must use the base AAPCS variant 518 | xsltGenericDebug(xsltGenericDebugContext, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 519 | "xsl:attribute-set : %s adds use %s\n", ncname, curval); | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ libs/xslt/libxslt/attributes.c:555:5: error: variadic functions must use the base AAPCS variant 555 | xsltGenericDebug(xsltGenericDebugContext, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 556 | "updated attribute list %s\n", ncname); | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ libs/xslt/libxslt/attributes.c:399:2: error: variadic functions must use the base AAPCS variant 399 | xsltGenericError(xsltGenericErrorContext, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 400 | "xsl:attribute-set : name is missing\n"); | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ libs/xslt/libxslt/attributes.c:399:2: error: variadic functions must use the base AAPCS variant libs/xslt/libxslt/attributes.c: In function 'xsltResolveStylesheetAttributeSet': libs/xslt/libxslt/attributes.c:713:5: error: variadic functions must use the base AAPCS variant 713 | xsltGenericDebug(xsltGenericDebugContext, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 714 | "Resolving attribute sets references\n"); | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ libs/xslt/libxslt/attributes.c:722:3: error: variadic functions must use the base AAPCS variant 722 | xsltGenericDebug(xsltGenericDebugContext, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 723 | "creating attribute set table\n"); | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ libs/xslt/libxslt/attributes.c: In function 'xsltApplyAttributeSet': libs/xslt/libxslt/attributes.c:1172:13: error: variadic functions must use the base AAPCS variant 1172 | xsltGenericDebug(xsltGenericDebugContext, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1173 | "apply attribute set %s\n", curstr); | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ make: *** [Makefile:159245: libs/xslt/libxslt/attributes.o] Error 1 Specific to armv7l, without mingw: Linux blah 5.9.12 #1 SMP PREEMPT Tue Mar 30 23:29:49 CDT 2021 armv7l GNU/Linux gcc version 10.2.1 20210110 (Debian 10.2.1-6) with llvm-mingw-20211002 (self-compiled, there's no linux/armv7l binary build afaik), however, wine builds. -- 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 49517] New: Warframe crashes during loading before menu with wined3d, gives popup
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=49517 Bug ID: 49517 Summary: Warframe crashes during loading before menu with wined3d, gives popup Product: Wine Version: 5.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: GloriousEggroll(a)gmail.com Distribution: --- Created attachment 67648 --> https://bugs.winehq.org/attachment.cgi?id=67648 d3d popup error The game crashes during the initial loading screen and gives the attached popup message. Happens on both amd and nvidia. The launcher is also affected by https://bugs.winehq.org/show_bug.cgi?id=44985 in wined3d and can be worked around with WINEDLLOVERRIDES="libglesv2=d" to get the game to the launching/crashing point. -- 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 53028] New: gamepad buttons stopped working correctly
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53028 Bug ID: 53028 Summary: gamepad buttons stopped working correctly 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: piotr5(a)netscape.net Distribution: --- ever since upgrading to wine-7.0 my gamepad got reduced to having only 10 functioning buttons and just 5 axes are actually doing anything. I now downgraded to wine-6.0.2 and it has all 14 buttons and 6 axes again. (actually now there are 2 devices of the same name detected, both have 8 axes, the second device is spreading the last 2 axes into being horizontal, while the first correctly assigns a 2d-movement analogue to one axis and nothing to the other. so I disabled the 2nd one.) to be precise, "wine control.exe" has a program for testing my gamepad, and there wine-7.0 is showing me only 10 buttons and 8 axes, of which only 5 are moving. in some game I had assigned one of the missing keys to an action and moving the axis which isn't perceived by wine sometimes triggers that missing button -- cannot see anything like that in this test program. I'm on gentoo linux, wine-vanilla is the only package providing wine there, and stable versions are just 6.0.2 and 7.0. installing newer versions doesn't work for me since it needs vulkan (winegcc aborts with function vkd3d_* not defined errors in wined3d.spec) which I have not installed. is it worth upgrading, or has that joystick bug not been fixed yet? -- 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

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 June 2022