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.
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.
https://bugs.winehq.org/show_bug.cgi?id=53300
Bug ID: 53300
Summary: Controller response delayed
Product: Wine
Version: 7.11
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: win32u
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
CC: z.figura12(a)gmail.com
Regression SHA1: 0a930890192726e64bc6207c0d04f44e4c849b7d
Distribution: ---
Lots of '00b0:err:rawinput:add_device Failed to get collection descriptor,
status 0xc00000e8.' during gameplay.
--
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.
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.
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.
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.
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.
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.
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.
https://bugs.winehq.org/show_bug.cgi?id=53980
Bug ID: 53980
Summary: httpapi:httpapi sometimes crashes testing overlapped
I/O with the v2 server in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: httpapi
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
httpapi:httpapi sometimes crashes testing overlapped I/O with the v2 server in
Wine:
httpapi.c:1539: Test marked todo: Got error 120.
Unhandled exception: page fault on write access to 0x00000000 in 32-bit code
(0x7b020c3f).
[...]
Backtrace:
=>0 0x7b020c3f GetOverlappedResultEx+0x9a(file=<couldn't compute location>,
overlapped=<couldn't compute location>, result=<couldn't compute location>,
timeout=<couldn't compute location>, alertable=<couldn't compute location>)
[Z:\home\winetest\tools\testbot\var\wine\dlls\kernelbase\file.c:3184] in
kernelbase (0x0062f0c8)
1 0x7b020d4a GetOverlappedResult+0x45(file=<couldn't compute location>,
overlapped=<couldn't compute location>, result=<couldn't compute location>,
wait=<couldn't compute location>)
[Z:\home\winetest\tools\testbot\var\wine\dlls\kernelbase\file.c:3144] in
kernelbase (0x0062f118)
2 0x703826c7 HttpReceiveHttpRequest+0x267(queue=<couldn't compute location>,
id=<couldn't compute location>, flags=<couldn't compute location>,
request=<couldn't compute location>, size=<couldn't compute location>,
ret_size=<couldn't compute location>, ovl=<couldn't compute location>)
[Z:\home\winetest\tools\testbot\var\wine\dlls\httpapi\httpapi_main.c:360] in
httpapi (0x0062f1b8)
3 0x0040f6d1 in httpapi_test (+0xf6d1) (0x0062fdb8)
See https://test.winehq.org/data/patterns.html#httpapi:httpapi
There are only four known instances of this crash, meaning it's pretty rare and
thus hard to reproduce:
* 2022-08-30 (fg-deb64-32) This is also the first known instance.
* 2022-11-14 (fg-deb64-32)
* 2022-11-16 (debian11-win32-de-DE)
* 2022-11-17 (debian11-win32) MR!1397
--
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.