https://bugs.winehq.org/show_bug.cgi?id=54170
Bug ID: 54170
Summary: 20XX: invisible character
Product: Wine
Version: 7.19
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: z.figura12(a)gmail.com
Regression SHA1: 5f1cbb1b85e7d92b6c783a32ae85ca2902296481
Distribution: ArchLinux
Created attachment 73693
--> https://bugs.winehq.org/attachment.cgi?id=73693
terminal output
The character you are controlling in the game is invisible.
The buttons in the menus lack a background pattern.
This bug has appeared since
commit 5f1cbb1b85e7d92b6c783a32ae85ca2902296481
Author: Zebediah Figura <zfigura(a)codeweavers.com>
Date: Sat Jul 30 19:10:09 2022 -0500
d3d9: Use a separate draw texture for managed resources.
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=52954
The game needs native d3dcompiler_47.dll to start.
This was tested with the Epic Games version (v1.42.13) but probably the Steam
version is also affected:
https://store.steampowered.com/app/322110/20XX/
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce GT 730/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 470.161.03
OpenGL core profile shading language version string: 4.60 NVIDIA
wine-8.0-rc1-75-g17e5ff74308
--
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=54023
Bug ID: 54023
Summary: d3d11:d3d11 - test_dynamic_map_synchronization() fails
on w11pro64_nv
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
d3d11:d3d11 - test_dynamic_map_synchronization() fails on w11pro64_nv:
d3d11.c:34427: Test failed: Got 0xff0000ff, expected 0xff00ff00 at (3, 5, 0),
sub-resource 0.
See https://test.winehq.org/data/patterns.html#d3d11:d3d11
Note: w11pro64_nv is the TestBot's NVIDIA RTX3050 PCI passthrough Windows 11
21H2 VM. The plain QXL (QEmu), and AMD PCI passthrough test configurations have
d3d11:d3d11 failures too but in other test functions.
--
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=53995
Bug ID: 53995
Summary: d2d1:d2d1 runs out of GL memory and crashes on the
debian 11 VM
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: d2d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
d2d1:d2d1 runs out of GL memory and crashes on the debian 11 VM:
d2d1.c:7145: Test marked todo: Figure does not match.
Unhandled exception: page fault on write access to 0x00000000 in 32-bit code
(0x6ab30fe4).
[...]
Backtrace:
=>0 0x6ab30fe4 memset+0x24(dst=0x000000000, c=0, n=0x12c000)
[Z:\home\winetest\tools\testbot\var\wine\dlls\msvcrt\string.c:3205] in ucrtbase
(0x0685f908)
1 0x008a9073 wined3d_texture_load_location+0x423(texture=002CB990,
sub_resource_idx=0, context=00289F90, location=0x8)
[Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\texture.c:862] in wined3d
(0x0685f9a8)
2 0x00897fce surface_cpu_blt+0x9ee(dst_texture=002CB990,
dst_sub_resource_idx=0, dst_box=0685FB38, src_texture=0028D170,
src_sub_resource_idx=0, src_box=0685FB50, flags=0x20000000, fx=0685FB68,
filter=WINED3D_TEXF_POINT)
[Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\surface.c:752] in wined3d
(0x0685faf8)
3 0x00899ac2 cpu_blitter_blit+0xc2(blitter=002BB820,
op=WINED3D_BLIT_OP_RAW_BLIT, context=00289F90, src_texture=0028D170,
src_sub_resource_idx=0, src_location=0x10, src_rect=0685FE10,
dst_texture=002CB990, dst_sub_resource_idx=<is not available>,
dst_location=0x8, dst_rect=0685FE20, color_key=00000000,
filter=WINED3D_TEXF_POINT, resolve_format=00000000)
[Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\surface.c:1328] in
wined3d (0x0685fb98)
4 0x008b7622 ffp_blitter_blit+0xa2(blitter=002BB838,
op=WINED3D_BLIT_OP_RAW_BLIT, context=00289F90, src_texture=0028D170,
src_sub_resource_idx=0, src_location=0x10, src_rect=0685FE10,
dst_texture=002CB990, dst_sub_resource_idx=0, dst_location=0x8,
dst_rect=0685FE20, colour_key=00000000, filter=WINED3D_TEXF_POINT,
resolve_format=00000000)
[Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\texture.c:6190] in
wined3d (0x0685fc58)
5 0x0085d36d glsl_blitter_blit+0x1ad(blitter=002BB850,
op=WINED3D_BLIT_OP_RAW_BLIT, context=00289F90, src_texture=0028D170,
src_sub_resource_idx=0, src_location=0x10, src_rect=0685FE10,
dst_texture=002CB990, dst_sub_resource_idx=0, dst_location=0x8,
dst_rect=0685FE20, colour_key=00000000, filter=WINED3D_TEXF_POINT,
resolve_format=00000000)
[Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\glsl_shader.c:13270] in
wined3d (0x0685fd78)
6 0x0089ada1 texture2d_blt+0x3c1(dst_texture=002CB990,
dst_sub_resource_idx=0, dst_box=05B678B4, src_texture=0028D170,
src_sub_resource_idx=0, src_box=05B678D4, flags=0x20000000, fx=05B678F0,
filter=WINED3D_TEXF_POINT)
[Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\surface.c:1639] in
wined3d (0x0685fe48)
7 0x0081b8ad wined3d_cs_exec_blt_sub_resource+0xcd(cs=05B50020,
data=05B678A8) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\cs.c:2579]
in wined3d (0x0685fec8)
8 0x0081d37b wined3d_cs_command_unlock(queue=<internal error>, cs=<internal
error>) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\cs.c:3310] in
wined3d (0x0685ff28)
9 0x0081d37b wined3d_cs_execute_next+0x53(ctx=<couldn't compute location>)
[Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\cs.c:3309] in wined3d
(0x0685ff28)
10 0x0081d37b wined3d_cs_run+0x13b(ctx=<couldn't compute location>)
[Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\cs.c:3376] in wined3d
(0x0685ff28)
[...]
7145 is the most common last trace seen, though 7033 also appears at least
once, but running with WINETEST_REPORT_SUCCESS I get different locations.
See https://test.winehq.org/data/patterns.html#d2d1:d2d1
Furthermore when reproducing this I saw out-of-memory traces right before the
crash. For instance:
d2d1.c:601: Test succeeded
01d8:err:d3d:wined3d_debug_callback 00291C38: "GL_OUT_OF_MEMORY in
glBufferStorage".
01d8:err:d3d:wined3d_debug_callback 00291C38: "GL_INVALID_VALUE in
glMapBufferRange(offset 0 + length 67108864 > buffer_size 0)".
01d8:err:d3d:wined3d_allocator_chunk_gl_map Failed to map chunk memory.
01d8:err:d3d:wined3d_bo_gl_map Failed to map chunk.
01d8:err:d3d:wined3d_context_gl_map_bo_address Failed to map bo.
wine: Unhandled page fault on write access to 00000000 at address 6AB30FE4
(thread 01d8), starting debugger...
It's not clear why only the debian11 VM is impacted: it has a dual-screen
configuration but so does debiant so it does not appear to be a multi-monitor
thing, and this does not happen on fgtb-debian11 or debian11b so it's not a
Debian version issue.
--
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=53752
Bug ID: 53752
Summary: Rayman 3: glitched graphics (black textures)
Product: Wine
Version: 7.3
Hardware: x86-64
URL: https://archive.org/download/rayman-3-pc-demo/Rayman3_
PC-Demo.zip
OS: Linux
Status: NEW
Keywords: download, regression
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: z.figura12(a)gmail.com
Regression SHA1: 1b1b03055db8bf03c6783d4fcb19abf670d53338
Distribution: ---
There are lots of black textures in Rayman 3 thus not so much of the game can
be seen.
Can be reproduced with the demo: the issue is already present in the main menu.
According to my testing the problem appeared with
commit 1b1b03055db8bf03c6783d4fcb19abf670d53338
wined3d: Try to allocate new OpenGL BOs from the client thread for DISCARD
maps.
With the previous commit in-game scenery looks good.
Workaround: disable hardware TnL in the video settings utility called
R3_Setup_DX8.exe in the demo.
Rayman3_PC-Demo.zip (184M)
md5: d6d3c2d76931feff73f56295a0dee6a3
Still present in wine-7.18-120-g001665d7354.
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce GT 730/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 470.141.03
OpenGL core profile shading language version string: 4.60 NVIDIA
--
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=53640
Bug ID: 53640
Summary: Bully: Scholarship Edition hangs on loading screen and
doesn't play intros
Product: Wine
Version: 7.15
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: quartz
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
CC: rbernon(a)codeweavers.com
Regression SHA1: 4608e1e1257a377cd554a0e885368e3feb7d286f
Distribution: ---
Loading screen is shown until mouse is clicked then you're getting to main
menu.
It's back to normal after deleting the registry path.
--
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=47828
Bug ID: 47828
Summary: regedit: Random crashes on selecting an entry
(thread-related?)
Product: Wine
Version: 4.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ed7-aspire4925(a)hotmail.com
Distribution: ---
Created attachment 65333
--> https://bugs.winehq.org/attachment.cgi?id=65333
commented logs from the various crashes
As described above. By selection I meant double-clicking or pressing [return]
on a highlighted entry
Sometimes the "debuggee" works, sometimes it doesn't.
Sometimes the back trace shows, sometimes it doesn't.
Sometimes the application crash window doesn't even appear.
Definitely a threading issue...
The crash occurs at around the eighth key selection.
--
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=48322
Bug ID: 48322
Summary: World of Warcraft Classic: Mouse movement can block
keydown events from registering
Product: Wine-staging
Version: 5.0-rc1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: m.schaefer8(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
This seems to be a regression:
I've noticed this in the game World of Warcraft Classic. In Wine 4.17.r11
mouse/keyboard behave as expected. With 5.0-rc1 when keeping the right mouse
button clicked *and* moving the mouse (changing character orientation and view
orientation with the mouse) all other keydown events are ignored. Moving the
mouse by itself does not block keydown events; keeping the button pressed but
not moving the mouse also does not block keydown events.
Keyup events are processed as normal.
Software I'm using is specifically Wine-Staging with TKG patches.
Having never filed bugs for Wine before, please inform me if you require
additional information, logs (and how to acquire said logs), etc.
--
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=47438
Bug ID: 47438
Summary: Bloodstained: Ritual of the Night freeze at
whitescreen because of mfplat commit
eff5a7aebc65e98cacf0d6a0ccc6101ffa552aa0
Product: Wine
Version: 4.4
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: mfplat
Assignee: wine-bugs(a)winehq.org
Reporter: GloriousEggroll(a)gmail.com
Distribution: ---
Bloodstained: Ritual of the Night shows a white screen upon opening and freezes
there due to the following commit that was made to mfplat:
eff5a7aebc65e98cacf0d6a0ccc6101ffa552aa0
mfplat: Implement media event queue
I did a bisect between 4.3 and 4.4 as it works in 4.3, and found that commit to
be the cause.
As a lot of work has been done on mfplat, and this is implementing a rather
large feature, its not some thing that seems to be easily revertible.
Using winetricks mf results in the game just popping up an error.
--
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=41339
Bug ID: 41339
Summary: Minor regression: Wine loads with
"/wine/dlls/ntdll/loader.c: loader_section" errors
when creating a new prefix or running an application
Product: Wine
Version: 1.9.18
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fjfrackiewicz(a)gmail.com
Distribution: ---
I noticed that with Wine 1.9.18, whenever I either created a new prefix or ran
an application I would receive the following errors in my terminal:
err:ntdll:RtlpWaitForCriticalSection section 0x7bcf4f84
"../../../wine/dlls/ntdll/loader.c: loader_section" wait timed out in
thread 001d, blocked by 001e, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x7bcf4f84
"../../../wine/dlls/ntdll/loader.c: loader_section" wait timed out in
thread 001c, blocked by 001e, retrying (60 sec)
This issue was also brought up by Bruno Jesus in the wine-devel mailing list
here: https://www.winehq.org/pipermail/wine-devel/2016-September/114672.html
Since I am not the only one experiencing this, I decided to run a regression
test. According to the git bisect I have performed this issue first appears in
wine-1.9.17-149-gd2b782f
The bad commit in question:
commit d2b782f4e4f0efa6e783031d57cf98789cdc4742
Author: Henri Verbeet <hverbeet(a)codeweavers.com>
Date: Fri Aug 26 13:51:22 2016 +0200
ddraw: Rename "wineD3DVertexBuffer" to "wined3d_buffer".
Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
:040000 040000 719fe9426a27661606b40339c96588fa09e3385e
07af319b9fd2e194b9a5990a0c09277d34ed42bb M dlls
--
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=54191
Bug ID: 54191
Summary: Agarest 1 stopped showing Videos after implementing
ASF Reader filter
Product: Wine
Version: 8.0-rc1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: j-r(a)online.de
Distribution: ---
The intro videos of Agarest 1 are no longer shown after
commit 4608e1e1257a377cd554a0e885368e3feb7d286f
Author: Rémi Bernon <rbernon(a)codeweavers.com>
Date: Fri May 20 21:48:59 2022 +0200
qasf: Register ASF Reader filter media type.
Looks like the new feature leads the game onto a new path that ultimately fails
with messages like
winegstreamer warning: audioconvert0: not negotiated
winegstreamer warning: audioconvert0:
../../../../libs/gst/base/gstbasetransform.c(1423):
gst_base_transform_reconfigure (): /GstBin:bin0/GstAudioConvert:audioconvert0:
not negotiated
winegstreamer warning: videoconvert1: not negotiated
winegstreamer warning: videoconvert1:
../../../../libs/gst/base/gstbasetransform.c(1423):
gst_base_transform_reconfigure (): /GstBin:bin0/GstVideoConvert:videoconvert1:
not negotiated
Perhaps my gstreamer 1.16 is just too old? But then it'd be nice if configure
gave a warning/error.
--
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.