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.
https://bugs.winehq.org/show_bug.cgi?id=51848
Bug ID: 51848
Summary: Performance Regression in Secondhand Lands
Product: Wine
Version: 6.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: escomk3(a)hotmail.com
Distribution: ---
After 4261369e5d8 [1], FPS will be near zero, and the game area will be black,
with the actual should-be content sometimes appearing and disappearing.
Standard output with default'ish debug channels doesn't show any difference
with a build prior to this commit.
1.
https://source.winehq.org/git/wine.git/commit/4261369e5d8f1d71e8d2074747515…
--
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=54003
Bug ID: 54003
Summary: vbscript:run sometimes fails on Windows UTF-8 locales
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: vbscript
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
vbscript:run sometimes fails on UTF-8 locales:
=== w10pro64_en_AE_u8 (64 bit report) ===
vbscript:
run.c:1206: Test failed: api.vbs: L"Err.number = 0"
run.c:1206: Test failed: api.vbs: L"Err.description = "
run.c:1206: Test failed: api.vbs: L"Err.number = 0"
See https://gitlab.winehq.org/wine/wine/-/merge_requests/1534
Strangely enough so far this has not happened in the nightly WineTest runs but
it did happen in another unrelated merge request (MR!1561).
According to Nikolay (probably s/testChrError/testCStrError/):
> This is happening on utf-8 locale, in testChrError().
> Needs to be fixed, but unrelated to this MR.
--
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=53172
Bug ID: 53172
Summary: advapi32:registry - test_enum_value() has a pair of
rare failures in UTF-8 system locales
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: advapi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
advapi32:registry - test_enum_value() has a pair of rare failures in UTF-8
system locales:
registry.c:558: Test failed: data set to 'xxxxxxxxxxxxxxxxxxxx' instead of
'foobar' or x's, data_count=21
registry.c:576: Test failed: data set to 'xxxxxxxxxxxxxxxxxxxx' instead of
'foobar' or x's, data_count=21
https://test.winehq.org/data/patterns.html#advapi32:registry
The line 558 and 576 failures happen about with the same frequency (~13% each)
but independently from each other so that most times there is at most one in
the report.
And they only happen in the TestBot's two UTF-8 test configurations:
w10pro64-en-AE-u8 and w10pro64-hi-u8.
--
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=54019
Bug ID: 54019
Summary: The 64-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 64-bit ntdll:wow64 fails on Windows 11. There are two failure modes:
wow64.c:269: Test failed: wrong Tib.ExceptionList 0000000000000000 /
00000013640C5000
wow64.c:273: Test failed: wrong len 0
wow64.c:290: Test failed: wrong len 0
wow64.c:312: Test failed: wrong len 0
wow64.c:320: Test failed: wrong ImagePathName ptr 0 / 75cec0-75d884
wow64.c:320: Test failed: wrong ImagePathNamelen 0 / 210
wow64.c:321: Test failed: wrong CommandLine ptr 0 / 75cec0-75d884
wow64.c:321: Test failed: wrong CommandLinelen 0 / 66
wow64.c:322: Test failed: wrong WindowTitle ptr 0 / 75cec0-75d884
wow64.c:322: Test failed: wrong WindowTitlelen 0 / 210
wow64.c:323: Test failed: wrong Desktop ptr 0 / 75cec0-75d884
wow64.c:323: Test failed: wrong Desktoplen 0 / 30
wow64.c:324: Test failed: wrong ShellInfo ptr 0 / 75cec0-75d884
wow64.c:326: Test failed: wrong size 0 / 3222
wow64.c:338: Test failed: wrong len 0
wow64.c:339: Test failed: BeingDebugged is 0
or with 2 extra failures and different values:
wow64.c:269: Test failed: wrong Tib.ExceptionList 0000000000000000 /
000000A7ECDDA000
wow64.c:273: Test failed: wrong len 0
wow64.c:290: Test failed: wrong len 0
wow64.c:291: Test failed: BeingDebugged is 117
wow64.c:309: Test failed: wrong ptr32 0000000000000000 / 00000298B3F80000
wow64.c:312: Test failed: wrong len 0
wow64.c:320: Test failed: wrong ImagePathName ptr 0 / 0-9c4
wow64.c:320: Test failed: wrong ImagePathNamelen 0 / 210
wow64.c:321: Test failed: wrong CommandLine ptr 0 / 0-9c4
wow64.c:321: Test failed: wrong CommandLinelen 0 / 66
wow64.c:322: Test failed: wrong WindowTitle ptr 0 / 0-9c4
wow64.c:322: Test failed: wrong WindowTitlelen 0 / 210
wow64.c:323: Test failed: wrong Desktop ptr 0 / 0-9c4
wow64.c:323: Test failed: wrong Desktoplen 0 / 30
wow64.c:324: Test failed: wrong ShellInfo ptr 0 / 0-9c4
wow64.c:326: Test failed: wrong size 0 / 3112
wow64.c:338: Test failed: wrong len 0
wow64.c:339: Test failed: BeingDebugged is 117
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 32-bit version fails on
Windows 11 too.
--
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=52895
Bug ID: 52895
Summary: advapi32:service - EnumServicesStatusA() does not
support UTF-8 on Windows?
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: advapi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
advapi32:service fails on Windows with a UTF-8 codepage:
service.c:1283: Test failed: Expected success, got error 8
service.c:1285: Test failed: Expected some returned services
service.c:1312: Test failed: Expected the needed buffer size for this one
service
service.c:1313: Test failed: Expected fewer services to be returned
service.c:1314: Test failed: Expected ERROR_MORE_DATA, got 1783
service.c:1326: Test failed: Expected the needed buffer size for this one
service
service.c:1327: Test failed: Expected fewer services to be returned
service.c:1328: Test failed: Expected a resume handle
service.c:1329: Test failed: Expected ERROR_MORE_DATA, got 1783
service.c:1340: Test failed: Expected success, got error 8
service.c:1342: Test failed: Expected 559038737 services to be returned
service.c:1610: Test failed: Expected success, got error 8
service.c:1627: Test failed: Expected the needed buffer size
service.c:1628: Test failed: Expected fewer services to be returned
service.c:1629: Test failed: Expected ERROR_MORE_DATA, got 1783
service.c:1641: Test failed: Expected the needed buffer size
service.c:1642: Test failed: Expected fewer services to be returned
service.c:1643: Test failed: Expected a resume handle
service.c:1644: Test failed: Expected ERROR_MORE_DATA, got 1783
service.c:1655: Test failed: Expected success, got error 8
service.c:1657: Test failed: Expected 559038737 services to be returned
service.c:1702: Test failed: Expected success 8
https://test.winehq.org/data/patterns.html#advapi32:service
The first failure is an ERROR_NOT_ENOUGH_MEMORY in this call:
services = HeapAlloc(GetProcessHeap(), 0, needed);
bufsize = needed;
needed = 0xdeadbeef;
returned = 0xdeadbeef;
SetLastError(0xdeadbeef);
ret = EnumServicesStatusA(scm_handle, SERVICE_WIN32, SERVICE_STATE_ALL,
services, bufsize, &needed, &returned, NULL);
Where needed was calculated from a previous call (30890 in my case). So the
buffer should be big enough but EnumServicesStatusA() fails anyway. I tried
increasing the buffer size to the max 256KB but EnumServicesStatusA() still
complains about insufficient memory which does not make sense.
Later, when given a resume handle, the tests return RPC_X_BAD_STUB_DATA (1783)
instead of ERROR_MORE_DATA (234).
So this looks like the underlying RPC code that accesses the service control
manager is buggy and does not support UTF-8. So win_skip() the whole thing on
the first failure? Move the resume test with the RPC_X_BAD_STUB_DATA first and
skip if that fails?
--
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.