https://bugs.winehq.org/show_bug.cgi?id=54020
Bug ID: 54020
Summary: The 32-bit ntdll:wow64 fails on Windows 11
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
The 32-bit ntdll:wow64 fails on Windows 11:
wow64.c:254: Test failed: wrong len 0
wow64.c:255: Test failed: wrong teb 0000004C / 00000000
wow64.c:258: Test failed: GdiBatchCount not set
wow64.c:282: Test failed: wrong peb 00000000 / 00000002
wow64.c:285: Test failed: wrong len 0
wow64.c:295: Test failed: wrong len 0
wow64.c:301: Test failed: wrong ImagePathName ptr 00000000 / 00000000-00000000
wow64.c:302: Test failed: wrong CommandLine ptr 00000000 / 00000000-00000000
wow64.c:303: Test failed: wrong WindowTitle ptr 00000000 / 00000000-00000000
wow64.c:304: Test failed: wrong Desktop ptr 00000000 / 00000000-00000000
wow64.c:305: Test failed: wrong ShellInfo ptr 00000000 / 00000000-00000000
wow64.c:331: Test failed: debugging failed
wow64.c:333: Test failed: wrong len 0
wow64.c:460: cs 0023 ss 002b fs 0053
wow64.c:782: Test failed: unknown module 7ffb1ed00000 L"wow64base.dll" found
wow64.c:782: Test failed: unknown module 7ffb20100000 L"wow64con.dll" found
See https://test.winehq.org/data/patterns.html#ntdll:wow64
The values are pretty stable from one run to the next but do change from time
to time (causing false positives). Note also that the 64-bit version fails on
Windows 11 too but the failures there are pretty different (see bug 54019).
--
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=53818
Bug ID: 53818
Summary: foobar2000 crashes shortly after startup
Product: Wine
Version: 7.19
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: matthias.grobarek(a)posteo.de
Distribution: ---
Created attachment 73344
--> https://bugs.winehq.org/attachment.cgi?id=73344
winedbg output
After starting foobar2000, it quickly crashes after a few seconds, no matter
what you do. Wine 7.18 and 7.17 are not affected.
I’m using wine-staging (no matter the version) on Gentoo Linux (kernel 6.0.2),
compiled for both 32bit and 64bit, with the following flags activated: x, alsa,
fontconfig, mshtml, gstreamer, mingw, mscoree, gettext, openal, opengl, sdl,
gnutls, freetype, udev, dbus, unwind, usb, vulkan, xcomposite.
I attached the output of winedbg and also the crash log and dump that
foobar2000 itself produces. If you need any more information, please tell me
what exactly I should do.
--
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=53526
Bug ID: 53526
Summary: kernel32:sync - test_timer_queue() occasionally fails
to delete the timer on Windows 10
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:sync - test_timer_queue() occasionally fails to delete the timer on
Windows 10:
sync.c:1135: Test failed: DeleteTimerQueueTimer
https://test.winehq.org/data/patterns.html#kernel32:sync
This failure happened twice:
* 2022-05-27 w10pro64-de-64
* 2022-08-04 w10pro64-he-64
--
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=53488
Bug ID: 53488
Summary: The dxgi:dxgi output is too big on debiant
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
The dxgi:dxgi output is too big in Wine.
It used to be about 24 KB but the commit below pushed it to 34 KB, over the 32
KB limit.
Then on 2022-07-22 another commit improved the situation on debian11 but not on
debiant where the size has not changed since the commit below.
commit 184ff3bfbb4be3e3fbcfaaba3ec7095d2d885882
Author: Nikolay Sivov <nsivov(a)codeweavers.com>
Date: Sat Jun 11 19:36:20 2022 +0300
dxgi: Create DXGI resource object, optionally supporting surface
interfaces.
Signed-off-by: Nikolay Sivov <nsivov(a)codeweavers.com>
dlls/d3d11/d3d11_private.h | 4 +-
dlls/d3d11/tests/d3d11.c | 7 -
dlls/d3d11/texture.c | 130 +++++++-------
dlls/dxgi/Makefile.in | 2 +-
dlls/dxgi/device.c | 24 +--
dlls/dxgi/dxgi_private.h | 11 +-
dlls/dxgi/resource.c | 423 +++++++++++++++++++++++++++++++++++++++++++++
dlls/dxgi/surface.c | 296 -------------------------------
dlls/dxgi/tests/dxgi.c | 34 ++--
include/wine/winedxgi.idl | 7 +-
10 files changed, 526 insertions(+), 412 deletions(-)
create mode 100644 dlls/dxgi/resource.c
delete mode 100644 dlls/dxgi/surface.c
--
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=54553
Bug ID: 54553
Summary: mmdevapi:propstore - The 32-bit
test_setvalue_on_wow64() fails on Windows 10 2004+
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: mmdevapi
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
mmdevapi:propstore - The 32-bit test_setvalue_on_wow64() fails on Windows 10
2004+:
propstore.c:186: Test failed: Wrong error when opening mmdevices Render key: 0
See propstore.c:186: Test failed: Wrong error when opening mmdevices Render
key: 0
As far as I can tell what this means is that the assumption that "should NOT
find the key in 32-bit view" is incorrect on Windows 10 2004+.
So maybe the old behavior should be considered to be broken() nowadays?
--
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=54078
Bug ID: 54078
Summary: ntdll:pipe - test_blocking() sometimes fails in Wine
when the pipe is not signaled
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
ntdll:pipe - test_blocking() sometimes fails in Wine when the pipe is not
signaled:
pipe.c:1769: Test marked todo: client is not signaled
pipe.c:1751: Test failed: pipe is not signaled
pipe.c:1769: Test marked todo: client is not signaled
pipe.c:1770: Test failed: pipe is not signaled
See https://test.winehq.org/data/patterns.html#ntdll:pipe
Here is this failure's nightly WineTest run history:
* There was no failure in June and July.
* The first known failure happened on 2022-08-13, the next on 2022-08-18.
* The third failure happened on 2022-09-23.
* The fourth on 2022-11-04 which was followed by 9 more in November.
So it's likely something changed in early August-ish that introduced this
failure. But there has been a further change in November that makes it more
frequent (maybe the latter is because the TestBot now runs two VMs at a time so
the host is more busy, though that started a bit earlier, on 2022-10-25).
This failure also happens in the GitLab CI.
--
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=53974
Bug ID: 53974
Summary: d3drm:d3drm sometimes crashes after failing to create
the IDirect3DRMDevice* interface in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
d3drm:d3drm sometimes crashes after failing to create the IDirect3DRMDevice*
interface in Wine:
d3drm.c:4600: Test failed: Cannot create IDirect3DRMDevice interface, hr
0x8007000e.
d3drm.c:4602: Test failed: expected ref2 > ref1, got ref1 = 1 , ref2 = 1.
d3drm.c:4604: Test failed: Expected surface_ref2 > surface_ref1, got
surface_ref1 = 1, surface_ref2 = 1.
Unhandled exception: page fault on read access to 0x00000000 in 32-bit code
(0x0040e52b).
[...useless backtrace...]
d3drm.c:4776: Test failed: Cannot create IDirect3DRMDevice2 interface, hr
0x8007000e.
d3drm.c:4778: Test failed: expected ref3 > ref1, got ref1 = 1 , ref3 = 1.
d3drm.c:4782: Test failed: Expected surface_ref2 > surface_ref1, got
surface_ref1 = 1, surface_ref2 = 1.
Unhandled exception: page fault on read access to 0x00000000 in 32-bit code
(0x004106c1).
[...useless backtrace...]
d3drm.c:4407: Test failed: Cannot create IDirect3DRMDevice3 interface, hr
0x8007000e.
d3drm.c:4409: Test failed: expected ref3 > ref1, got ref1 = 1 , ref3 = 1.
d3drm.c:4413: Test failed: expected cref2 > cref1, got cref1 = 1 , cref2 = 1.
Unhandled exception: page fault on read access to 0x00000000 in 32-bit code
(0x0041290a).
[...useless backtrace...]
See https://test.winehq.org/data/patterns.html#d3drm:d3drm
The two "expected..." failures are not always present. This has been seen on
debian11, debiant but also fgtb-debian11 and gitlab-debian. So it's not
specific to dual-screen configurations nor to QEmu's QXL driver. But it seems
to only happen on "virtual GPUs" (gitlab-debian uses Xorg's dummy driver).
--
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=53528
Bug ID: 53528
Summary: ntdll:info - test_query_kerndebug() fails on Windows 8
to 10 1709
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
ntdll:info - test_query_kerndebug() fails on Windows 8 to 10 1709:
info.c:1097: Test failed: Expected STATUS_SUCCESS, got 80000002
info.c:1102: Test failed: Expected STATUS_SUCCESS, got 80000002
https://test.winehq.org/data/patterns.html#ntdll:info
The failures started on 2022-07-26.
--
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=53182
Bug ID: 53182
Summary: shell32:shelllink - A save(NULL, TRUE) fails randomly
in test_load_save() on Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: shell32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
A save(NULL, TRUE) fails randomly in test_load_save() on Wine:
shelllink.c:775: Test failed: save(NULL, TRUE) failed (0x80070020)
https://test.winehq.org/data/patterns.html#shell32:shelllink
This is probably the same issue as bug 28290, the only difference being that it
does not happen at a point that leads to a NULL pointer access.
--
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=52948
Bug ID: 52948
Summary: gdi32:font - test_EnumFonts() fails on Arial Bold on
Windows in Russian
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: gdi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
gdi32:font - test_EnumFonts() fails on Arial Bold on Windows in Russian:
font.c:5409: Test failed: font Arial Bold is not enumerated
font.c:5412: Test failed: expected FW_BOLD got 400
font.c:5419: Test failed: font Arial Bold Italic is not enumerated
font.c:5421: Test failed: expected Arial got Arial Bold
font.c:5422: Test failed: expected FW_BOLD got 400
https://test.winehq.org/data/patterns.html#gdi32:font
Maybe this can happen in other locales, but among those that are tested this
only happens with the Russian one (w10pro64-ru).
--
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.