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

[Bug 53623] New: Resident Evil 7 has broken rendering in DX11 mode
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53623 Bug ID: 53623 Summary: Resident Evil 7 has broken rendering in DX11 mode Product: Wine Version: 7.1 Hardware: x86-64 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com CC: z.figura12(a)gmail.com Regression SHA1: b2087112144ca945d1df9ab9d82ef8a9f6e6d00b Distribution: --- Created attachment 73021 --> https://bugs.winehq.org/attachment.cgi?id=73021 example Using 'dx11_non-rt' branch. -- 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 53918] New: Building with external PE libraries fails when static libraries are also installed
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53918 Bug ID: 53918 Summary: Building with external PE libraries fails when static libraries are also installed Product: Wine Version: 7.20 Hardware: x86-64 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: build-env Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com Regression SHA1: 6a912649188a765d0c58e8b26e093fb0c31b3e3d Distribution: --- The basic problem is that winegcc, when passed e.g. "-L/usr/x86_64-w64-mingw32/lib -lvkd3d", looks up that library in the search path, finds libvkd3d.a, and tries to link to it. The mingw-w64 linking process, at least for vkd3d (but presumably others as well), provides both "libvkd3d.a" and "libvkd3d.dll.a". The former is a static library, and the latter is essentially an import library for libvkd3d-1.dll. Normal mingw-w64 gcc, when passed -lvkd3d, links to the latter, according to the search path specified in [1] s.v. "direct linking to a dll". winegcc does not know about .dll.a and hence finds the static library first. This worked before 6a912649 because winegcc would try to find a library ending in ".cross.a", fail to find *any* vkd3d libraries, and just leave the linker argument as "-lvkd3d". Given this, an obvious solution is to teach winegcc about the ld linker path. However, I find myself asking—why are we trying to rewrite the command line at all? Why can't we just let mingw-w64 gcc work by itself? winegcc is, naturally, devoid of any comments, and as far as I can tell the code doesn't actually *do* anything that depends on the library type or path, so I started looking in the git history, but unfortunately was only partly able to answer the question. Here is what I found: * c7a210bc2f27 forces the use of library paths if -mno-cygwin is set (in addition to some other conditions). The commit message specifies that we *can* do this (due to our use of -nodefaultlibs), but doesn't specify why we *need* to do this. Jacek, can you by chance explain? * 33147c947500 forces the use of library paths (sort of) if lib_suffix is set, which makes sense—gcc won't be able to find any libraries if we are overriding lib_suffix. * 870d490eecdb forces the use of library paths for all winelib DLLs, so that "-lfoo" links to "foo/foo.dll". This makes sense, but is also now obsolete—our makefiles pass the direct paths. Or do we want to support winelib users outside of wine including from the build tree? * 006ec80dd5c1 introduces the logic in the first place, forcing the use of library paths for static libraries. This was written by Dimitrie O. Paun, with the comment "For static libs (.a) we need to pass the actual filename to winebuild, not a -l switch." No further explanation is given. Alexandre, can you please shed light on this? [1] https://sourceware.org/binutils/docs-2.39/ld/WIN32.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 6

[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 53406] New: Had been running 7.10 Fedora version no problem, but today updated to 7.12 broke??
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53406 Bug ID: 53406 Summary: Had been running 7.10 Fedora version no problem, but today updated to 7.12 broke?? Product: Wine Version: 7.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mikes(a)kuentos.guam.net Distribution: --- Did the dnf update and it was mostly the 7.12 version of wine from Fedora. Upgrade went thru fine, or so I thought. But primary program I use the wine to run is Pegasus Mail. After running it, it came up fine, and had it download new mail. Was 14 new messages, went to view them, but just got a spinning little circle icon. No error message shows, top and ps -ef don't seem to show anything. Had to kill program to close it. Tried different message, but all did the same thing. Restarted machine, same result. Only option I could think of was dnf downgrade wine* That ran fine, but installed wine-core-6.16-1.fc35, thought it would have gone to 7.10 that had been working fine before todays upgrade to 7.12? Since no error shows other than ivy bridge is incomplete, so can't report more than just getting a spinning icon and no response. Have never done a downgrade before, so not sure why it went to 6.16. Just to see what would happen type dnf upgrade wine* and it showed that it would intall that 7.12 version, so I responsed N. Don't know if there is some option I could run to hopefully get more details on what is going on. But after the downgrade the messages view fine. Have it set to using windows 10 option, so not sure if using 8.1 or some other option might make a different. -- 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 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 46500] New: Cogpack - Exercises can' t be run - Error 380 - Invalid property value
by wine-bugs＠winehq.org 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=46500 Bug ID: 46500 Summary: Cogpack - Exercises can't be run - Error 380 - Invalid property value Product: Wine Version: 4.0-rc6 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: maiktapwagner(a)aol.com Distribution: --- Created attachment 63348 --> https://bugs.winehq.org/attachment.cgi?id=63348 Console output on wine 4.0-rc6 Hello everyone, the application in question can be downloaded from and also has a demo version available which has the same "symptoms" as the full version: http://www.markersoftware.com/USA/demoinfo.htm#Download It returns an error message "invalid property value" with an error code of 380. Console output is attached and an entry for the AppDB has been submitted as well. -- 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 8

[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

[Bug 53485] New: Cursor is missing in Visio 2003 when editing text
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53485 Bug ID: 53485 Summary: Cursor is missing in Visio 2003 when editing text Product: Wine Version: 7.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: winebugs(a)copysoft.org Distribution: --- In Visio 2003 running under Wine 7.14 the text cursor is not displayed when editing text. How to reproduce: Open visio, create a new document, select the text tool, type on the screen, the cursor does not appear. Text input is fine, text is rendered fine and can be selected, copied and pasted, all that is missing is the cursor. I've run a bisect and found that this commit appears to be responsible for the regression: commit b8732c80b112af388264ac84d726aad09d93c8c6 Author: Zebediah Figura <zfigura(a)codeweavers.com> Date: Tue Apr 26 16:06:04 2022 +0100 win32u: Move caret APIs from user32. Signed-off-by: Zebediah Figura <zfigura(a)codeweavers.com> Signed-off-by: Jacek Caban <jacek(a)codeweavers.com> Signed-off-by: Huw Davies <huw(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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 53894] New: user32:sysparams - test_WM_DISPLAYCHANGE() times out on Windows 7+
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53894 Bug ID: 53894 Summary: user32:sysparams - test_WM_DISPLAYCHANGE() times out on Windows 7+ Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com user32:sysparams - test_WM_DISPLAYCHANGE() times out on Windows 7+: sysparams.c:2474: Test failed: WaitForSingleObject returned 0x102 sysparams.c:2475: Test failed: got WM_DISPLAYCHANGE bpp 4294967295 See: https://test.winehq.org/data/patterns.html#user32:sysparams The failures started on 2022-09-23 which saw two commits to this test. However the test does not fail when run standalone so the commits may not be directly responsible. -- 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 53744] New: WM_SETTEXT between ANSI programs treating LPARAM as Unicode causing name corruption
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53744 Bug ID: 53744 Summary: WM_SETTEXT between ANSI programs treating LPARAM as Unicode causing name corruption Product: Wine Version: 7.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: dark(a)darkok.xyz Distribution: --- When sending a WM_SETTEXT to and from a program expecting ANSI strings, it seems to be interpreting the string as Unicode, causing the window title to become corrupted. Sending a wide string over then makes it work on Wine, but not Windows. The issue was introduced in Wine 7.6, and still exists in the latest versions. -- 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